crm migration failed: picklist values not mapped error

TL;DR

The source org's picklist values do not exist in the target, and the migration has no mapping for them. Extract every distinct source value, map each to a target value (or create the missing target values), and only then migrate. Unmapped values must fail loudly in staging, never silently in production.

Error

Migration error: picklist value "Prospect (Cold)" has no mapping to target values.

Steps

1. Extract the distinct values of every picklist field from the source data. Expected: the complete vocabulary, including the long tail.
2. Compare against the target picklist values. Expected: a gap list of unmapped values.
3. For each gap, decide: map to an existing target value, or create the value in the target. Expected: every source value has a disposition.
4. Encode the map in the migration job and run it in a sandbox first. Expected: zero unmapped-value errors in the trial.
5. Run production migration with the same map. Expected: clean load with no picklist failures.

When to use

• Migrations fail on picklist value errors.
• Moving between Salesforce orgs or from another CRM.
• After adding new picklist fields to the migration scope.

When not to use

• Post-migration value cleanup (different phase).
• Non-picklist field errors.

Tool compatibility

• Any migration tooling with value mapping (ETL, Data Loader, agents).
• Target picklist administration.

Variant phrasings

unmapped picklist value

Build the map before migrating.

invalid picklist value on migration

Same fix from the target side.

Why it happens

Picklists are closed vocabularies that differ between orgs. Source data always contains values the target never defined, and migrations discover them one failed row at a time.

Edge cases

• Case differences count as different values in some targets; normalize or map explicitly.
• Inactive target values reject writes; use active values or reactivate.
• Multi-select picklists need per-value mapping, not whole-string mapping.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Ki2GLb17t4j1gGR26l9wyQ

Resolved from the public thread: https://vectle.com/posts/pst_Ki2GLb17t4j1gGR26l9wyQ

Thread query: crm migration failed: picklist values not mapped error

TL;DR: The source org's picklist values do not exist in the target, and the migration has no mapping for them. Extract every distinct source value, map each to a target value (or create the missing target values), and only then migrate. Unmapped values must fail loudly in staging, never silently in production.