Example My Domain Change Post-Deployment Checklist

Each company and configuration is different. Use this checklist as a starter list for updating your org after you deploy your My Domain change. For the checklist of tasks to perform before you deploy your My Domain change, see Example My Domain Change Pre-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 Post-Deployment Checklist

• Incomplete pre-deployment tasks—Review the pre-deployment update checklist, and complete any incomplete tasks.
• Changed URLs—To help your users update outdated links and bookmarks, enable a brief message during the redirection that provides the current URL.
• Cross-Org Links and Redirections—Update references to your old My Domain URLs.
• Chatter—Tell your users to update the bookmarks listed on their Chatter groups.
• Custom Visualforce pages or custom apps—Replace references to the org’s instance URL with your new My Domain URL. Whenever possible, use relative URLs and dynamically generated host names.
• Einstein Bots—For each bot, regenerate the deployment code and update it on each web page that uses the bot.
• External software that accesses your Salesforce org—Update the references to your Salesforce URLs within the external software, and log in to Salesforce again.
• Hard-coded references to URLs—Update hard-coded references to your old URLs, including instanced host names, such as na87.salesforce.com. Ideally, generate the host name via a dynamic method, such as the DomainCreator class in Apex. If you deployed enhanced domains, review the host name redirections that stop in Winter ’25. If you find any of those host name formats in your org, update them to the enhanced domain format.
• Installed packages from AppExchange—Verify package functionality. For your end-user communications, note the features that require users to reconnect.
• Pinned certificates—Eliminate (recommended) or update the certificates.
• Firewalls and Proxy Servers—Optionally, remove the host names that no longer apply to your org from your trust settings. However, we recommend that you allow those host names for redirection until all users and integrations are using your new domains successfully.

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

• API Integrations—Update API integrations into your org to use the server endpoint. Download your metadata, and then use a command-line interface to search.
• Branding—If your brand changed, update your login page branding
• Desktop links—Update the desktop link with your new My Domain login URL.
• DevOps Center—Update the named credentials used to authenticate users that access your org through DevOps Center.
• Email templates—Update the login URL for your Salesforce org.
• Enablement Sites (myTrailhead)—If your enablement site’s login URL is your My Domain login URL, contact Salesforce Customer Support to update your Sales Enablement authentication provider.
• Identity providers on your login page—Update your identity providers to use your new login URL.
• Knowledge articles served on your *.my.salesforce.com URL—Update hard-coded references to the knowledge article URLs.
• Lightning Out (beta)—Update external client apps that use your My Domain login URL. Refresh the markup on Visualforce pages, web pages, and other locations that call your Lightning Out app. Generate a new Session ID or authentication token for authenticated connections.
• Enhanced Chat—To update your Enhanced Web Chat configuration with your new URLs, republish your Enhanced Web Chat deployment.
• Multi-factor authentication (MFA) for accessing Salesforce—Update authentication.
• Named credentials—Review the URL field for your named credentials. If a named credential uses your My Domain login URL, update the URL field with your new My Domain login URL. If users access functionality that relies on an updated named credential, instruct them to reauthenticate.
• Marketing Cloud Account Engagement (Pardot) —If your configuration uses the Pardot Connector User, update the login URL that Account Engagement uses.
  

  Warning When you deploy another My Domain change, existing redirections stop.
• Open Computer-Telephony Integrations (CTIs), such as Salesforce Call Center and Click to Dial—Verify and optionally update your telephony provider’s allowlist. Update any hard-coded references to your Salesforce URLs in your configuration.
• A personalized version of the Salesforce mobile app published on the Google Play or Apple App stores—If your personalized version of the Salesforce app uses your My Domain login URL, update your app to use your new login URL.
• Service Cloud Voice with Amazon Connect or Service Cloud Voice with Partner Telephony from Amazon Connect—Optionally, remove your old URL formats from the Amazon Connect allowlist.
• Service Cloud Voice with Partner Telephony—Update any hard-coded references to your Salesforce URLs in your configuration. Optionally, remove your old Salesforce URLs from the telephony provider’s allowlist.
• Single sign-on for accessing your org—Update authentication.
• Streaming API—Update to use your new My Domain login URL.
• Third-party external client apps that access your org—Work with the app owners to update the login URLs in their app, including SSO and other authentication methods.
• Zones for Experience Cloud sites (Ideas, Answers, Chatter Answers)—Update the email notification URL.

If the Visualforce URL changed, complete these tasks. If the change also updates your My Domain login URL, these post-deployment tasks are covered in that section.

• Open Computer-Telephony Integrations (CTIs), such as Salesforce Call Center and Click to Dial—Update any hard-coded references to your Visualforce URLs in your configuration. Verify and optionally update your telephony provider’s allowlist.
• Salesforce Maps—If you show nearby maps in Salesforce records or on sites, update the corresponding Maps Nearby Map component.
• Service Cloud Voice with Partner Telephony—Verify and optionally update your telephony provider’s allowlist.

If the content URL changed, complete these tasks.

• Email and other document templates that use files hosted in Salesforce—Update the embedded content or images. Instruct users to update their local templates. For example, an icon or image hosted in your org and used in email footer templates.
• Enablement Sites (myTrailhead)—Update your modules and trails with your new badge art URLs.
• Web content that uses files hosted in Salesforce—Update the content links. For example, an image used on your website or externally published PDFs.

If your Experience Cloud sites or Salesforce Sites URL changed, complete these tasks.

• Authentication that uses your site URL—Verify your configuration. If your setup uses your site URL, update the configuration.
• Branding—If your brand changed, update the branding for your Experience Cloud site login page.
• Desktop links—Update the desktop links with your new site login URL.
• Email templates—Replace references to your old site URLs with your new site URLs.
• Embedded Service Deployment (Chat)—Regenerate the Embedded Service code snippet. Update the web pages that include chat with the new snippet.
• Enablement Sites (myTrailhead)—If your enablement site’s login URL is your Experience Cloud sites URL, contact Salesforce Customer Support to update your Sales Enablement authentication provider.
• External integrations—Update external integrations that reference your sites.
• External links to the site—Update all references to the new site URL.
• Hard-coded references to your site within your sites and custom pages—Update the references to your site URL. Where possible, use relative links or dynamically created host names.
• Identity providers on your site login page—Update your identity providers to use your new site URL.
• Knowledge articles served on your Experience Cloud sites URL—Update hard-coded references to the knowledge article URLs.
• Lightning Out (beta)—Update external client apps that use your Experience Cloud login URL. Generate a new Session ID or authentication token for authenticated connections.
• Enhanced Chat—If you use Enhanced Web Chat in an Experience Builder site, update your allowlisted URLs.
• A Mobile Publisher for Experience Cloud app—Update your app to use your new Experience Cloud sites URL.
• Multi-factor authentication for accessing your site—Update authentication.
• Named credentials—Review the URL field for your named credentials. If a named credential uses your site URL, update the URL field with your new site URL. If users access functionality that relies on an updated named credential, instruct them to reauthenticate.
• Single sign-on for accessing your site—Update the configuration.
• Third-party external client apps that access your site—Work with the app owners to update the site URLs in their app, including SSO and other authentication methods.
• Trusted domains for inline frames—Review and update the list of trusted domains for clickjack protection. In particular, ensure that *.my.salesforce.com is trusted.

If you have Experience Cloud sites the My Domain change included deploying enhanced domains, complete this task.

• Network restrictions that use IP allowlists only—If users on your network can’t access your .my.site.com URL, allowlist that domain, disable the Salesforce CDN for that URL, or serve your site via a custom domain.

If a custom domain such as https://www.example.com serves your Experience Cloud sites or Salesforce Sites and the sites URL changed, complete these tasks.

• The custom domain uses the HTTPS Option: Use a third-party service or CDN to serve the domain—Update the target host name used when forwarding requests from your domain’s proxy or CDN.
• The custom domain serves the site via a non-Salesforce host or service—Review and update the domain configuration, such as CDN settings and hard-coded references to Salesforce URLs.