WEBSITE MIGRATION
Migrations where losing traffic is not an acceptable outcome.
200+
pages migrated
600+
CMS entries rebuilt
200K
launch-week visitors
0
acceptable ranking loss
Most migration horror stories are redirect stories.
The design gets approved, the content gets moved, the site goes live, and three weeks later organic traffic is down forty percent because a few hundred legacy URLs quietly 404. Every one of those was preventable at planning time, and none of them are visible in a design review.
We treat the redirect map, the canonical logic and the CMS model as the first deliverables, not the last. On PetDesk that meant an extensive redirect architecture across a 200-page WordPress estate. On Roamless it meant continuous redirect maintenance across 12+ locales for three years as the content structure kept changing.
URL inventory
Every live URL, its traffic, its backlinks and whether it deserves to survive.
CMS modelling
The content structure rebuilt properly rather than replicated field for field.
Redirect architecture
A complete map including wildcards, legacy routes and changed slugs.
Rebuild
Design and production in Framer, with page templates that scale.
SEO parity
Metadata, structured data, canonicals and internal linking checked page by page.
Post-launch watch
Search Console monitoring and fixes in the weeks that actually matter.
Migrations that ran at difficult scale.
PetDesk
WordPress to Framer: 200+ pages, 600+ CMS entries, 50+ forms, complete on launch day.
Armor
A regulated-industry security platform migrated and restructured, 40+ pages live.
Xpander
Migration used to collapse an over-complex CMS into something the team can run.
When to migrate
When the CMS is slowing your marketing team down more than it is helping, or when every page change needs a developer.
When not to
Mid-quarter, before a major campaign, or without anyone owning the redirect map. Timing is most of the risk.
Lift and shift
The old structure recreated in a new tool, including every problem that made you want to leave.
Migrate and simplify
The move used as the one chance you get to fix the content model, the URLs and the page hierarchy.
What a migration includes
WordPress to Framer
Full migration including CMS content, forms, redirects and integrations.
Webflow to Framer
Structure and CMS rebuilt, with SEO and content hierarchy preserved.
Custom stack to Framer
Marketing site pulled out of an app codebase so marketing can own it.
Redirect architecture
Complete mapping, wildcards, legacy routes and ongoing maintenance.
CMS restructuring
Content models rebuilt for how your team actually publishes.
Localisation
Multi-locale architecture, canonicals and hreflang handled properly.
Sitting on a WordPress site nobody wants to touch?
Start a project
