Migration Plans

As described in the previous section, the drivers for which instructions to include in a migration plan differ a bit based on whether the migration plan will be included in a wholesale or a piecemeal migration request. The decision for the base product migration plans was to not provide multiple migration plans for various objects (one for wholesale migrations and one for piecemeal migrations). Rather, the base product provided migration plans supports a reasonable piecemeal migration. In general, sub-instructions are not provided for the foreign keys where there is a reasonable assumption that the data already exists in the target region. For example, the migration plan for any record that has a foreign key to Tax Type will not include a sub-instruction for tax type given that tax type is considered a type of “parent” configuration object that would be copied on its own to a region and not as part of the migration of a lower level entity.

Note: Potential issues in wholesale migrations. Because not all foreign key references that are part of base business objects in the BO Data Area are defined in the migration plans, it means that CMA will not know about the relationship between the record and its foreign key and will not know to group the data together. This could cause some “foreign key not found” errors on the import side. Users importing the data will then need to manage resolving the order of insertion of the new records in the target region.

To see the migration plans provided with the base product, navigate to Admin > Migration Plan and view the data that is provided there.

The following points highlight some information about the base administrative objects and their migration plans.

Refer to the detailed descriptions of the base migration plans for more information.

Note: Base package migration plans cannot be altered. To extend an existing base package migration plan, the base package plan must be duplicated and then altered as needed. The duplicate migration plan can then be added to a custom migration request.