Pick your move
Find your move, then read how we run it.
Leaving a hosted builder
Leaving a page builder
Changing the stack
From our logs
Next.js rebuild.
Our after-launch test found old URLs redirected to the homepage. The indexed URLs were remapped to their closest new pages four days later. Writing a rule down is not enough. Testing for it is what caught this.
WordPress to Next.js, staging.
A parity check across 94 unique URLs found 7 returning 404 and 2 redirecting to the homepage. The old category sitemap listed 26 URLs. Staging had 5.
Tile manufacturer.
The URL structure changed in a move and the map had to be built after launch. We matched Search Console’s most-clicked pages to new products and categories, and used the Wayback Machine for the eight that had no obvious match.
Client names are left out.
Should you move at all?
We will tell you if the answer is no. A migration costs time and carries risk, and sometimes a smaller fix gets you most of the way.
- •Every change needs a developer, or a ticket to the platform
- •You pay monthly for apps that WordPress does with one plugin
- •The builder is the reason the site is slow, and speed matters to your sales
- •You cannot get your own data out, or cannot control your own SEO settings
- •The real problem is content or design, not the platform
- •The site earns its keep and nobody on the team is blocked by it
- •The move would land in your busiest season
How we work
Every migration is a fixed-scope project. We scope it after seeing your site and your data, not from a price list. After launch, most clients keep us on a maintenance retainer that watches the 404 log, Search Console, updates and backups. You do not have to.
If you are rebuilding rather than moving, start with how we approach web design.
Frequently asked questions
Will we lose our Google rankings?+
Nobody can promise rankings will not move during a migration, because Google has to recrawl the site. What we can promise is the work that prevents avoidable losses: the inventory, the redirect map, and tests before and after launch.
How long does a migration take?+
It depends on the number of URLs, products and integrations. A brochure site is usually a few weeks. A store with customer accounts and subscriptions takes longer. You get a timeline with the scope, before you commit.
Will the site go down during the move?+
No, in normal circumstances. The new site is built and tested on staging while the old one stays live. The switch happens at a quiet time, and the old site stays reachable until the new one is proven.
Can you keep our current design?+
Yes, if it works. We can rebuild it faithfully on the new platform, or use the move to fix what is not converting. That is your call.
Do you work with our SEO consultant or in-house developer?+
Yes. We agree who owns what up front: Search Console, redirects, DNS, analytics. It is how we already work with two clients who have their own SEO consultants.
What happens to our email when DNS changes?+
Nothing, if the records move with care. We export the full DNS zone, list what every record does, and send test emails the day you switch.