Platform migration
WordPress to Shopify, Wix to WordPress, custom to a CMS. Highest risk because URL structures usually change entirely. Redirect mapping is the whole job.
Migrations fail in one predictable way: URLs change, nobody mapped them, and the traffic that took years to build goes to a competitor.
Any migration, whether platform, host or domain, needs the same discipline: export every indexed URL first, map each to a destination, implement as permanent redirects, and verify every one before going live. Most migration traffic losses come from skipping the first step.
WordPress to Shopify, Wix to WordPress, custom to a CMS. Highest risk because URL structures usually change entirely. Redirect mapping is the whole job.
Same URLs, different server. Lower risk, and the failure modes are downtime, DNS propagation and missing files rather than lost rankings.
Changing domain name. Redirects plus Google's change of address tool, and expect a temporary dip even when done correctly. Some inbound links never get updated.
Should have happened years ago and some sites still have not. Redirect everything, update internal links and canonicals, and fix mixed content.
Changing your URL pattern without changing platform. Only worth doing with a genuine reason, because every change costs some authority in transfer.
Exporting every indexed URL before starting. Search Console, analytics and a full crawl, because each misses what the others catch. Without this list there is nothing to map against.
| Do | Why |
|---|---|
| Export URLs from three sources | Each misses what the others catch |
| Map every URL to a destination | Not the homepage, the closest equivalent |
| Use permanent redirects | Temporary ones do not pass authority the same way |
| Test every redirect before launch | Valid syntax is not working syntax |
| Keep redirects indefinitely | Old links keep sending traffic for years |
| Update internal links to new URLs | Do not rely on redirects internally |
| Watch coverage daily for two weeks | Catch problems while they are small |
| Ask them | Good answer | Walk away if |
|---|---|---|
| Who owns the accounts and data? | You do, in your own name | Accounts in the agency's name |
| Can I open three live examples? | URLs you can check yourself | Screenshots and a PDF |
| What is explicitly not included? | A written list with change pricing | Everything is included |
| What happens when it breaks? | A named process and response time | Not discussed |
The failure question matters most on anything connected to another system, because integrations fail quietly.
Not if every existing indexed URL is mapped to a destination and implemented as a permanent redirect. Almost all migration traffic loss comes from skipping the URL export at the start, which leaves nothing to map against.
Hosting migrations can be done in a day plus DNS propagation. Platform migrations take weeks depending on content volume, and most of that time is content and redirect mapping rather than technical work.
Usually, by building on the new platform in parallel, testing thoroughly, then switching DNS. Downtime happens when the migration is done in place under pressure.
Redirects plus Google's change of address tool. Expect a temporary dip even when done correctly, and accept that some inbound links will never be updated by their owners. Change domain only with a real reason.
Indefinitely. Old links on other sites keep sending traffic for years, and removing a redirect breaks them permanently. Redirects cost almost nothing to keep.
Wix and some proprietary systems have no clean export, so content is recreated rather than migrated. The URL mapping matters even more in that case, because everything else is being rebuilt anyway.
Send us what you are trying to fix and we will tell you what it takes, what it costs, and whether we are the right people for it. If we are not, we will say so.