Example My Domain Change Project Checklist

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 and Japanese only). For more information on each of these steps, see Plan for a My Domain Change.

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 Project Checklist

Prepare for and schedule the change.

• If your project includes deploying enhanced domains, review the considerations for the feature, and join the Trailblazer Community group.
• Review the My Domain provisioning and deployment process.
• Determine the host names that change.
• Note whether your login URLs change.
• 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.
• Review recommended practices, 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 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 to serve your sites (optional).
• Share test plans and issue reporting instructions with testers.
• Verify that users can access the sandbox.
• Preserve login access for your sandbox.
• Update your sandbox with changes that can be made before you deploy the My Domain change.
• Save the change to your My Domain details in your sandbox.

Test in a sandbox.

• Deploy the change in your sandbox.
• Update authentication for your sandbox.
• Disable redirections for testing.
• Run automated tests, if applicable.
• Update your sandbox with changes that can be made only after you deploy the My Domain change.
• Test in your sandbox. Use your test plan.
• Record changes made to resolve issues.
• Re-enable redirections (optional).

Prepare to update production.

• Notify 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 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 access to production.
• Save the change to your My Domain details in production.

Update production.

• Deploy the change in production.
• Update authentication in production.
• Update 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 for testing.
• Run automated tests, if applicable.
• Test in production. Use your test plan.
• If your brand changed, update your My Domain login page and update your Experience Cloud site login page.
• Re-enable redirections (optional).

Post-deployment adoption.

• Notify users and customers about the change.
• Enable My Domain host name redirection logging, and schedule a daily query of the Hostname Redirects event type.
• Monitor host name redirections, and determine when to disable redirections.
• Disable redirections (optional).
• Update your org to remove references to your old host names.
• If your org was created without enhanced domains, disable redirections for non-enhanced domains.
• If you don’t want users to access Salesforce from your old My Domain URLs, remove your previous My Domain.