Move your site to code you own.
Whatever your site is built on today, we can rebuild it as plain, fast code on Claude Code - keeping your content and your rankings, with no platform subscription, no lock-in, and no export wall. Pick your starting point.
WordPress to Claude Code
Escape the plugin stack, the updates and the security patches. Same content, plain fast code.
Read more
Squarespace to Claude Code
Keep the simplicity, lose the template ceiling. A site that can finally do what you need.
Read more
Wix to Claude Code
Move off the locked-in builder to code you own - faster, cleaner, and properly optimised.
Read more
Webflow to Claude Code
Keep the design ambition, drop the subscription and the CMS limits. Plain code you own.
Read more
Framer to Claude Code
Take the polished design into code you own, with room to grow past a marketing site.
Read more
Duda to Claude Code
Keep the polish, drop the subscription and the editor weight. Plain, fast code you own outright.
Read more
Hand-coded / HTML to Claude Code
Modernise an ageing hand-built site into maintainable code you can change by asking.
Read moreWhat a website migration
actually is.
The word covers four different jobs. It’s worth knowing which one you’re buying, because the risk sits in different places for each.
A website migration is any change big enough to alter how search engines find and read your site - a new platform, a new domain, a restructured set of pages, or several sites folded into one. Done properly, your visitors and your rankings barely notice it happened. Done casually, it is how businesses lose years of search equity in a weekend.
Most of the migrations we run are platform migrations: a site living on WordPress, Wix, Squarespace, Webflow, Framer or Duda, rebuilt as plain, fast code in a repository in your name. Your content is already yours; the foundation underneath it is what changes.
Platform migration
Same domain, same content, new foundation. The most common move on this page, and the safest when it's planned - the URLs can usually stay exactly where they are.
Domain migration
The site moves to a new address, so every URL changes even if nothing else does. Redirects carry the whole weight of the move.
Redesign and restructure
New templates, new page architecture, often new content. The design is the visible part; the URL and metadata changes underneath are where rankings are won or lost.
Consolidation
Two or more sites folded into one - after an acquisition, a rebrand, or years of microsites nobody retired. The hardest type to inventory and the easiest to lose pages in.
Most real projects combine at least two of these. A typical engagement here is a platform migration and a redesign in one pass: the site comes off the platform, the design gets sharpened while it’s on the bench, and the crawlable structure underneath is carried over deliberately. Whatever the combination, the risk concentrates in the same three places - URLs, metadata and redirects - which is why our process is built entirely around them.
Why migrations lose rankings - and how ours don’t.
Rankings are not attached to your business. They are attached to your URLs - each one carrying its own history of content, links and user behaviour that Google has learned to trust. A migration disturbs that history by definition. Whether rankings survive comes down to one thing: is every piece of accumulated trust deliberately carried to its new address, or silently abandoned at the old one?
Migrations that go wrong rarely fail dramatically. They fail quietly: a batch of URLs nobody inventoried, redirects that dump everything on the homepage instead of the matching page, metadata regenerated from scratch because carrying it over felt like extra work. Google re-crawls, finds a site it doesn’t recognise, and starts evaluating it from cold.
How rankings survive the move.
The SEO-safe migration, in one glanceRedesigns lose rankings through skipped redirects, so we never skip them. Every migration runs the same four checks, in order, and the last one happens after launch, not before.
URL inventory
Every URL on the old site crawled and recorded, with its rankings, backlinks and traffic noted. Nothing moves until the full map exists.
Rebuild, mirrored
Content, titles, metadata and structured data carried over one to one. The design can be kept faithful or sharpened; the crawlable structure stays deliberate.
Redirects, one to one
Every old URL 301-redirects to its exact successor. No wildcard shortcuts, no redirect chains, no orphaned pages.
Crawl re-test
The live site is re-crawled against the inventory: every redirect checked, every page indexed, Search Console watched through the handover weeks.
What each step is actually for.
Step 1 - URL inventory. Nothing moves until the map exists. We crawl every URL on the old site and record what each one is worth: its rankings, its backlinks, its traffic. This inventory does three jobs at once - it fixes the scope and timeline of the migration, it decides the redirect map, and it becomes the checklist the live site is verified against after launch. It’s also where data integrity starts: if a page, a title or an image is in the inventory, it can’t be silently lost, because the inventory is what the finished site is checked against.
Step 2 - Rebuild, mirrored. The new site is built on staging while the old one carries on trading, untouched. Content, titles, meta descriptions and structured data are carried over one to one - carried, not regenerated - so what Google reads after the move is what it already trusts. The design can be rebuilt faithfully or sharpened while it’s open on the bench; the crawlable structure underneath stays deliberate either way. Before anything goes live, staging is verified page by page against the inventory from step one.
Step 3 - Redirects, one to one. Every old URL gets a 301 redirect to its exact successor - the page that answers the same question, not the homepage, not a category page that vaguely relates. No wildcard shortcuts, because a wildcard sends hundreds of distinct pages to one address and throws their individual equity away. No redirect chains, because every hop leaks signal and slows the crawl. No orphaned pages, because the inventory says exactly what exists.
Step 4 - Crawl re-test, after launch. Launch isn’t the end of the migration; it’s the start of the verification. The live site is re-crawled against the original inventory: every redirect followed, every page confirmed indexed, every 404 investigated. Search Console is watched through the handover weeks, so a wobble gets caught while it’s still a wobble.
And if something does look wrong, the way back is short. The old site stays live until the new one has passed its checks - launch is a DNS switch, not a demolition, and a switch can be reversed. On the new site, every deploy is versioned in Git, so rolling back a change means redeploying the previous version, not reconstructing it from memory. Migrations go wrong when they’re built as one-way doors. Ours aren’t.
The working version of this process - every check, in order, with the reasoning - is published as our website migration checklist. It’s the same list we run internally, so you can use it to hold us to account, or to hold anyone else to account.
What moves with you - and what gets rebuilt.
The honest answer to “will we lose anything?” is: nothing you’d want to keep, and quite a lot you won’t miss.
Comes with you
- Every page, post and image, migrated as structured content
- Your URL structure - kept where it's good, mapped and 301-redirected where it isn't
- Titles, meta descriptions and structured data, carried one to one
- Your rankings, and the backlink equity behind them
- Forms, bookings and integrations, reconnected to the tools they feed
- Analytics continuity, so reporting doesn't restart from zero
Gets rebuilt, deliberately
- Templates and themes become a design system, applied everywhere
- Plugins and widgets become small amounts of code that do exactly their job
- Embeds and iframes become native features of the site
- Platform hosting becomes modern infrastructure - versioned, previewable on every change, deployed with zero downtime
Forms are the classic migration casualty - the thing everyone forgets until enquiries quietly stop arriving. We rebuild them natively, with validation, spam protection and reliable delivery to your inbox or CRM, and we test them before and after launch. Most plugin and widget functionality turns out to be a surprisingly small amount of code once it isn’t wrapped in a platform.
Plain code you own.
Every migration on this page ends in the same place, which is what makes the process so repeatable. Your site becomes plain, fast code in a repository in your name, built and maintained with Claude Code - Anthropic’s agentic coding tool, working inside the codebase the way an engineer does. If that sentence needs unpacking, we’ve written a plain-English guide to what Claude Code is for exactly this moment.
Lighthouse 100s
Performance, accessibility, best practices and SEO - full marks, because in plain code every flag Google raises can actually be reached and fixed.
No platform fee
The subscription you're paying today ends at launch and isn't replaced by another one. Hosting is measured in pounds, not plans.
Changes by asking
You describe the change and it ships, usually the same day. No admin panel to learn, no ticket queue, no waiting for a developer to be found.
Owned outright
Plain code, your repository, your hosting accounts. If you ever leave us, you leave with everything.
We’re an Anthropic Claude Partner and we build this way daily - the full argument lives on our Built on Claude Code page. If you’re evaluating the tooling itself, we’ve also covered what Claude Code costs in the UK and how it compares to Cursor, Codex and Copilot, written from daily production use rather than a weekend road test.
One honest caveat, as always: if hands-on, drag-and-drop editing is essential for your team, we’ll say so on the first call and recommend Duda instead. We build on both lanes every week and recommend on fit, not on what we’d rather sell.
How long it takes, and what it costs.
Most sites are rebuilt and live within one to three weeks. Large content archives run longer, and the timeline is fixed after the URL inventory rather than guessed up front - once the map exists, we know exactly what’s moving and can put a date on it instead of an estimate. The old site stays live for the whole build, so there is no gap where you’re invisible, and launch waits until the new site has passed its checks, not until a deadline says so.
A migration is priced as a build, because that’s what it is: websites from £4,500, and from £18,000 where the move includes real software - a portal, a members area, an application behind the marketing site. There’s no separate “migration fee”; the URL inventory, the redirect map and the post-launch verification are part of how we build, not an add-on. Full pricing is published on our pricing page, including the retainers most clients don’t need.
The number that changes most after the move is the one nobody quotes up front: the cost of change. On a platform, every change after launch is either your team’s time or a developer’s invoice. Here, you describe the change and it ships - usually the same day - so the site keeps improving instead of quietly going stale. If you want to see the approach before committing to anything, we’ll redesign your homepage free: a working page, yours to keep either way.
Your starting point,
in detail.
Each platform fails in its own way, so each migration page covers the specifics: the before-and-after stack, what happens to your particular widgets and integrations, and the honest comparison table.
WordPress to Claude Code migration
Most WordPress conversations start with “we're scared to update it”. The plugin stack that made the site possible is now the thing that keeps breaking it. We replace the whole stack with code you own - every post and page kept, rankings carried - so the patch treadmill simply ends.
Squarespace to Claude Code migration
A fine place to start, a frustrating place to grow. When the template won't do what the business now needs - custom layouts, real integrations, proper performance - we rebuild as plain code with no ceiling, and keep the bit you actually liked: not having to maintain anything.
Wix to Claude Code migration
There's no full site export from Wix, which makes leaving look harder than it is. We rebuild from the live site - content, images and all - and carry your rankings across with a full URL map and one-to-one redirects.
Webflow to Claude Code migration
A serious design tool with real limits: CMS item caps, per-site fees, and a wall when you need application logic. We keep the design, remove the ceiling, and the collections come across as structured content with no item limits on the other side.
Framer to Claude Code migration
Framer has no code export - the site exists only while the subscription does. We rebuild it as code you own outright, keep the polish and the speed, and give it room to grow past a marketing site.
Duda to Claude Code migration
We build on Duda every week and recommend it for teams who need to edit the site themselves - so this is the most honest page on the list. The move makes sense when ownership, top-end performance and dropping the monthly fee matter more than self-serve editing, and we'll tell you plainly which side of that line you're on.
HTML to Claude Code migration
Fast but frozen: every change means finding a developer, and the original one left years ago. We rebuild from the live site into modern, maintainable code you can change by asking - keeping the speed a lightweight site already has.
Proof, not
promises.
Migration work is awkward to showcase, because the best possible result is that nothing visible changes except the numbers. So here is the nearest honest evidence: rebuilds and Claude Code builds you can go and inspect.
Cademi
A complete rebuild, not a reskin: a multilingual training platform rebranded and rebuilt around the demo funnel, with SEO rebuilt from the foundations. Demo requests multiplied 3.4x after relaunch (reported from the engagement).
SimpleFuel
Three product lines - bulk fuel, fuel cards and telematics - carried by one Claude Code build, each with its own clear space and its own route to a qualified enquiry.
AMG Rib & Repair
A specialist marine workshop's site, built on Claude Code and owned outright: the destination every migration on this page arrives at.
The same stack runs Avago (an end-to-end build: site, API, portal and brand), LoadSnap (a UK waste-compliance SaaS with a DEFRA Digital Waste Tracking integration) and Drone Rules (a regulation-led search resource built with Coptrz). To be precise about the claims: not all of these began as migrations - some started from nothing - but every one shows the code quality, the speed and the ownership your site ends up with.
Asked before every migration.
By treating rankings as things that live at URL level. We crawl and inventory every URL before anything moves, rebuild with titles, metadata and structured data carried one to one, 301-redirect every old URL to its exact successor, then re-crawl the live site against the inventory after launch. Rankings carry over because nothing gets left behind by accident.
See your homepage rebuilt before you commit.
Send us your URL and we'll redesign your homepage free: a working page, yours to keep either way.