Enabling these picklists is a one-way improvement to data quality, but the rollout has several moving parts. The standard sequence below avoids the common pitfalls and gives the org a clean activation rather than a panicked rollback.
- Run the address scan in sandbox first
From Setup, navigate to State and Country/Territory Picklists and run the address scan. The scan completes in minutes for small orgs and hours for large orgs with millions of records. Review the output report: which records mapped cleanly, which need manual review. Build a cleanup plan for the unmappable records, either correcting them manually for small volumes or using Data Loader for larger volumes.
- Audit and update validation rules, formulas, automations
Search the org for every validation rule, formula field, workflow rule, process, Flow, and Apex class that references BillingState, BillingCountry, MailingState, MailingCountry, ShippingState, or ShippingCountry. Update text comparisons from full names ("California") to Integration Values ("CA"). Run these changes through the standard test cycle. Document any places where automation now needs adjustment so the same changes can be repeated in production.
- Configure custom values and deactivate unused entries
Review the standard picklist values for any countries or states the business does not operate in. Deactivate them to keep the picklist short. Add custom values for any geographies Salesforce does not ship by default. Test the customizations against a sample of records to confirm the address fields look right. Save the configuration and prepare to replicate it in production.
- Enable in production during a low-activity window
Schedule production enablement during a low-traffic window, ideally a weekend or after-hours period. Run the address scan in production, apply the cleanup plan to the unmappable records, then enable the picklists. Communicate the change to integration owners and data teams the same day so they can verify their downstream systems still work correctly. Monitor the Setup Audit Trail and any custom error logs for the next several days for any automation that misbehaves.
- Once enabled, picklists cannot be reverted to free-text fields without a Salesforce Support engagement and significant data implications. Treat the enablement as permanent.
- Validation rules and formulas need to use Integration Values, not Display Values. Rules that compare against full state names break silently on enablement.
- The address scan does not detect all unmappable values. Manual review of the report is required because some records contain valid-looking strings that the scanner accepts but that map to the wrong state or country.
- Integrations that POST records with full state names like "California" fail after enablement. They must be updated to send "CA" or rely on the platform's text-to-picklist matching, which is not always available.
- Visualforce and Aura components that build custom address forms must be updated to use the standard state picklist components. Custom text inputs cause silent data corruption.