Retry without the uncertainty.
Separate logical jobs from processing attempts and make duplicate handling, partial outcomes, and uncertain commits understandable.
Read the guideImport solutions
Data Migration
Plan mappings, rehearsals, cutover, and recovery before moving the production dataset.
Inventory before moving
Define the source collection, ownership, destination schema, and relationships between record types. Separate active data from archives and intentionally excluded fields. Identify which external identifiers remain stable and where the destination will generate its own keys.
Keep an explicit mapping for each source type. A field with a similar name may have a different meaning in the new application. Document conversions and the behavior of absent, empty, and null values.
Rehearse the difficult cases
Run a representative dry run and reconcile counts by record type. Include duplicate identifiers, unsupported values, missing relationships, and a partial processing failure. Keep parsing and business-rule errors separate so correction work has a clear owner.
Decide how changes made during the migration window are captured. A one-time export is a snapshot; a destination that continues changing needs a plan for conflicts and final reconciliation.
Make cutover recoverable
Record the source revision, mapping version, and outcome of each logical import. Distinguish retries from new requests, and verify behavior when the result of an attempt is uncertain. Keep rollback or compensating changes within a defined boundary.
Before declaring the migration complete, compare agreed totals and representative records, verify permissions, and test the destination workflows. Archive reports under an appropriate retention policy so later corrections can reference what actually happened.
Define your first acceptance check
Choose a representative source, an owner for the destination contract, and a small set of results that a reviewer can inspect. Include a correction case and an interrupted attempt before expanding the workflow.
The developer guides connect these planning decisions to record shapes and local examples. Keep your implementation narrow enough that its outcome is easy to explain.
From Import Notes
A little reading. A better workflow.
Map it. Validate it. Understand it.
Separate transformations from validation, make every conversion explainable, and design useful errors around an explicit destination contract.
Read the guide