Migration Implementation Considerations

Pre-Migration

• Test the migration logic with a small, representative data set before a full migration.
• Proceed with bulk data loading data only after you verify that the generated assets and billing schedules work as expected. Make sure that you also validate positive amendments, negative amendments, the cancellations of assets, and the invoice behavior.

Object Import Order

Import object records based on how objects are referenced by other objects. Migrate the records of parent objects before you migrate the records of their child or related objects.

Data Orchestration

• While there’s no limit on the number of historical orders that you can migrate, sequential activation requires careful orchestration during large-scale deployments to avoid processing issues.
• Switch off your org’s triggers to ensure that the records are migrated efficiently.

Data Volume and Performance for Large Datasets

Migration tools can handle large-scale deployments. Performance varies based on data quality and transformation complexity. For large datasets, follow these guidelines.

• For objects that have a large volume, divide the data into batches and then migrate each batch. See Bulk API and Bulk API 2.0 Limits and Allocations.
• Defer sharing calculations for high data volume objects until data import is complete. See Defer Sharing Calculations.
• Use chunked batch processing to avoid loading millions of records in a single transaction.
• For Data Manipulation Language operations, set allOrNone to false to allow partial batch success and reduce transaction failure risk.
• Expect and plan for record-level failures. Not all records migrate successfully the first time. Build retry logic into your implementation to handle failed records.