--- schema_version: "1" id: 88ce10d73386ac6a3764e86f951d23238386655f021a2bff7bde7dfd15071d40 title: Understand the My Domain Change Process collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/domain_name_plan_process.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_process.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: ae273fc57d9ed65afde0c87cece270c898a1a965bfae764037d8d4215bead94a description: Review the high-level process to successfully deploy a change to your My Domain. The change can include a My Domain name change, enhanced domains, or partitioned domains. products: - Salesforce Platform - Cross Cloud release: "264" --- # Understand the My Domain Change Process Review the high-level process to successfully deploy a change to your My Domain. The change can include a My Domain name change, enhanced domains, or partitioned domains. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
Here’s the step-by-step process to enable, test, and deploy a change to your My Domain. 1. Review the [recommended practices](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_recommendations.htm&release=264.0.0&type=5 "Before you deploy a change to your My Domain, consider configuring a custom domain to serve your sites, and review your My Domain settings. Review recommendations for testing and go-live plans. Understand the steps that you can make only after you deploy a My Domain change, and follow recommendations to minimize disruption during your deployment. After you complete testing, notify users, enable redirection logging, and determine when to disable redirections.") for a My Domain change. 2. [Prepare for and schedule](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_prepare.htm&release=264.0.0&type=5 "To prepare for a My Domain change, first gather the key information: the required updates, testing, and participants. Then review the deployment process for a My Domain change, identify your testing environment, and schedule your testing and production deployment.") your change. 3. Review the [example checklists](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_checklists.htm&release=264.0.0&type=5 "Review example checklists for a My Domain change, including a project checklist, pre-deployment checklist, and post-deployment checklist."). 4. Prepare to test in a sandbox. 1. Follow the [recommended practices](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_recommendations.htm&release=264.0.0&type=5 "Before you deploy a change to your My Domain, consider configuring a custom domain to serve your sites, and review your My Domain settings. Review recommendations for testing and go-live plans. Understand the steps that you can make only after you deploy a My Domain change, and follow recommendations to minimize disruption during your deployment. After you complete testing, notify users, enable redirection logging, and determine when to disable redirections.") before a My Domain change. 2. Save the [change to your My Domain details](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_rename.htm&release=264.0.0&type=5 "If you don’t like your My Domain or circumstances warrant a change, you can rename it. For example, you can change the name when your company’s name or branding changes. In some orgs, the admin can also choose a different domain suffix, enable enhanced domains, and remove instance names from certain My Domain URLs.") in the sandbox. 3. [Preserve login access](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_login_change_preserve_access.htm&release=264.0.0&type=5 "When your My Domain or site login URL changes, two multi-factor authentication (MFA) verification methods stop working: built-in authenticators and security keys. Without those methods, single sign-on (SSO) can also stop working. To preserve admin access to Salesforce and prevent end-user frustration, verify your backup authentication methods. In preparation for your My Domain change, determine the post-deployment steps to reestablish authentication for your org, including resetting the affected verification methods for your users.") for your sandbox. 4. [Update](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_guidelines.htm&release=264.0.0&type=5 "When you deploy a change your My Domain, your Salesforce org’s login URL and application URLs change. URLs that are dynamically constructed—for example, URLs generated via the DomainCreator Apex class—use the new URLs automatically. However, some Salesforce functionality requires an update to work with your new URLs. Similarly, custom code, your network configuration, and third-party integrations that use the old URLs require updates. To ensure a smooth transition to your new URLs, update references to your old URLs.") your sandbox with changes that can be made before deployment. 5. Test in a sandbox. 1. [Deploy](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_testing_and_rollout.htm&release=264.0.0&type=5 "After you change your My Domain and Salesforce provisions those changes, deploy your org’s new My Domain. Only after you deploy your new My Domain can you test your new URLs. And your users can’t use the new My Domain URLs until you deploy the updated My Domain.") the change in your sandbox. 2. [Update authentication](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_auth_update.htm&release=264.0.0&type=5 "Determine whether your My Domain change requires that you update your authentication settings. Then learn about the authentication settings that can be impacted after a My Domain change and make the required updates. If your My Domain login host name or sites host name changed when you deployed a My Domain change, update your authentication settings.") for your sandbox. 3. [Update](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_guidelines.htm&release=264.0.0&type=5 "When you deploy a change your My Domain, your Salesforce org’s login URL and application URLs change. URLs that are dynamically constructed—for example, URLs generated via the DomainCreator Apex class—use the new URLs automatically. However, some Salesforce functionality requires an update to work with your new URLs. Similarly, custom code, your network configuration, and third-party integrations that use the old URLs require updates. To ensure a smooth transition to your new URLs, update references to your old URLs.") your sandbox with changes that can only be made after you deploy the My Domain change. 4. [Test](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_test.htm&release=264.0.0&type=5 "Follow these guidelines to test My Domain changes and to ensure a smooth transition to the new My Domain URLs.") in your sandbox. 5. Follow the [recommended practices](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_recommendations.htm&release=264.0.0&type=5 "Before you deploy a change to your My Domain, consider configuring a custom domain to serve your sites, and review your My Domain settings. Review recommendations for testing and go-live plans. Understand the steps that you can make only after you deploy a My Domain change, and follow recommendations to minimize disruption during your deployment. After you complete testing, notify users, enable redirection logging, and determine when to disable redirections.") after a My Domain change. 6. Prepare to update production. 1. Follow the [recommended practices](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_recommendations.htm&release=264.0.0&type=5 "Before you deploy a change to your My Domain, consider configuring a custom domain to serve your sites, and review your My Domain settings. Review recommendations for testing and go-live plans. Understand the steps that you can make only after you deploy a My Domain change, and follow recommendations to minimize disruption during your deployment. After you complete testing, notify users, enable redirection logging, and determine when to disable redirections.") before a My Domain change. 2. [Notify](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_comms.htm&release=264.0.0&type=5 "A My Domain change can impact users who log in to your Salesforce org, and it can impact external users, such as visitors to your Experience Cloud sites. Review recommendations about communicating to these groups before and after you deploy the change.") users and customers. 3. Save the [change to your My Domain details](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_rename.htm&release=264.0.0&type=5 "If you don’t like your My Domain or circumstances warrant a change, you can rename it. For example, you can change the name when your company’s name or branding changes. In some orgs, the admin can also choose a different domain suffix, enable enhanced domains, and remove instance names from certain My Domain URLs.") in production. 4. [Preserve login access](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_login_change_preserve_access.htm&release=264.0.0&type=5 "When your My Domain or site login URL changes, two multi-factor authentication (MFA) verification methods stop working: built-in authenticators and security keys. Without those methods, single sign-on (SSO) can also stop working. To preserve admin access to Salesforce and prevent end-user frustration, verify your backup authentication methods. In preparation for your My Domain change, determine the post-deployment steps to reestablish authentication for your org, including resetting the affected verification methods for your users.") to production. 5. [Update](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_guidelines.htm&release=264.0.0&type=5 "When you deploy a change your My Domain, your Salesforce org’s login URL and application URLs change. URLs that are dynamically constructed—for example, URLs generated via the DomainCreator Apex class—use the new URLs automatically. However, some Salesforce functionality requires an update to work with your new URLs. Similarly, custom code, your network configuration, and third-party integrations that use the old URLs require updates. To ensure a smooth transition to your new URLs, update references to your old URLs.") production with changes that can be made before deployment. 7. Deploy and test in production. 1. [Deploy](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_testing_and_rollout.htm&release=264.0.0&type=5 "After you change your My Domain and Salesforce provisions those changes, deploy your org’s new My Domain. Only after you deploy your new My Domain can you test your new URLs. And your users can’t use the new My Domain URLs until you deploy the updated My Domain.") the change in production. 2. [Update authentication](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_auth_update.htm&release=264.0.0&type=5 "Determine whether your My Domain change requires that you update your authentication settings. Then learn about the authentication settings that can be impacted after a My Domain change and make the required updates. If your My Domain login host name or sites host name changed when you deployed a My Domain change, update your authentication settings.") in production. 3. [Update](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_guidelines.htm&release=264.0.0&type=5 "When you deploy a change your My Domain, your Salesforce org’s login URL and application URLs change. URLs that are dynamically constructed—for example, URLs generated via the DomainCreator Apex class—use the new URLs automatically. However, some Salesforce functionality requires an update to work with your new URLs. Similarly, custom code, your network configuration, and third-party integrations that use the old URLs require updates. To ensure a smooth transition to your new URLs, update references to your old URLs.") production with changes that can be made only after you deploy the My Domain change. 4. [Test](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_test.htm&release=264.0.0&type=5 "Follow these guidelines to test My Domain changes and to ensure a smooth transition to the new My Domain URLs.") in production. 5. Follow the [recommended practices](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_recommendations.htm&release=264.0.0&type=5 "Before you deploy a change to your My Domain, consider configuring a custom domain to serve your sites, and review your My Domain settings. Review recommendations for testing and go-live plans. Understand the steps that you can make only after you deploy a My Domain change, and follow recommendations to minimize disruption during your deployment. After you complete testing, notify users, enable redirection logging, and determine when to disable redirections.") after a My Domain change. #### See Also - [My Domain](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_overview.htm&release=264.0.0&type=5 "Showcase your company’s brand with a customer-specific subdomain name in your Salesforce org URLs. With My Domain, you can include your company name in your URLs, for example, https://mycompany.my.salesforce.com. With these org-specific URLs, you can set up a custom login page, set a custom login policy, offer single sign-on, and allow users to log in with a social account. My Domain also allows you to work in multiple Salesforce orgs in the same browser at the same time.") - [Plan for a My Domain Change](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan.htm&release=264.0.0&type=5 "Whether you change your My Domain to update your brand, to adopt enhanced domains, or to enable partitioned domains, the URLs that Salesforce hosts for your org change. Those changes can have a large impact, and making the required updates can seem like a daunting project. To make the process as smooth as possible for you, your users, and your customers, review the high-level steps, the recommended practices, and how to reduce the impact on your users and customers.")