SF-Data-Arch Data Migration Practice Question
A Salesforce data architect is migrating 500,000 Lead records from a legacy system. The legacy data contains a field 'Lead_Status' with values such as 'New', 'Working', 'Qualified', 'Unqualified'. Salesforce's Lead Status picklist has values: 'Open - Not Contacted', 'Working - Contacted', 'Closed - Converted', 'Closed - Not Converted'. The architect needs to map the legacy values to the Salesforce picklist values. Which approach should be used to ensure a successful migration?
⚠ Common exam trap
The trap here is thinking that Salesforce will automatically map legacy picklist values or that the picklist can be easily modified without impact.
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
✓
Use an ETL tool to map legacy values to the corresponding Salesforce picklist values before loading.
Mapping legacy values to the standard Salesforce picklist values must occur before loading to avoid errors and ensure data consistency. An ETL tool provides the necessary transformation capabilities. Other options either avoid the mapping, cause load failures, or alter the Salesforce schema unnecessarily.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Load the legacy values as-is and then run a batch Apex job to update the Lead Status field.
Why it's wrong here
Loading invalid picklist values would cause errors because Salesforce validates picklist entries during insert. Even if the field were a text field, a subsequent update would be needed, which is inefficient and may hit governor limits. This approach risks partial loads and requires additional development. It is not the best practice.
- ✗
Create a custom field to store the legacy Lead Status and leave the standard Lead Status blank.
Why it's wrong here
Creating a custom field does not meet the requirement to map to the standard Lead Status picklist. The business likely needs the standard field populated for reporting and automation. Leaving it blank would result in incomplete data and potential process failures. This approach avoids the mapping challenge rather than solving it.
- ✗
Modify the Salesforce Lead Status picklist to include the legacy values.
Why it's wrong here
Adding legacy values to the standard picklist may not be desirable and could disrupt existing business processes. It also does not map to the intended Salesforce values, so reporting would be inconsistent. The requirement is to map to existing values, not to expand the picklist. This approach changes the Salesforce data model unnecessarily.
- ✓
Use an ETL tool to map legacy values to the corresponding Salesforce picklist values before loading.
Why this is correct
An ETL tool can transform the legacy Lead Status values to match the Salesforce picklist values exactly. This ensures that the standard Lead Status field is populated correctly and avoids load errors. The mapping can be defined in the ETL tool's transformation logic. This is the most reliable method for ensuring data quality.
About these practice questions
This SF-Data-Arch question is part of Courseiva's 222-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.