Comparing Objects in Different Models › Evaluating the Compare Aggregate Object Report › Evaluate Report Data to Determine the Next Step › Migrate Objects

Migrate Objects

Migrating objects enables you to maintain the same version of like objects across models. Migration either replaces an equivalent object, if it exists in the destination model, or creates a new instance of the object in the destination model:

• For each object pair reported as different, evaluate the content, then:
  • If one version is acceptable as is, consider making the objects the same in both models by migrating the preferred version to the model containing the version to be replaced.
  • If neither version is acceptable as is because each has unique component objects that you want to retain, consider migrating one object's unique components to the other model, then migrating the updated aggregate object back.
  • If both versions are acceptable as is because the same updates were made to each at different times, consider migration to prevent future reporting of a difference.
• For each object reported in the section, the following objects do not exist in the source model; consider adding that object to the source model through migration.
• For each object reported in the section, the following objects do not exist in the destination model; consider adding that object to the destination model through migration.
• Aggregate objects listed in the section, the following objects are the same do not require migration. If such objects exist in the aggregate set to be used for migration, they should be removed.

For report example reports listing possible candidates for migration, see the following:

• Compare Report That Identifies Objects to Consider for Migration.
• Sample Compare Report on an Aggregate and Its Subordinate Objects.