Object migration library

Salesforce Data Migration Object Library

Migration guidance for Salesforce objects including record Ids and External Ids, relationships, RecordTypes, ownership, validation rules and Bulk API loading.

How Salesforce accepts data

Load order and mechanism apply across every object on this platform.

1. 1Reference and setup data firstTerritories, currencies, price books, products and picklist values. Everything downstream resolves against these.
2. 2Accounts, then contactsAccounts head the customer hierarchy. Parent-child account relationships resolve in a second pass, because a parent has no target key until it has itself been created.
3. 3Use External Id fields for upsertLoading against an External Id makes a reload an update rather than a duplicate, which is what makes multiple migration cycles survivable.
4. 4Leads with conversion state intactSo converted leads are not re-presented to sales as open work on day one.
5. 5Opportunities and line itemsResolved against account and owning user. Stage and close date drive forecasting, so their mapping is validated rather than assumed.
6. 6Activities, cases and historyEach resolving to a parent that now exists.
7. 7Ownership and sharingOwner drives visibility. Where a source owner has no counterpart, the fallback is an explicit decision rather than a default.