Website migration
Move your site one piece at a time.
Six chapters on running two systems behind one domain, moving a platform in phases, and finishing the job. With route tables, batch checks and a retirement run sheet.
To move a website in stages, put a reverse proxy in front of your domain, send each path to the old or the new system from a written route table, and check every batch on the public domain before you start the next. It suits large sites and sites with parts that cannot move yet. Most small and medium sites should move all at once. It carries no ranking guarantee, and it adds a live system someone has to own until the old site is retired.
Chapters
Read it in order,
or jump in.
- 01
When a full cutover is wrong
Most sites should switch in one go. Here are the few real reasons not to, the options that sit between the two, and what running two systems costs you each week.
6 min - 02
Reverse proxy setup in plain words
Three hostnames, one route table and a few settings that decide if it works. How to plan the setup, what Webflow asks for, and how to test it before real traffic arrives.
7 min - 03
SEO parity for each page
In a staged move, every batch is a small launch. What to capture before you switch a route, what to compare after, and the gate each batch must pass before the next one starts.
6 min - 04
Forms, tracking and sign-in across two systems
Search engines are not the only ones crossing between systems. How to keep leads, data, consent and logins working when a visitor moves between two platforms on one domain.
6 min - 05
Moving platforms in phases
Sometimes a site should change platform more than once, or change one layer at a time. How to set up phases that each stand on their own, with Webflow to Astro and Sanity as the example.
7 min - 06
Retiring the old site
A staged move ends only when the old system is gone, or when you decide on purpose to keep it. How to prove nothing depends on it, switch it off in order, and remove the proxy.
6 min
What you get
6 chapters that each end with a clear next move.
- Switch everything at once unless a named part of the site cannot move in time.
- Each system gets its own origin hostname, and the public domain points at the proxy.
- With unchanged URLs, nothing warns you when a page loses its title, so compare each one yourself.
- Behind one proxy, the browser sees one site, so cookies and storage are shared between systems.
- Change one thing per phase, and finish each phase in a state you could stay in.
- Keeping two systems can be right, as long as it is a decision with an owner.
Who it is for
Marketing leads and developers on larger sites, or sites with parts that cannot move yet, who are planning a staged move or a platform change in phases.
Planning a staged move? Book a free 20 minute callKeep a copy
Take the whole guide
as a PDF.
It all stays free to read here. If you want a copy for your team, leave your email and the download link shows up right away.
Thanks. Use it, share it, and tell us what is missing.
Download the PDFDownload the PDFFAQs
Questions
people ask.

It means moving a site in parts. Usually a reverse proxy sends each URL to the old or the new system, so both stay live on one domain while pages move in batches. It can also mean changing platform in phases, with one system live at a time.
Most small and medium sites should move all at once. Google recommends that in its site move guide, and says large sites can move a section at a time. Stages make sense when a named part of the site cannot move in time. Chapter 1 has the tests.
Not by itself, if it is set up well. Search engines see one domain and the same URLs. Trouble comes from leaked origin hostnames, wrong canonicals, broken status codes and outages. No one can guarantee rankings during a move, so check each batch.
Webflow says it does not support third-party proxies, and its help article sends Enterprise customers to Sales. The article lists a paid Site plan and a connected domain as needed. Do not proxy a webflow.io address, as Webflow says that is not supported and breaks its terms. Check the current docs.
The Site Move Playbook is for a move that happens all at once, from first decision to the first 30 days after launch. This guide is for what is different when two systems run together, or when a move happens in phases.
There is no fixed limit, but the cost keeps running: two sets of menus, tracking and plans, and a proxy to own. Set an end date before you start. If part of the site should stay on a second system for good, make that a decision with an owner.
A developer who has worked with proxies and DNS can. Marketing teams can run the batch checks in this guide, but someone technical has to own the proxy. If you want a second opinion, send us your site and tell us which parts cannot move yet.


