top of page
  • Writer's pictureshannan

Salesforce My Domain Change Post-Deployment Checklist

Example Post-Deployment Checklist

Salesforce My Domain Change Post Deployment Checklist

  • Incomplete pre-deployment tasks—Review the pre-deployment update checklist, and complete any incomplete tasks.

  • 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 hostnames.

  • 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 hostnames, such as na87.salesforce.com. Ideally, generate the hostname via a dynamic method, such as the DomainCreator class in Apex. If you deployed enhanced domains, review the hostname redirections that stop in Winter ’25. If you find any of those hostname 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 hostnames that no longer apply to your org from your trust settings. However, we recommend that you allow those hostnames 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 use a command-line interface such as Salesforce CLI.

  • 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.

  • Messaging for In-App and Web—To update your Messaging for Web configuration with your new URLs, republish your Messaging for Web deployment.

  • Knowledge articles served on your *.my.salesforce.com URL—Update hard-coded references to the knowledge article URLs.

  • Identity providers on your login page—Update your identity providers to use your new login URL.

  • 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.

  • Service Cloud Voice—When you enable Service Cloud Voice, Salesforce uses your My Domain login URL to configure single sign-on (SSO) to Amazon Connect. Changing your org’s My Domain login URL breaks that configuration and disables Voice. Reconfigure Salesforce Voice, or wait until Salesforce announces a solution to allow you to change your My Domain name without breaking the configuration.

  • Single sign-on for accessing your org—Update authentication.

  • Pardot—If your configuration uses the Pardot Connector User, update the login URL that Pardot uses.

  • 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.

  • Streaming API—Update to use your new My Domain login URL.

  • Third-party connected 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 this task.

  • Service Cloud Voice—Add your new Visualforce page format to the allowlist for Amazon Connect.

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.

  • 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 hostnames.

  • Knowledge articles served on your Experience Cloud sites URL—Update hard-coded references to the knowledge article URLs.

  • Identity providers on your site login page—Update your identity providers to use your new site URL.

  • Messaging for In-App and Web—If you use Messaging for Web 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 connected 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 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: A non-Salesforce host or service serves this domain over HTTPS—Update the target hostname 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.


Recent Posts

See All
bottom of page