A naive search-replace
A plain SQL replace corrupts serialized strings, because the length prefix no longer matches the content. The layout survives the import and breaks on render.
Infrastructure
The files copy easily. The database is where migrations quietly break — and where a careful cutover is worth the planning.
A WordPress migration is a database operation disguised as a file copy. Copy the files, dump the database, and serialized data — theme options, widget settings, page builder content — still points at the old URL. The homepage looks fine, and the builder layout quietly falls apart on the pages that matter.
I copy to staging, run a serialized-safe search-replace, test every template on the new environment before DNS moves, and plan the cutover so the window is short. SSL and redirects are in place before traffic arrives, not after.
A plain SQL replace corrupts serialized strings, because the length prefix no longer matches the content. The layout survives the import and breaks on render.
Themes, page builder data and plugin settings can carry absolute URLs outside the normal siteurl and home options.
An HTTPS redirect added before the certificate is issued produces a redirect loop or a browser warning on the first visit.
A records move but MX, SPF or DKIM do not, and outgoing mail starts failing silently a day later.
Files, database, cron jobs, DNS records and mail configuration listed before anything moves.
The full site on the new environment, reachable through a hosts file or temporary URL.
URLs updated with a tool that understands serialized data, then verified in theme options and builder content.
Front end, admin, forms, checkout, media and permalinks on the new copy while the old site still serves traffic.
TTL lowered in advance, DNS switched in one window, old environment kept warm for a fast rollback.
SSL chain, redirects, 404s, mail delivery, sitemap resubmission and a crawl check after propagation.
Minutes, if planned: DNS TTL is lowered ahead of time, the new environment is fully tested, and the switch happens in one window. Days of downtime come from an unplanned move, not from migrating.
Not if URLs, redirects and the canonical host stay consistent. The real risks are unplanned URL changes and soft 404s. I map old URLs to new ones and check indexing after the move.
Yes, including orders, customers and product data. High-performance order storage adds a step: the order tables must be migrated and verified, not just copied.
I handle the WordPress side and advise on DNS records for SPF, DKIM and DMARC. If you use a separate mail provider, I make sure the records point at it before the cutover.
Migration, SSL & DNS
A short diagnosis is free. If the fault is outside this service, you will be told which one applies — or that the site is not worth repairing.
Or email hello@wordpressfixe.com — first reply within 1 business day.