text update

Author: tapanm-MSFT

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

@@ -40,7 +40,12 @@ 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 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.
+> The Configuration Migration tool uses schema to export and import configuration data. The tool does not migrate entities or entity schema. Migration may fail with missing elements such as entities and fields when configuration data has mismatch with selected schema.
+>
+> During export, ensure the source environment contains portal entities as specified in Configuration Migration tool schema file. You can still alter the schema files to add, remove, and modify entities, attributes, and so on to migrate subset of configuration data.
+>
+> During import, ensure the destination environment contains the same portal type already installed with any additional customizations such as entities, fields, forms or views imported separately as solutions.
+
 
 ## Export portal configuration data