Changing a SaaS domain affects more than the public homepage. Existing sessions, authentication redirects, payment returns, shared study links, email actions, and browser policies may all refer to the old origin.
Inventory those dependencies before changing DNS. The migration should preserve the intended customer path or give a clear transition, with an explicit plan for links that cannot simply redirect.
Map every domain-dependent surface
List public pages, authenticated routes, API endpoints, cookies, callback allowlists, webhook destinations, email templates, file URLs, shared links, analytics, monitoring, and provider dashboards. Distinguish server-to-server callbacks from browser navigation.
Review the relevant identity, hosting, and payment provider documentation for the actual configuration. Avoid assuming that a redirect at the old homepage fixes every callback or preserves every session across origins.
Rehearse a fictional study-domain move
Suppose a study product moves from an initial launch domain to a permanent brand domain. Existing founders have private dashboard bookmarks, while respondents hold public study links sent weeks earlier.
Test a signed-in founder, a signed-out founder, an old respondent link, an invitation or recovery link, a checkout return, and a provider event destination. Verify the resulting account and study identity after navigation, not just whether a page loads.
Decide what happens to old links: preserve, redirect with validated path handling, or show an explicit migration notice where necessary. Do not convert arbitrary redirect parameters into an open route to untrusted destinations.
Plan coexistence and observation
Keep the old domain under organisation control for the required transition period and monitor relevant errors. Confirm certificate, DNS, and provider configuration changes through the chosen hosting process. Exact propagation and cache behaviour should be observed rather than promised as a universal duration.
Communicate whether users will need to sign in again and which messages are legitimate. Support should know the migration dates and safe domains so customers can distinguish expected changes from suspicious links.
The tradeoff is a quick cutover versus compatibility work. Supporting both domains temporarily can reduce broken links but introduces duplicate configuration and origin behaviour to manage. A simpler forced transition may fit a small private pilot if users are informed and the constraints are accepted.
The StackFlight portfolio account supplies related shared-link and authenticated-workspace context. This domain move is fictional and makes no claim about its deployment history.
Questions about SaaS domain changes
Will existing sessions always survive?
Do not assume so. Session and cookie behaviour depends on the actual origins and authentication configuration. Test representative accounts.
Is a homepage redirect sufficient?
No. Verify shared paths, callbacks, email actions, API requests, and provider destinations separately.
What should the migration review include?
Include the dependency inventory, old-link policy, account checks, cutover steps, observation, and recovery owner. Bring gaps to a domain-migration review.