Run Mass Update Addresses as part of the State and Country/Territory Picklists conversion. Do this in a sandbox first, scan your data, then convert values in controlled waves before relying on it in production.
- Scan your org first
From Setup, open State and Country/Territory Picklists and run the scan. Review the discovery report to see every distinct country and state value, which records hold them, and which list views, reports, and code reference the fields.
- Set integration values
Before converting, confirm the integration value for each standard country and state matches what your existing integrations send and receive. Defaults follow the full ISO names. Adjust them so API calls, data loads, and formulas keep working after enablement.
- Open the conversion tool
Choose to convert your identified data. Decide whether you are updating country, state, or both. The tool groups existing records by their current text value so you map each group once rather than editing records individually.
- Map and apply in waves
For each text value, pick the standard value it should become, then apply. Work through high-volume countries in batches, and let any triggers or flows settle between waves rather than converting everything in one pass.
- Verify and lock it down
Query for records still on non-standard values, spot-check samples across Account, Contact, Lead, and Person Account, and add validation rules so imports and integrations cannot reintroduce free-text variants later.
Controls which part of the address you convert. State and country are linked, so a state cannot be saved without a matching country in scope.
The Setup tool handles Account, Contact, Lead, and Person Account. Use Data Loader with a mapping CSV for custom objects, which the tool does not cover.
The text stored on the record after conversion. Set it to match legacy integrations before running, since it is what downstream systems read.
- Records not re-saved since you enabled picklists keep their original text values, so convert before relying on the data rather than assuming enablement cleaned it.
- Every rewritten record can fire triggers, flows, validation rules, and workflow on the address fields, so high-volume runs can hit governor limits or spam notifications.
- Custom objects with address fields are out of scope; convert those with Data Loader using a prepared mapping CSV.
- These picklists are not supported in change sets or packages, so move integration value changes from sandbox to production with the Metadata API.