Resources
Planning migrations based on governance
Depending on the size of your migration, your project may also require a migration specialist to assist with planning migration.
Your migration must not move unneeded content to your new platform. To avoid moving unneeded content, your governance team must review the content inventory created at the same time designing your content architecture. You must establish a plan to ensure the unneeded content is not moved to your new platform. For more information, see Designing your content architecture.
After creating an inventory of your content you must create a spreadsheet to map your existing fields and attributes to the fields and attributes in your new platform. You must determine which content types can migrate programmatically, and which ones must migrate manually.
In both cases, your migration plan must account for the types of effort required:
For more information about migrations, see 10 Tips to Streamline Migration Review on dev.acquia.com.
Your migration specialist must investigate the technical details of your migration, such as assessing the size of your databases, both to determine the number of content types but also the time required to send data from one source to another.
The migration specialist must also perform small test migrations with your proposed data mappings to identify issues or resolve inconsistencies before the final migration.
Your migration specialist must review the security of your data and determine your needs for security certifications and password protection.
In the following documentation, you will gradually learn more about maintaining your governance plans.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.