Moving a business to a new domain affects redirects, email, analytics, ownership, and recovery. Use this checklist to keep the old and new domains working together.
Changing a business domain can look like a branding decision. In practice, it is also a website migration, an email migration, an analytics change, an identity update, and a risk-management project. A recent Domain Name Wire episode described two businesses that moved to .ai domains. Pedra had started on .so and later selected Pedra.ai.
Swipe had launched under a name that no longer matched its broader ambitions, then acquired Swipe.ai through a lease-to-own arrangement. Those stories do not mean every company should change domains or choose the same extension. They do show why the operational plan matters as much as the new name.
A strong domain will not protect a business from broken redirects, lost email, missing analytics, unclear ownership, or an expired fallback domain. A domain change is several migrations at once Before changing the primary domain, name the systems that depend on the old one.
The list often reaches far beyond the website: Public pages, landing pages, files, and subdomains Employee and shared email addresses Password resets, account notifications, and single sign-on Search Console, analytics, advertising, and conversion tracking Certificates, DNS records, APIs, webhooks, and third-party integrations Invoices, contracts, social profiles, app listings, and printed material Registrar access, renewal responsibility, and recovery contacts The safest plan treats each dependency as a named workstream with an owner, a test, and a rollback step.
Business domain change continuity checklist 1. Confirm control before announcing the move Verify the registrant, registrar account, transfer status, renewal date, nameservers, DNS access, and recovery contacts for both domains.
ICANN advises organizations to keep domain and DNS administration inside their risk-management program and to avoid leaving the registrant role with a developer, hosting provider, or other third party.
If the new domain is being acquired through lease-to-own, document who controls DNS during the term, whether transfers are restricted, what happens after a missed payment, how renewal is handled, and when full ownership transfers. A memorable domain is not ready to become a primary business asset until the control path is clear. 2. Inventory every use of the old domain Create a working inventory before changing DNS.
Crawl the website, export known URLs, list subdomains, search application settings, review email groups, and inspect third-party tools. Include less obvious uses such as password-reset senders, OAuth callbacks, webhook targets, tracking allowlists, API documentation, support links, QR codes, and downloadable files. Mark each item as migrate, redirect, retain, or retire.