Techniques

The following techniques can improve the process involving migration:

Migrate at the lowest aggregate level. For example, if you change an attribute, migrate the attribute, not the entity type.
Keep migrates small (less than 10 minutes) if you must do them during peak processing hours.
Know what is running prior to a migration. Do not migrate if other large encyclopedia jobs are running such as an upload, download, model copy or another migrate.
Whenever possible, schedule migrates to run during a time period for single stream batch processing.
If you must perform migrations during peak processing hours, notify all encyclopedia users in advance.
Analyze the objects to be migrated. Know the rules of migration for each type of object. Identify the enabling and companion objects for each object to be migrated. You can use the When Changed report to identify changed objects and automatically create aggregate sets. You can use the Compare Report to compare the results between the source and destination models. The Contains/Contained, References/Referenced, and Implements/Implemented reports help you to identify enabling objects that may need to be included in the aggregate set of the migration.
Avoid large migrations. If one object fails, the entire migration fails.