When performing large data loads or migrating data into Salesforce, loading Salesforce objects in the correct sequence prevents relationship errors and data integrity issues. Salesforce objects are linked through lookup and master-detail relationships — parent records must exist before child records that reference them are created.
For example, Accounts must be loaded before Contacts because a Contact record contains a lookup field that references an Account. If Contacts are loaded first, the Account lookup will fail.
This article provides the recommended load order for standard Salesforce objects and notes on Custom Objects and Activities.
Load objects in the following sequence to respect parent-child relationships:
000384386

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.