Example My Domain Change Pre-Deployment Checklist

Each company and configuration is different. Use this checklist as a starter list for updating your org before your My Domain change. For the checklist to complete after you deploy your My Domain change, see Example My Domain Change Post-Deployment Checklist.

Optionally, to create your own version of this checklist, use the My Domain Change Checklist Templates in Quip (available in English and Japanese only). For more information on each of these steps, see Update Your Org for My Domain Changes.

Note Enhanced domains were enforced in Winter ’24. For more information, see Enhanced Domains Timeline. To assist customers who continue to test after deploying enhanced domains, these checklists include steps that are specific to that change.

Example Pre-Deployment Checklist

• Allowlists—Update your allowlists for any new domains.
• Cross-Org Links and Redirections—Create an inventory and plan to update them after you deploy the new domain.
• Custom Visualforce pages or custom apps—Replace references to the org’s instance URL with relative URLs and dynamically generated host names. Note any URLs that require a hard-coded reference.
• Einstein Bots—Identify the web pages and sites that use your bots. For each chatbot, review the Permitted Domains field in the chat deployment settings.
• External software that accesses your Salesforce org—Verify that the external software that uses your Salesforce URLs, including site URLs, can process redirections. If the software can’t process those redirects, work with the software owner to get that redirection functionality in place, or plan to update your use of the software with your new URLs after you deploy the change.
• Firewalls and Proxy Servers—Update trust settings that filter by host name. Include all applicable URL formats for your new configuration.
• Hard-coded Salesforce org URLs—Create an inventory. Replace hard-coded Salesforce org URLs with relative URLs and dynamically generated URLs when possible. Note the URLs to update after you deploy the change.
• Identity providers on your Salesforce login page—Note any authentication options available to your users.
• Installed Packages from AppExchange—To get the latest fixes, potentially including fixes for enhanced domains, install the latest version of each package. Note the package providers so that you can report any issues detected.

If the change to your My Domain updates your My Domain login URL, complete these tasks.

• Authentication options such as single sign-on (SSO), authentication providers, and named credentials—Plan to update authentication. Document your existing settings for your rollback plan.
• Knowledge articles served on your *.my.salesforce.com URL—Search for hard-coded references to the knowledge article URLs.
• Lightning Out (beta)—Identify the Visualforce pages, web pages, and other locations that call your Lightning Out app. Identify who can update the markup that’s embedded in those pages. Determine whether authenticated users access Lightning Out and whether the connected app for Lightning Out uses your My Domain login URL.
• Open Computer-Telephony Integrations (CTI), such as Salesforce Call Center and Click to Dial—Work with your telephony provider to add your new URLs to their allowlists. Review your configuration for any hard-coded references to your Salesforce URLs. Whenever possible, update these references to relative URLs instead, and note any exceptions.
• Preserve login access for your admins and end users.
• Service Cloud Voice with Partner Telephony—Work with your telephony provider to add your new URLs to their allowlist. Also identify hard-coded connect API URLs and references to the Next generation Omni-Channel engagement URL that ends in *.my.salesforce-scrt.com.

If the change to your My Domain updates your Visualforce URL, complete these tasks. If the change also updates your My Domain login URL, these pre-deployment tasks are included in that section.

• Open Computer-Telephony Integrations (CTI), such as Salesforce Call Center and Click to Dial—Work with your telephony provider to add your new Visualforce URL to their allowlists. Review your configuration for any hard-coded references to your Visualforce URLs. Whenever possible, update these references to relative URLs instead, and note any exceptions.
• Salesforce Maps—Determine whether you show nearby maps in Salesforce records or on sites.
• Service Cloud Voice with Partner Telephony—Work with your telephony provider to add your new Visualforce URL to their allowlist. Also identify hard-coded references to your Visualforce URL in your configuration. Whenever possible, update these references to relative URLs instead, and note any exceptions.

If the change to your My Domain changes your Experience Cloud sites or Salesforce Sites URL, complete these tasks.

• Authentication options such as single sign-on (SSO), authentication providers, and named credentials—Plan to update authentication. Document your existing settings for your rollback plan.
• Embedded Service Deployment (Chat)—Identify the web pages that include chat and identify who can update the code snippet embedded in those pages.
• Knowledge articles served on your Experience Cloud site URL—Search for hard-coded references to the knowledge article URLs.
• Lightning Out (beta)—Identify the connected apps for Lightning Out that use your Experience Cloud sites URL. Determine whether authenticated users access Lightning Out.
• Identity providers on your site login page—Note any authentication options available to your users.
• A Mobile Publisher for Experience Cloud app that uses your Experience Cloud site login URL—Before you deploy enhanced domains in production, upgrade to Mobile Publisher version 10.0 or later.
• Multi-factor authentication (MFA) for your site—Preserve login access for your admins and end users.

If you have Experience Cloud sites or Salesforce Sites and the My Domain change includes deploying enhanced domains, complete these tasks.

• External integrations—Work with third parties that currently integrate with your *.force.com site URL to ensure that they support Server Name Indication (SNI).
• IP restrictions are configured in Salesforce with only IPv4 addresses—Update your IP allowlists or restrictions to allow IPv6 source addresses for authorized users. Review and update the login IP range restrictions for the relevant profiles, including the site’s guest user profile.
• Network restrictions that use IP allowlists only—Allowlist your site’s domain, serve your site via a custom domain, or plan to disable the Salesforce CDN for your *.my.site.com URL after you deploy the My Domain change.
• Trusted domains for inline frames—Review and update the list of trusted domains for clickjack protection. Ensure that *.my.salesforce.com is trusted.
• Visualforce pages with embedded Lightning components—For each Experience Cloud site with Visualforce pages that include embedded Lightning components, update the Security & Privacy settings, and add your Lightning Components URL to the Trusted Sites for Scripts.