SF-Data-Arch Data Migration Practice Question
Which object must be loaded first in a standard Salesforce migration involving Accounts, Contacts, and Opportunities?
⚠ Common exam trap
Test-takers sometimes select Opportunities first because they represent revenue, ignoring the fundamental foreign key dependency requiring parent Accounts.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Accounts, to establish the parent records for children.
Accounts must be loaded first because they are the parent objects for both Contacts and Opportunities in the standard data model. Without the Account records present, the foreign key lookups for Contacts and Opportunities will fail, as they have no valid parent ID to link to. Establishing the hierarchy is the fundamental requirement for data referential integrity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Opportunities, because they drive revenue reporting.
Why it's wrong here
Opportunities require a parent Account record to be linked. Attempting to load them first would result in orphan records or outright failure, as the 'AccountId' field is mandatory. Loading revenue objects before the account hierarchy is an architectural mistake that causes significant data dependency issues.
- ✗
Contacts, to ensure the primary contact is defined.
Why it's wrong here
Contacts are child records linked to an Account. Loading them first requires the account IDs to exist. While you can load standalone contacts, they are usually associated with an account. In a full migration, the Account object must always precede the Contact object to ensure proper relationship mapping.
- ✓
Accounts, to establish the parent records for children.
Why this is correct
Accounts serve as the foundation of the relational data model. By loading them first, you generate the Salesforce IDs necessary to map children (Contacts and Opportunities) correctly during subsequent loads. This top-down hierarchical approach is the industry-standard sequence for successful data migration projects in Salesforce.
- ✗
It does not matter if you use the Bulk API.
Why it's wrong here
The API choice does not change the database schema requirements. Even when using the Bulk API, referential integrity must be maintained. You cannot insert child records with a non-existent parent ID. Ignoring the hierarchical dependency will lead to thousands of errors during any API-based migration.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.