SF-Data-Arch Data Migration Practice Question
A Salesforce data architect is migrating 100,000 Opportunity records from a legacy system. The legacy data includes a custom field 'Legacy_Region__c' that must be mapped to a new picklist field 'Region__c' in Salesforce. The picklist values in Salesforce are: 'North America', 'Europe', 'Asia', 'Latin America'. The legacy data uses values like 'NA', 'EU', 'APAC', 'LATAM'. What is the most efficient way to transform the data during migration?
⚠ Common exam trap
The trap here is assuming that Salesforce can automatically map legacy values to picklist values or that post-load updates are efficient.
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
✓
Perform the transformation in an ETL tool before loading the data.
The most efficient way to transform legacy values to match Salesforce picklist values is to perform the transformation in an ETL tool before loading. This avoids load errors and ensures data quality. Formula fields, post-load updates, and workflow rules are either not possible or inefficient for this purpose.
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 use Data Loader to update the picklist values.
Why it's wrong here
Loading invalid picklist values would cause errors because Salesforce enforces picklist restrictions. Even if the field were a text field initially, a subsequent update would be needed, which is inefficient. This approach risks partial loads and requires additional steps. It is not the most efficient way.
- ✗
Use a formula field in Salesforce to convert the legacy values after loading.
Why it's wrong here
Formula fields are read-only and cannot be used to transform data during load. They are calculated at query time, so they cannot map legacy values to picklist values for storage. The legacy field would need to be loaded first, but the picklist field requires the transformed values. This approach does not work for migration.
- ✓
Perform the transformation in an ETL tool before loading the data.
Why this is correct
Using an ETL tool allows the architect to map legacy values to the correct picklist values before loading into Salesforce. This ensures data integrity and avoids load errors due to invalid picklist values. The transformation can be done via lookup tables or scripts within the ETL tool. This is the most efficient and reliable method for large-scale migrations.
- ✗
Create a workflow rule to update the picklist field based on the legacy field.
Why it's wrong here
Workflow rules cannot set picklist values to invalid entries, and they run after save, so the initial load would fail if the legacy field is a picklist. If the legacy field is a text field, a workflow could update the picklist, but this adds complexity and may hit governor limits. It is not the most efficient for bulk migration.
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.