Prepare to Scan State, Country, and Territory Data and Customizations

Every org’s discovery process is unique. For some orgs, transitioning from state and country/territory text fields to standardized picklists is straightforward and manageable. However, if state and country/territory metadata is used extensively throughout an org, the transition can be a complicated and time-consuming process. Salesforce recommends that you scan your org early and often so that you can transition smoothly to the new lists. Keep these recommendations and considerations in mind.

• Scanning doesn’t convert data or fix your customizations. Convert your data separately, and update your customizations individually.
• You can continue to work normally in your org during the scan.
• The scanning process identifies affected managed packages but doesn’t provide a mechanism for addressing packaging issues.
• Scanning doesn’t find formulas that include state and country/territory metadata.
• You can’t use display values in validation rules or workflow rules that use comparison formula functions. If your validation or workflow rules on state or country/territory fields use BEGINS, CONTAINS, ISCHANGED, or REGEX, use ISPICKVAL with state and country/territory code values in your comparison functions.
• Scanning doesn’t find personal list views and reports that use state and country/territory metadata. Individual users must update those customizations themselves.
• Converted leads aren’t scanned. State, country, and territory values aren’t updated on converted lead records when you enable state and country/territory picklists.
• Scan your org multiple times. After you update a customization, rescan to make sure that your changes fixed the problem and didn’t create new ones.