--- schema_version: "1" id: 6280ec7087f7497868e9245f9bcdce0a622a4dbdbd152ad9347e4536c58b3ba7 title: Example My Domain Change Project Checklist collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/domain_name_plan_checklist_project.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan_checklist_project.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 62cb99ed2321cc1bff444a3d56613409a4582300631463ea610d2010aacb71e4 description: The items on this list help with planning, scheduling, and performing a My Domain change. products: - Salesforce Platform - Cross Cloud release: "264" --- # Example My Domain Change Project Checklist The items on this list help with planning, scheduling, and performing a My Domain change. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
Each company and configuration is different. Use this checklist as a starter when you develop the plan for your My Domain change. Optionally, to create your own version of this checklist, use the My Domain Change Checklist Templates in Quip (available in [English](https://salesforce.quip.com/790aAYs5A0Br) and [Japanese](https://salesforce.quip.com/4eyuAgnfQlYQ) only). For more information on each of these steps, see [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."). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png) Note Enhanced domains were enforced in Winter ’24. For more information, see [Enhanced Domains Timeline](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_enhanced_timeline.htm&release=264.0.0&type=5 "To prevent disruption for your customers and users, review the enhanced domains timeline and prepare for upcoming changes. Redirections for legacy host names stopped in production and demo orgs in Spring ’26. And in Winter ’27, Salesforce ends support for API traffic that uses an incorrect instanced URL."). To assist customers who continue to test after deploying enhanced domains, these checklists include steps that are specific to that change. ## Example Project Checklist [Prepare for and schedule the change](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."). - If your project includes deploying enhanced domains, review the [considerations](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_enhanced_considerations.htm&release=264.0.0&type=5 "Before you enable and deploy enhanced domains, understand the prerequisites. Learn about how URLs, including public-facing URLs, change across your org with enhanced domains. Review recommendations for preserving access to your org during the change, learn about redirections, and understand how enhanced domains improve your Experience Cloud sites.") for the feature, and join the [Trailblazer Community group](https://trailhead.salesforce.com/trailblazer-community/groups/0F94S000000kF9qSAE). - Review the My Domain [provisioning and deployment process](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_setup.htm&release=264.0.0&type=5 "Understand the provisioning and deployment process when you deploy a change to your org’s My Domain. Learn about how each step of the process impacts your user’s access to Salesforce and why it’s important to test these changes in a sandbox."). - Determine the [host names](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_app_url_changes.htm&release=264.0.0&type=5 "Your My Domain name is a subdomain used in login URL and application URLs across your Salesforce org, including sites and Visualforce pages. Understand what determines your org’s URL formats and the structure of those formats.") that change. - Note [whether your login URLs change](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_auth_update_determine.htm&release=264.0.0&type=5 "If your My Domain login URL or site URL changes, authentication updates are required. Determine whether these changes apply to your My Domain change. Then understand the types of updates required."). - Create an inventory of hard-coded URLs that point to the org where you plan to deploy the My Domain change. - Identify the features that [require an 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."). - Review [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."), and identify any additional changes. - Identify participants: update owners, testers, communication owners, and go-live participants. - Identify any features covered by automated tests. - Create a test plan. - Determine how to capture testing results. - Develop a communication plan. - Create a go-live plan. - Develop a rollback plan. - Identify or create a sandbox for testing. - Determine your target project dates and dependencies. - Choose your testing and deployment windows. - Finalize and share your schedule. Prepare to test in a sandbox. - Review the [recommended steps](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.") to take before and after you deploy a My Domain change. - Replace login references with dynamically created host names. - Review and document your current My Domain configuration. - If your login or site URLs change, document your authentication configuration. - Configure a [custom domain](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt.htm&type=5&language=en_US) to serve your sites (optional). - Share test plans and issue reporting instructions with testers. - Verify that users can access the sandbox. - [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. - [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 you deploy the My Domain change. - [Save](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.") the change to your My Domain details in your sandbox. Test in a sandbox. - [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. - [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. - Disable [redirections](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections.htm&release=264.0.0&type=5 "When you deploy a change to your My Domain, Salesforce redirects multiple host names automatically. Learn about the types of redirections, how to log redirections for the host names that Salesforce hosts for your org, and how you can control these redirections.") for testing. - Run automated tests, if applicable. - [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 only after you deploy the My Domain change. - [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. Use your test plan. - Record changes made to resolve issues. - Re-enable [redirections](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections.htm&release=264.0.0&type=5 "When you deploy a change to your My Domain, Salesforce redirects multiple host names automatically. Learn about the types of redirections, how to log redirections for the host names that Salesforce hosts for your org, and how you can control these redirections.") (optional). Prepare to update production. - [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. - Update your go-live plan based on testing results. - Replace login references with dynamically created host names. - Review and document your current My Domain configuration. - If your login or site URLs change, document your authentication configuration. - [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 you deploy the My Domain change. Refer to the list of changes made during testing. - [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.") access to production. - [Save](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.") the change to your My Domain details in production. Update production. - [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. - [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. - [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. Refer to the list of changes made during testing. - Disable [redirections](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections.htm&release=264.0.0&type=5 "When you deploy a change to your My Domain, Salesforce redirects multiple host names automatically. Learn about the types of redirections, how to log redirections for the host names that Salesforce hosts for your org, and how you can control these redirections.") for testing. - Run automated tests, if applicable. - [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. Use your test plan. - If your brand changed, [update your My Domain login page](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_login_branding.htm&release=264.0.0&type=5 "My Domain gives you a point-and-click way to brand the page that prompts users to log in to your Salesforce org. You can replace the Salesforce logo with your own and change your background and login button colors. You can also display content to the right of your login form. Branding options apply to the entire login experience, including pages for users to verify their identity and reset passwords. They also apply to login flows.") and [update your Experience Cloud site login page](https://help.salesforce.com/s/articleView?id=experience.external_identity_customize_community.htm&type=5&language=en_US). - Re-enable [redirections](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections.htm&release=264.0.0&type=5 "When you deploy a change to your My Domain, Salesforce redirects multiple host names automatically. Learn about the types of redirections, how to log redirections for the host names that Salesforce hosts for your org, and how you can control these redirections.") (optional). Post-deployment adoption. - [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 about the change. - Enable My Domain host name [redirection logging](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections_log.htm&release=264.0.0&type=5 "To reduce disruption, Salesforce redirects multiple host names automatically when you deploy a change to your My Domain. To track blocked and successful redirections for your My Domain host names, enable event logging for these redirections."), and schedule a daily query of the Hostname Redirects event type. - Monitor [host name redirections](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_hostnameredirects.htm), and determine when to disable redirections. - Disable [redirections](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections.htm&release=264.0.0&type=5 "When you deploy a change to your My Domain, Salesforce redirects multiple host names automatically. Learn about the types of redirections, how to log redirections for the host names that Salesforce hosts for your org, and how you can control these redirections.") (optional). - [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 org to remove references to your old host names. - If your org was created without enhanced domains, disable [redirections for non-enhanced domains](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections_non_enhanced.htm&release=264.0.0&type=5 "After enhanced domains deployment, your previous non-enhanced host names were redirected. In Winter ’25, Salesforce stopped redirections for legacy (non-enhanced) My Domain URLs in Developer Edition orgs, patch orgs, scratch orgs, Trailhead Playgrounds, and existing sandboxes. Redirections for those legacy URLs stopped in Spring ’26 in all orgs, including production orgs. If your org was created before October 2020, Salesforce also stopped redirections for host names that contained your instance name but not your My Domain. And in Winter ’27, support ends for incorrect instanced URLs in API calls. Review the affected host names and how to test for the end of these redirections."). - If you don’t want users to access Salesforce from your old My Domain URLs, [remove](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_remove_previous.htm&release=264.0.0&type=5 "Each time that you deploy a change to your My Domain, Salesforce redirects requests from your previous My Domain URLs to your current My Domain. Optionally, disable redirections from your previous My Domain. We recommend that you use that option when you test a My Domain change. Or, to use your previous My Domain in a different Salesforce org, remove your previous My Domain.") your previous My Domain. #### See Also - [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.") - [Example My Domain Change 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.")