SF-Data-Arch Data Migration Practice Question
Which THREE factors are essential to consider when performing a multi-org data migration consolidation?
⚠ Common exam trap
Candidates often focus only on record migration while neglecting the metadata and security model. They fail to realize that differing profiles and field data types will break the target org structure.
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
✓
Handling duplicate record IDs across source orgs.
Consolidating multiple Salesforce orgs requires meticulous planning around unique ID collisions, metadata differences (such as custom field mapping), and security model alignment. Since each org has its own unique record IDs and potentially overlapping data, an intermediary mapping strategy is vital to ensure that relationships are preserved correctly in the new, unified environment without creating duplicate records or data conflicts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Handling duplicate record IDs across source orgs.
Why this is correct
Since Salesforce IDs are only unique within a single org, consolidation will lead to ID collisions. Architects must map original records to new unique external keys and cross-reference them to ensure that parent-child relationships remain intact within the new, consolidated environment after the data is migrated.
- ✓
Merging disparate security models and profiles.
Why this is correct
Different orgs often have completely different security structures. Consolidating requires mapping roles, profiles, and sharing rules into a unified model. Failure to align these models leads to data being exposed to users who should not see it, or users losing access to data they previously owned.
- ✓
Mapping custom fields with identical names but different data types.
Why this is correct
Even if fields share the same label, their underlying data types or picklist values may differ across orgs. A rigorous metadata gap analysis is required to normalize these discrepancies into a single, unified schema before any actual record data can be migrated successfully.
- ✗
Enabling the 'Set Audit Fields' for every user.
Why it's wrong here
This permission is a security-sensitive setting and should only be granted to the specific integration user account performing the migration. Granting this to all users would be a major security violation, as it allows users to modify historical system timestamps and ownership, compromising data integrity.
- ✗
Using only the standard Import Wizard for migrations.
Why it's wrong here
The Import Wizard is designed for small, manual loads and lacks the advanced mapping capabilities needed for large-scale, complex consolidation projects. Professional migrations require enterprise ETL tools that support multi-pass loads, complex logic transformation, and high-volume processing, which the Import Wizard cannot handle appropriately.
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.