Project Migration Map Best Practices
Keep the following set of best practice recommendations in mind when creating maps to migrate projects from one process model to another:
- Use the From and To Model Names in the Migration Map Name - To help Process Managers identify the migration maps to use when migrating projects, include the original model and the model to migrate to in the migration map name. For example, From Idea Process - Development Process.
- When You Update Models, Recreate Migration Maps - Migration is based on the relationships between the models as they existed when the migration map was created. These relationships are not updated if a model changes. If models that are part of a migration map change, re-create maps that use those models to ensure the migration uses the most current model information.
- Take Caution When Removing Objects from Models - If objects such as deliverables, activities, and gate documents are removed from a model and then added back again, even using the same names, you must re-create existing migration maps that contain those models. Accolade identifies objects within a model with unique IDs that change when new ones are created, causing migrations to fail unless you re-create the migration map.
Learn More: