Salesforce My Domain Change Project Checklist
Updated: Feb 15
Example My Domain Change 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 hostnames that 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 hostnames.
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 hostnames.
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.
Enable My Domain hostname redirection logging.
To get a more complete view of the hostnames being redirected for your org, schedule a daily query of the Hostname Redirects event type via REST API. For example, you can configure a cron job in Unix or a scheduled task in Windows to run the query. Then monitor hostname redirections, and determine when to disable redirections.
Disable redirections (optional).
Update your org to remove references to your old hostnames.
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.
If your org was created without enhanced domains, complete the Deploy Enhanced Domains release update.
