SF-Data-Arch Data Migration Practice Question
A Salesforce architect is planning a migration of 2 million custom object records from a legacy Oracle database. The legacy system has a field 'Status' with values like 'Active', 'Inactive', 'Pending', and 'Archived'. In Salesforce, the Status field is a picklist with values 'Active', 'Inactive', and 'Pending' only. The architect needs to migrate the data while preserving as much information as possible and ensuring data quality. Which two actions should the architect take? (Choose two.)
⚠ Common exam trap
The trap here is assuming that adding a new picklist value or excluding records is acceptable, when the better approach is to transform the data and preserve the original value for audit.
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
✓
Create a custom text field to store the original legacy status value for audit purposes, in addition to mapping to the picklist.
The architect should map the unsupported 'Archived' value to a valid picklist value like 'Inactive' to maintain data integrity and avoid load failures. Additionally, storing the original legacy status in a separate text field preserves the exact source information for auditing. This combination ensures data quality, traceability, and compliance with Salesforce picklist constraints.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add 'Archived' as a new picklist value in Salesforce to accommodate the legacy data without transformation.
Why it's wrong here
Adding a new picklist value might seem straightforward, but it could impact existing business processes, reports, and automation that assume only three values. It also may not be approved by stakeholders. The architect should first assess if 'Archived' is needed in the new system; if not, mapping to an existing value is preferable. This option assumes uncontrolled schema changes.
- ✓
Create a custom text field to store the original legacy status value for audit purposes, in addition to mapping to the picklist.
Why this is correct
Storing the original legacy status in a separate text field preserves the exact source value for auditing and reporting, while the picklist field is used for operational purposes. This dual approach ensures data quality and traceability without compromising the picklist's integrity. It is a best practice when transforming data during migration to retain historical context.
- ✗
Use a validation rule to prevent 'Archived' from being loaded, and manually update those records after migration.
Why it's wrong here
A validation rule would block the load of 'Archived' records, causing errors and requiring manual intervention. This is inefficient for 2 million records and risks incomplete data. The architect should handle transformations during the load, not rely on post-load manual updates. This approach introduces unnecessary complexity and potential for human error.
- ✓
Map the legacy 'Archived' value to 'Inactive' in Salesforce and document the transformation for future reference.
Why this is correct
Mapping 'Archived' to 'Inactive' preserves the record's inactive status while conforming to the Salesforce picklist. Documenting the transformation ensures auditability and clarity for future data consumers. This approach avoids data loss by not dropping records and maintains data quality by using an existing valid value. It is a common practice when source values exceed target picklist options.
- ✗
Exclude records with 'Archived' status from the migration to avoid picklist conflicts.
Why it's wrong here
Excluding records would result in data loss, which is typically unacceptable in a migration. The architect should aim to migrate all records, transforming values as needed. Dropping records can lead to incomplete reporting and business disruption. This option fails to meet the requirement of preserving as much information as possible.
About these practice questions
Courseiva writes every SF-Data-Arch question from scratch — 222 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.