Redirect map reviewed page by page
Built from your crawl, analytics, and backlink data. Pattern rules cover the long tail. A person checks every page that carries traffic or links, including pagination, archives, and trailing slashes.
Replatform with a redirect map and a rehearsed rollback.
WordPress to Next.js, Magento to Shopify, legacy CMS to headless. Redirect maps reviewed page by page, staged cutovers, and a rehearsed rollback.
The shape of a clean cutover
Six pieces every replatform needs.
Most migration risk sits in URLs, content, and launch day. We plan each one before any traffic moves.
Content migration
Scripted and repeatable, with a diff report per content type. Editors review it before cutover.
ScriptedDiffReviewed
Staged rollout
Traffic moves in steps. Rollback triggers fire if error rates or 404s cross thresholds we agree in writing.
StagedTriggersRollback
Hreflang and canonicals
Locale tags and canonicals rebuilt for the new structure and validated before launch.
Multi-localeCanonicalValidated
Daily monitoring through the move
Search Console, 404 logs, organic sessions, and revenue per session, checked daily against a pre-launch baseline.
A planned sunset
The old stack stays warm until the numbers settle. Then a final backup, an archived redirect map, and a clean shutdown.
Cutover
Move traffic with a safety net.
A replatform can work page by page and still lose traffic on launch day. We move traffic in stages, watch errors and search signals at each step, and hold or roll back before a problem spreads.
- Traffic ramps 5%, 25%, 50%, then 100%, with a go/no-go check at each step.
- 404s and server errors watched live, with thresholds agreed before launch.
- Missed redirects patched the same day from the 404 log.
- The old platform kept warm for 14 days as a fallback.
Before launch day
Rehearse the rollback first.
A rollback plan nobody has run is a guess. We run it on staging before launch, time it, and write down who does what.
- DNS TTLs lowered ahead of cutover so a switch-back takes minutes.
- Rollback run end to end on staging and timed.
- A written runbook with named owners for every step.
- A launch window agreed with marketing, away from campaigns and peak trading.
1:1
Redirect for every URL with traffic or backlinks
T−7 days
Rollback rehearsed on staging before cutover
Daily
Search, 404, and revenue reports through the move
14 days
Old platform kept warm after cutover
Launch day was the quietest day of the project. We had rehearsed the rollback twice and never needed it.
Questions
What buyers ask us first.
Will we lose search rankings?
Some movement is normal after any migration, and nobody can guarantee rankings. A complete redirect map, unchanged content where it matters, and daily monitoring keep the risk low and catch problems early.
How long does a migration take?
It depends on URL count, content volume, and integrations. After discovery you get a dated plan that includes the rehearsal, the cutover window, and the sunset.
Which platforms do you move between?
Common moves are WordPress to Next.js, Magento or WooCommerce to Shopify, and legacy CMSs to a headless CMS. If your source has an export or a database, we can plan a route off it.
Can we change our URL structure at the same time?
Yes, though every changed URL adds risk. We help you decide which changes are worth it and map each one.
How is it priced?
Migrations are quoted as a fixed scope after discovery, since most of the work is known once we have crawled the site. Post-launch support runs as a short retainer.
Ready when you are
Tell us what platform you’re stuck on.
A 30-minute call. We’ll outline the risks, the order of work, and what we need from your team.