A custom-domain cutover is a change to an existing service boundary. Write the destination, current state and rollback before editing DNS or a hosting association.
Identify what already serves the address
Record the exact hostname, the current provider and any related services. A screenshot of one DNS row is not a complete dependency map. Include the hosting-side association and certificate status as well as the zone record.
Do not assume that a new storefront has permission to replace every subdomain of a merchant's domain.
Verify the destination independently
Check the new build on an appropriate protected or temporary address before directing customer traffic to it. Verify the intended merchant, assets, product routes and backend connection. A successful homepage build does not prove checkout or order lookup works.
Keep test activity read-only unless real transactions are explicitly authorised. Do not create customer orders merely to make a launch checklist green.
Define the exact change
Write which record or association will be created or changed, who will do it and what must remain untouched. Include email-related and unrelated application records in the preservation boundary.
Avoid giving a generic DNS command without the provider's actual instructions. The required record depends on the hosting setup; an example from another store is not a safe substitute.
Prepare rollback as an operation
Record the previous values and the conditions that trigger reversal. Distinguish reversing traffic from undoing data written after launch. Moving a hostname back does not automatically erase orders or restore a database.
Assign an observer who can check both the new storefront and any service that must remain available. Include the certificate and customer-facing routes, not just whether a name resolves.
Close only after the real hostname works
Check the live address after the change and record the observed result. Allow for the actual provider and resolver behaviour without promising an exact universal propagation time.
If URLs change, search continuity needs its own mapping and monitoring. Google's migration guidance separates preparation, URL mapping, redirects and observation. Google site-move guidance
Use the store evaluation guides to ensure the destination is ready before the domain becomes the next avoidable emergency.
Illustrative case to check
A shop already uses its main domain for marketing and a separate hostname for orders. The new storefront is intended for only one address. Write that exact boundary and preserve the other service. A successful new build does not authorise replacing a wildcard or the entire zone. Have the operator confirm the smallest required change and retain evidence of both services before and after it.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store