Migration is the least glamorous web project and the one with the most ways to go badly. Nothing about it is visible when it works, and everything about it is visible when it does not.
The word also covers several different jobs. Moving a WordPress site to new hosting is routine. Moving to WordPress from another platform is a rebuild wearing a migration label. Moving away from WordPress is a different rebuild again. They carry different risks and it is worth being precise about which one you are doing.
This covers all three, what actually breaks, and how to decide whether the move is worth making. If you want it handled, our WordPress development service does migrations regularly, so request a quote with your current setup.
Three Different Jobs, One Word
Host to host is routine
Same platform, same site, new server. Predictable, quick, and the main risks are DNS timing and email. Anyone competent can do this and it should not be expensive. The one thing worth insisting on is a tested rollback.
Onto WordPress from another platform
This is a rebuild. Content can usually be imported, but design, functionality and integrations do not transfer. They are recreated. Anyone describing this as a straightforward import is understating it. It is the same effort as a new build plus the content mapping.
Away from WordPress
Also a rebuild, and often a bigger one, because WordPress sites accumulate plugin functionality nobody has documented. The forms, the redirects, the membership logic and the custom fields all have to be identified before they can be replaced. Moving to Webflow or Shopify is very achievable; assuming it is a data transfer is where projects get into trouble.
Multisite, multilingual and membership
Any of these multiplies the work substantially. Multilingual sites carry per-language URL structures that must all be mapped. Membership sites carry user accounts and access rules, and moving those involves people’s credentials and data rather than just content. Neither is a reason not to migrate; both are reasons to scope carefully.
What Actually Breaks
In order of how often we find it, and how much it costs when nobody checked:
URLs and redirects
The single biggest cause of traffic loss. Every URL that changes needs a permanent redirect to its closest equivalent. On a large site this means an actual mapping exercise, not a wildcard rule to the homepage. Search engines treat that as a soft error and it sends every visitor to the wrong place.
Media library paths
Images referenced by absolute URLs break silently when the domain or directory changes. The page still loads; the pictures do not. Because nothing errors, this can survive undetected for weeks.
Forms and their destinations
Contact forms usually survive the move and quietly stop delivering, because the notification address, the SMTP configuration or the spam integration did not come with them. Always submit a real test through every form after launch. Silent form failure is the most expensive migration bug because you cannot see the enquiries you are not receiving.
Scheduled tasks
Anything running on a schedule, including backups, feeds, syncs and abandoned-cart emails, needs reconnecting. These fail invisibly by definition.
Email deliverability
Moving hosting frequently changes the sending IP or configuration, and mail starts landing in spam folders. Worth checking authentication records before and after rather than discovering it from a client who says they never got your reply.
SSL, mixed content and the trailing details
Certificates, canonical protocol, trailing-slash consistency and the sitemap all need attention. Individually minor; collectively enough to make a clean migration look shaky.
How a Migration Should Be Run
There is no clever method here. There is a sequence, and the discipline to follow it.
- Inventory first. Every URL, every form, every integration, every scheduled job, every plugin doing something functional rather than decorative.
- Baseline the current site for traffic, rankings and conversions, so you can tell afterwards whether anything changed.
- Build and populate a staging environment that search engines cannot index.
- Map the redirects from the URL inventory, page by page, before launch rather than after.
- Test everything a user can do, especially forms and checkout, with real submissions.
- Launch, then verify: redirects firing, tracking live, indexing unblocked, sitemap submitted.
- Watch for a month. Most migration damage surfaces within four weeks and is cheap to fix if caught.
Keep the old site until you are certain
Retain a full backup and, where practical, the old environment, until the new site has been stable for several weeks. This is inexpensive insurance and it is the difference between an inconvenience and an emergency.
Should You Migrate At All?
Migration carries real risk and real cost, so it needs a real reason. These are good ones:
- Your team cannot maintain the current site without a developer for routine changes.
- The platform cannot do something the business now needs.
- Hosting or security has become a recurring problem rather than an occasional one.
- Maintenance is consuming more than the migration would cost.
And these are not
Wanting a fresh look, which a redesign handles without moving platform. Disliking the admin interface, which is usually familiarity rather than capability. Or a general sense that something newer would be better. That is the most expensive reason of all, because it produces a project with no measurable finish line.
The honest recommendation is often to stay
WordPress runs an enormous share of the web competently. If your objection is that the site is slow, that is usually fixable in place. If it is that the site looks dated, that is a redesign rather than a migration. We will tell you when staying put is the right answer, so book a free consultation and we will look before recommending.
Frequently Asked Questions
Will migrating my WordPress site affect SEO?
It should not, if URLs are preserved or properly redirected and the content survives intact. Traffic loss after a migration is nearly always caused by missed redirects, deleted pages, or a staging environment launched with indexing still blocked.
How long does a WordPress migration take?
A host-to-host move of a straightforward site is quick. A platform change is a rebuild and takes as long as a rebuild. The variables are the number of URLs, the amount of custom functionality, and whether anyone documented what the plugins actually do.
Will my site go down during the migration?
It should not. The new environment is built and tested before anything switches, and the changeover is a DNS change. There is a short propagation window during which some visitors see the old site and some the new, which is why launches are usually scheduled for quiet periods.
Can you move my site off WordPress?
Yes, most commonly to Webflow or Shopify. Treat it as a rebuild rather than a transfer: content moves, functionality is recreated. The first task is always identifying every plugin doing something functional, because that is the work nobody remembers to scope.
What happens to my plugins?
On a host-to-host move they come with you. On a platform change they do not exist, and each one has to be replaced with a native feature, a third-party service or custom development. This is usually the largest single piece of migration scoping.
Do I need to keep the old site?
Keep a full backup, and ideally the old environment, for several weeks after launch. Most problems surface in the first month, and having somewhere to check what the previous behaviour was makes them far quicker to fix.
Can you migrate a WooCommerce store?
Yes, though ecommerce raises the stakes: products, variants, customer accounts, order history and payment configuration all have to survive. Live stores are usually migrated with a freeze window on order processing. Tell us your setup and we will scope it.
Get the Migration Scoped Properly
Send us your current setup and where you want to end up, and we will scope the work properly, including saying if you should stay where you are. Request a quote.
Our WordPress design and development service covers migrations, rebuilds and ongoing support. For a look at your site before you commit to anything, book a free consultation.