The short answer
A move is worth it when the platform itself stops your team from doing work the business needs, and you have tried or priced a fix in place. It is not worth it because the site looks old, because a new tool is popular, or because traffic dipped last quarter. A new look does not need a new platform, and a slow site can often be made quick where it is.
A move always costs something. There is the build, a content freeze, and a stretch when search results move around. Google's own site move guide says to expect temporary fluctuation in ranking during a move. So the question is not "would the new platform be nicer?" It is "what will we be able to do after the move that we cannot do now, and is that worth the cost?"
Fix in place, or move?
Start with the problem, not the platform. Most complaints fall into one of these rows.
| The complaint | Try this first | Move when |
|---|---|---|
| The site is slow | Compress images, remove old scripts and plugins, fix fonts and hosting. See Core Web Vitals. | You have done this and the platform or theme still holds you back. |
| Marketing waits on developers | Build reusable sections and a simple CMS structure on the current platform. | Editors still cannot publish a page safely without help. |
| It breaks after updates | Remove plugins, pin versions, move to better hosting. | Upkeep keeps eating time that should go to new work. |
| It looks dated | A redesign on the same platform. | The design you want cannot be built well on it. |
| We cannot connect our tools | Check for an official app, a script, or a small piece of middleware. See integrations. | The tools you rely on have no sane way to connect. |
| Traffic fell | Find out why first. Look at Search Console by page and query. | Almost never a reason on its own. A move will not fix content or demand. |
| Fees are too high | Check the plan, and cut seats and add-ons you do not use. | The total cost, including people, is clearly lower elsewhere. |
Decision rule Write the problem as one sentence with a person in it: "Our marketing lead cannot publish a landing page without a developer." If you cannot write that sentence, you are not ready to move.
Five questions to score the move
Answer these with your team. Be honest, and write the answers down, because you will need them when the project gets hard and someone asks why you started.
- What can we not do today? Name the work, the person and how often it comes up.
- Have we priced a fix in place? If nobody has asked, ask. It may be a week of work instead of a project.
- How much does the current site earn? Pull clicks, leads and sales by page. The more it earns, the more care the move needs.
- Who owns the move? One person who decides on edge cases and signs off the launch. No owner, no move.
- Is there a quiet window? Avoid your busiest season, a big campaign, or a product launch.
If you get a clear answer to question 1 and a named person for question 4, go on. If question 1 is vague, stay where you are and fix the small things. Coming back in six months costs nothing.
Know which kind of move you are making
"Migration" covers very different jobs, with very different risk. Name yours before you plan anything.
| Kind of move | What changes | Main risk | Google guide |
|---|---|---|---|
| New host, same URLs | Where the site is served | DNS and firewalls blocking crawlers | No URL changes |
| New platform, same URLs | The system, and maybe the HTML | Lost titles, schema, forms and tracking | No URL changes for the host part |
| New platform, new URLs | System and addresses | All of the above, plus broken links | With URL changes |
| New domain | The whole address | All of the above, plus signals moving to a new name | With URL changes and Change of Address |
| Move plus redesign plus new copy | Everything at once | When something drops, you cannot tell why | Split it if you can |
Keeping your URLs is the biggest risk you can remove. On one revamp we kept the same URLs, titles, meta, schema and internal links, so the design could change without search engines having to learn a new site.
Decision rule Change as few things at once as the goal allows. A new platform with the same URLs and the same copy is a far safer project than a new platform, new URLs and new words. Rewrite the copy after the move has settled.
All at once, or in stages?
Google's site move guide recommends that small and medium sites move all URLs at the same time, and says larger sites can move one section at a time. For most marketing sites, the answer is one go.
Stages make sense when the site is very large or when some part cannot move yet. A reverse proxy can serve pages that are not moving yet under your domain, so it all reads as one site. That is real extra work and someone has to own it for as long as it runs. Our post on moving a site in stages covers the trade-offs.
| Choose | If |
|---|---|
| All at once | The site is small or medium, and you can freeze content for the last days of the build. |
| In stages | The site is large, a section depends on a system you cannot replace yet, and someone will own the proxy. |
When to stay put
Say no to the move if any of these is true. It is a real answer, and often the right one.
- The goal is a new look, and your platform can build it.
- You have a launch or your best sales season in the next two months.
- Nobody can spend time on content checks and sign-off.
- The real problem is the offer or the copy, not the site.
- You would be moving because a tool is new, with no job it does better for you.
If you are still choosing a platform, our comparisons are a good next read, for example Webflow vs WordPress.
Write a one-page move brief
Before anyone starts a crawl, put this on one page. It keeps the project honest and gives you something to check the launch against.
- The problem, in the one sentence from above.
- The move, by kind: host, platform, URLs, domain.
- What stays the same. URLs, copy and design, wherever you can.
- The owner, and who signs off content, SEO, forms and tracking.
- The window, with launch dates to avoid.
- What you will watch afterwards, and for how long. Chapter 6 has the list.
If you want a second pair of eyes on it, see our WordPress to Webflow and Webflow to Astro services, or the full list of moves on our services page.


