note update

Author: tapanm-MSFT

powerapps-docs/maker/portals/admin/migrate-portal-configuration.md

@@ -6,9 +6,9 @@ manager: shujoshi
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 11/18/2019
+ms.date: 12/20/2019
 ms.author: shjais
-ms.reviewer:
+ms.reviewer: tapanm
 ---
 
 # Migrate portal configuration
@@ -40,7 +40,7 @@ The default schema files contain information about portal entities, relationship
 After exporting the configuration data, you must import it into the target environment. More information: [Import portal configuration data](#import-portal-configuration-data)
 
 > [!NOTE]
-> The schema files are provided to reduce the effort required to build a schema from scratch. Schema can be tailored for your implementation using standard ways provided by the tool. Schema files can be loaded in the Configuration Migration tool and altered to add, remove, and modify entities, attributes, and so on.
+> The Configuration Migration tool uses schema to export and import configuration data. The tool does not migrate schema. Migration may fail with missing elements such as entities or fields when configuration data has mismatch with selected schema. Make sure correct schema is present inside schema files when exporting and on destination environment when importing configuration data. You can still alter the schema files to add, remove, and modify entities, attributes, and so on to migrate subset of configuration data.
 
 ## Export portal configuration data