Website Migration
Move the website without losing track of what depends on it
A migration can mean moving hosting, changing platforms, or changing a domain. Before anything is moved, identify what must carry over and decide what a successful cutover looks like.
Protect your domain, email, and important links as separate items
Moving the site does not automatically mean moving every service that uses the domain. Document where the domain and DNS are managed, where email is delivered, and where the site is hosted. Be clear about which provider is changing. The migration plan should flag which people and systems need to work before the switch can be called complete.
What to verify before, during, and after a move
Use a small set of business-critical checks rather than relying on whether the homepage alone appears.
- Before switching
Make a source inventory and test the destination. Check forms, downloads, logins, redirects, and other important paths that apply to the site.
- At the switch
Confirm which records can still change and make the agreed updates. Keep the old setup accessible according to the recovery plan.
- After switching
Recheck real entry URLs, transactions, and email. Record the problem and exact affected step if any check fails.
Put old and new addresses next to each other
A page name change can affect links already in ads, emails, search, or booking instructions. Compare the source and destination page lists. Preserve an address when it still makes sense, and redirect moved pages to the relevant replacement when there is one. Flag pages without an equivalent separately. It is easier to spot a missed path with an actual map than with a single general rule.
Decide what happens to new activity during the move
A basic informational site may be stable while a copy is prepared. A membership site, active booking system, or store can receive new records while you test. Decide which copy takes new activity, whether data needs a final sync, and when it is appropriate to restrict changes. Verify important counts and a few current records using a safe test.
Agree on a decision point before launch day
Identify the tests that must pass and who can approve the switch. Keep access to the previous environment through the agreed recovery period. If something unexpected appears, a clear cutover checklist makes it easier to determine whether the issue belongs to the new site, a redirect, email, or another connected account.
Bring the move you have in mind
Share the current site and which pieces you plan to change. Include any active bookings, account access, or sales that the project must protect.
Inventory the dependencies
Identify pages, media, forms, accounts, DNS records, and email services. A site may rely on subscriptions, add-ons, scheduled jobs, or integrations that are easy to overlook while looking only at the home page.
Rehearse the move
Work from a current backup and test a staging copy where possible. Decide how updates that happen during the move will be handled. Check links, downloadable files, internal search, and any booking or payment path.
Keep a recovery plan
If URLs change, put redirects in place and update links to use their new destinations. If hosting or DNS changes, make sure email settings are accounted for. Agree on when to roll back and who needs access to do it.
What to bring
Bring both the current and target environments, if selected, and identify the services that cannot be interrupted. Do not send passwords in an inquiry.
Common questions
Can I move a site and keep its domain?
Yes. A host or platform move does not require changing the domain. A domain change introduces additional redirect and verification work.
Can you guarantee there will be no downtime?
No. Downtime risk depends on the setup. Testing, a cutover plan, and a known rollback path can reduce it.
Tell us what you want to do
Bring a goal, a website address, or the problem you are trying to solve.
