Home

->

Website migration

Updated September 2026

AI-native website migration services with Every URL Accounted For.

AI-native website migration services with Every URL Accounted For.

AI-native website migration services with Every URL Accounted For.

AI-native website migration services with Every URL Accounted For.

Claude and a full crawl read your live site, and our engineers rebuild it natively in Webflow, Framer or Next.js, with every changed URL redirected and tested.

Claude and a full crawl read your live site, and our engineers rebuild it natively in Webflow, Framer or Next.js, with every changed URL redirected and tested.

Ask ChatGPT

Claude

Ask Claude

Webflow
Ploy
Next.js
WordPress
Framer
Webflow

Migrate to Webflow

For marketing-led teams

A visual CMS your marketing team runs, with hosting and security handled.

Shopify
Lovable
Webflow
Ploy
Next.js
WordPress
Framer
Webflow

Migrate to Webflow

For marketing-led teams

A visual CMS your marketing team runs, with hosting and security handled.

Shopify
Lovable

Rango moves websites for SaaS and AI companies onto Webflow, Framer, Next.js, WordPress, Shopify, Lovable and Ploy, including sites with Thousands Of URLs, gated content and custom post types.

Rango moves websites for SaaS and AI companies onto Webflow, Framer, Next.js, WordPress, Shopify, Lovable and Ploy, including sites with Thousands Of URLs, gated content and custom post types.

Rango moves websites for SaaS and AI companies onto Webflow, Framer, Next.js, WordPress, Shopify, Lovable and Ploy, including sites with Thousands Of URLs, gated content and custom post types.

Claude and a crawl read Every Live Page, our engineers rebuild it natively and keep Watching After Launch to catch anything that could cost you leads.

Claude and a crawl read Every Live Page, our engineers rebuild it natively and keep Watching After Launch to catch anything that could cost you leads.

Claude and a crawl read Every Live Page, our engineers rebuild it natively and keep Watching After Launch to catch anything that could cost you leads.

Why teams migrate

Name the goal first. The Platform Comes Second.

Name the goal first. The Platform Comes Second.

01

Every edit waits on a developer

The goal: marketing publishes pages, posts and edits without a ticket.

01

Every edit waits on a developer

The goal: marketing publishes pages, posts and edits without a ticket.

02

Plugins that need constant patching

The goal: fewer moving parts to patch. Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 91% of them in plugins.

02

Plugins that need constant patching

The goal: fewer moving parts to patch. Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 91% of them in plugins.

03

Slow pages on mobile

The goal: pages that pass Core Web Vitals, measured on the new build, not promised by the platform.

03

Slow pages on mobile

The goal: pages that pass Core Web Vitals, measured on the new build, not promised by the platform.

04

A rebrand the old theme cannot carry

The goal: a design system in the new stack that your team reuses on every page it adds.

04

A rebrand the old theme cannot carry

The goal: a design system in the new stack that your team reuses on every page it adds.

05

Blogs and microsites that drifted apart

The goal: one site, one CMS and one analytics setup, with every old URL pointed to its new home.

05

Blogs and microsites that drifted apart

The goal: one site, one CMS and one analytics setup, with every old URL pointed to its new home.

06

Pages AI assistants struggle to read

The goal: clean HTML, metadata and schema that search engines and AI assistants can read and cite.

06

Pages AI assistants struggle to read

The goal: clean HTML, metadata and schema that search engines and AI assistants can read and cite.

Sources: Patchstack, State of WordPress Security in 2026; HTTP Archive Core Web Vitals technology report; Google Search Central on site moves.

Website migration services

Everything a platform move needs, Nothing Left Behind.

Everything a platform move needs, Nothing Left Behind.

Everything a platform move needs, Nothing Left Behind.

01

URL inventory and crawl

We build the inventory from a full crawl, the sitemap, Search Console, analytics and CMS exports, and Claude in Chrome reads pages alongside them, so pages missing from the sitemap still get a destination.

02

Redirect mapping

Claude drafts the URL map, and an engineer checks every row, keeps unchanged URLs as they are, points changed ones to the right page with a 301, and tests the map on staging.

03

Content and CMS migration

Posts, case studies, gated resources and custom post types read from the live site or its API and rebuilt in a CMS modelled for them, then checked by a person.

04

Metadata and schema

Titles, descriptions, canonicals, Open Graph and structured data read from each live page and carried across, not rewritten from memory.

05

Internal links and media

Links inside body copy repointed to the new URLs, and images, files and video rehosted with their alt text intact.

06

Forms and integrations

Form routes into HubSpot or your CRM, chat widgets and scheduling tools rewired and tested end to end before cutover.

07

Analytics continuity

Analytics, Tag Manager, conversion events and consent carried over and checked before cutover, so reporting continues through the move.

08

Performance and accessibility

The new build checked against Core Web Vitals and WCAG 2.2 AA before launch, so the move improves the site, not just its platform.

09

Staged cutover and rollback

Launch set for a low-traffic window, with DNS, SSL and redirects staged in advance and the old site kept ready, so we can roll back quickly if something fails on the day.

10

Post-launch monitoring

After launch we watch Search Console coverage, 404s, redirects, rankings, form submissions and AI crawler access, and fix what surfaces during the monitoring period agreed in the scope.

URL inventory and crawl

We build the inventory from a full crawl, the sitemap, Search Console, analytics and CMS exports, and Claude in Chrome reads pages alongside them, so pages missing from the sitemap still get a destination.

Redirect mapping

Claude drafts the URL map, and an engineer checks every row, keeps unchanged URLs as they are, points changed ones to the right page with a 301, and tests the map on staging.

Content and CMS migration

Posts, case studies, gated resources and custom post types read from the live site or its API and rebuilt in a CMS modelled for them, then checked by a person.

Metadata and schema

Titles, descriptions, canonicals, Open Graph and structured data read from each live page and carried across, not rewritten from memory.

Internal links and media

Links inside body copy repointed to the new URLs, and images, files and video rehosted with their alt text intact.

Forms and integrations

Form routes into HubSpot or your CRM, chat widgets and scheduling tools rewired and tested end to end before cutover.

Analytics continuity

Analytics, Tag Manager, conversion events and consent carried over and checked before cutover, so reporting continues through the move.

Performance and accessibility

The new build checked against Core Web Vitals and WCAG 2.2 AA before launch, so the move improves the site, not just its platform.

Staged cutover and rollback

Launch set for a low-traffic window, with DNS, SSL and redirects staged in advance and the old site kept ready, so we can roll back quickly if something fails on the day.

Post-launch monitoring

After launch we watch Search Console coverage, 404s, redirects, rankings, form submissions and AI crawler access, and fix what surfaces during the monitoring period agreed in the scope.

How it works

How a migration works, From Audit To Cutover.

What you have today

A crawl, the sitemap, CMS exports, Search Console and analytics give the full URL list, and Claude in Chrome reads pages alongside them. We also record baseline rankings, speed and conversions to measure the move against.

01

Claude reads the live site

Week one

Agreed before we build

Claude drafts the redirect map and content model, an engineer checks every row, and you approve the platform plan and launch window before anything is built.

02

Redirect map and plan

Before the build

On staging first

Pages are rebuilt as real components in the new stack, not pasted HTML. A designer checks each one by eye against the old page, and we run content, SEO and page speed checks.

03

Native rebuild and content move

Every page

Launch and after

We switch over in a planned window with rollback ready, then watch Search Console, 404s, rankings, leads and AI crawler access, and fix migration issues during the agreed monitoring period.

04

Cutover and monitoring

Launch day onward

What you have today

A crawl, the sitemap, CMS exports, Search Console and analytics give the full URL list, and Claude in Chrome reads pages alongside them. We also record baseline rankings, speed and conversions to measure the move against.

01

Claude reads the live site

Week one

Agreed before we build

Claude drafts the redirect map and content model, an engineer checks every row, and you approve the platform plan and launch window before anything is built.

02

Redirect map and plan

Before the build

On staging first

Pages are rebuilt as real components in the new stack, not pasted HTML. A designer checks each one by eye against the old page, and we run content, SEO and page speed checks.

03

Native rebuild and content move

Every page

Launch and after

We switch over in a planned window with rollback ready, then watch Search Console, 404s, rankings, leads and AI crawler access, and fix migration issues during the agreed monitoring period.

04

Cutover and monitoring

Launch day onward

What you have today

A crawl, the sitemap, CMS exports, Search Console and analytics give the full URL list, and Claude in Chrome reads pages alongside them. We also record baseline rankings, speed and conversions to measure the move against.

01

Claude reads the live site

Week one

Agreed before we build

Claude drafts the redirect map and content model, an engineer checks every row, and you approve the platform plan and launch window before anything is built.

02

Redirect map and plan

Before the build

On staging first

Pages are rebuilt as real components in the new stack, not pasted HTML. A designer checks each one by eye against the old page, and we run content, SEO and page speed checks.

03

Native rebuild and content move

Every page

Launch and after

We switch over in a planned window with rollback ready, then watch Search Console, 404s, rankings, leads and AI crawler access, and fix migration issues during the agreed monitoring period.

04

Cutover and monitoring

Launch day onward

AI reads the old site. People Sign Off Every Page.

AI reads the old site. People Sign Off Every Page.

AI reads the old site. People Sign Off Every Page.

Illustration of a designer working on a laptop in a dark office at night

Claude reads the old site

Alongside a full crawl and your CMS exports, Claude reads pages the way a visitor does and records copy, links, metadata and schema for our engineers to review.

Illustration of a designer working on a laptop in a dark office at night

Claude reads the old site

Alongside a full crawl and your CMS exports, Claude reads pages the way a visitor does and records copy, links, metadata and schema for our engineers to review.

Illustration of a designer working on a laptop in a dark office at night

Claude reads the old site

Alongside a full crawl and your CMS exports, Claude reads pages the way a visitor does and records copy, links, metadata and schema for our engineers to review.

Rebuilt natively, not pasted

Pages become real components and CMS items in Webflow, Framer or Next.js, set up so your team edits the content it owns after launch.

Rebuilt natively, not pasted

Pages become real components and CMS items in Webflow, Framer or Next.js, set up so your team edits the content it owns after launch.

Rebuilt natively, not pasted

Pages become real components and CMS items in Webflow, Framer or Next.js, set up so your team edits the content it owns after launch.

Our engineers, in your Slack

Our engineers, in your Slack

Our engineers, in your Slack

The people moving your site join your Slack or Teams, so launch questions go straight to whoever is doing the work during agreed overlap hours.

The people moving your site join your Slack or Teams, so launch questions go straight to whoever is doing the work during agreed overlap hours.

The Rango team in Rango t-shirts
Illustration of a phone screen built from page layout blocks

Redesign or like-for-like

Move the site as it is, or redesign it on the way. Either way the URL map and content plan are settled first.

Illustration of a phone screen built from page layout blocks

Redesign or like-for-like

Move the site as it is, or redesign it on the way. Either way the URL map and content plan are settled first.

Illustration of a phone screen built from page layout blocks

Redesign or like-for-like

Move the site as it is, or redesign it on the way. Either way the URL map and content plan are settled first.

Illustration of a laptop on a desk at night showing a chat interface

Checked by a designer

Before launch, a designer checks every page by eye against the old site, and we run content, SEO and page speed checks on each one.

Illustration of a laptop on a desk at night showing a chat interface

Checked by a designer

Before launch, a designer checks every page by eye against the old site, and we run content, SEO and page speed checks on each one.

Illustration of a laptop on a desk at night showing a chat interface

Checked by a designer

Before launch, a designer checks every page by eye against the old site, and we run content, SEO and page speed checks on each one.

Choosing a website migration partner

Rango

Traditional agency

Development-only agency

Choosing a website migration partner

Rango

Traditional agency

Development-only agency

What It Costs

What It Costs

Fixed price for an agreed scope.

Fixed price for an agreed scope.

A project fee, often after paid discovery.

A project fee, often after paid discovery.

A build fee, SEO often scoped apart.

A build fee, SEO often scoped apart.

URL Inventory

URL Inventory

Every live URL, from a crawl plus Claude.

Every live URL, from a crawl plus Claude.

Depth depends on the SEO scope.

Depth depends on the SEO scope.

Depends on the brief.

Depends on the brief.

Redirects

Redirects

One-to-one 301s, tested on staging.

One-to-one 301s, tested on staging.

Often handed to an SEO partner.

Often handed to an SEO partner.

Added if the scope includes them.

Added if the scope includes them.

Content Move

Content Move

Read from the live site, rebuilt natively.

Read from the live site, rebuilt natively.

Manual or scripted, by project.

Manual or scripted, by project.

Imported where an export exists.

Imported where an export exists.

Forms And Tracking

Forms And Tracking

Rewired and tested before cutover.

Rewired and tested before cutover.

Rebuilt as part of the project.

Rebuilt as part of the project.

Rebuilt to spec, testing varies.

Rebuilt to spec, testing varies.

Launch Day

Launch Day

Staged cutover with a rollback plan.

Staged cutover with a rollback plan.

A scheduled launch, process varies.

A scheduled launch, process varies.

Deploy, then a handover.

Deploy, then a handover.

After Launch

After Launch

Search Console and 404s watched.

Search Console and 404s watched.

Launch support, then a retainer.

Launch support, then a retainer.

A warranty period, then new tickets.

A warranty period, then new tickets.

Who Does The Work

Who Does The Work

Designers and engineers, with AI agents.

Designers and engineers, with AI agents.

Separate strategy, design and build teams.

Separate strategy, design and build teams.

Engineers, with design from you.

Engineers, with design from you.

Platforms Covered

Platforms Covered

Webflow, Framer, Next.js, WordPress, Shopify and more.

Webflow, Framer, Next.js, WordPress, Shopify and more.

Usually one preferred platform.

Usually one preferred platform.

Usually the stack they specialise in.

Usually the stack they specialise in.

Where Access Lives

Where Access Lives

Your hosting, repo and CMS.

Your hosting, repo and CMS.

Often hosted by the agency.

Often hosted by the agency.

Usually transferred at handoff.

Usually transferred at handoff.

A launch you can check, line by line.

A launch you can check, line by line.

A launch you can check, line by line.

We test the redirect map, forms and tracking before cutover, and check the new build against Core Web Vitals and WCAG 2.2 AA, so you see the results instead of taking our word for it.

We test the redirect map, forms and tracking before cutover, and check the new build against Core Web Vitals and WCAG 2.2 AA, so you see the results instead of taking our word for it.

  • Full URL inventory

  • One-to-one 301 redirects

  • Redirects tested on staging

  • Metadata carried over

  • Schema carried over

  • Internal links repointed

  • CMS content checked

  • Forms tested end to end

  • Analytics continuity

  • Core Web Vitals checks

  • WCAG 2.2 AA checks

  • Staged cutover

  • Rollback plan

  • Search Console monitoring

Engagement Models

Ways To Work With Rango.

Staff Augmentation

Migration engineer (3 to 5 yrs)

Daily async updates, weekly live reviews

1 WEEK TRIAL

Fixed-Scope Build

Ideal for a full platform move

Weekly progress reviews

2-FOLD TRIAL

Monthly Partnership

Ideal for a move done in phases

Asynchronous updates + fast turnarounds

8 HOUR TRIAL

What we run into, written down.

What we run into, written down.

What we run into, written down.

Speaker with a headset mic on stage at Webflow Conf, beside the Webflow Conf logo, in orange halftone
Webflow Conf 2026: Review Beats Generation

Webflow announced a generation layer and shipped a review layer. Source is still a research preview. What you can actually use today is about control.

Industry

8 MIN READ

Illustrated conference tickets and badges stamped with landmark icons for five fintech event cities
Fintech Event Season Is a Design Deadline

Before GFF, Money20/20, Hong Kong FinTech Week and Singapore FinTech Festival, fintech teams need clarity across their website, demo, deck and follow-up.

Fintech

6 MIN READ

Orange pixel art of the Paper logo linked to a terminal prompt, beside a design canvas window
Website Designers Can't Skip Paper.design

I don't write code. Two Next.js landing pages shipped anyway. This is the workflow.

Tools

9 MIN READ

Speaker with a headset mic on stage at Webflow Conf, beside the Webflow Conf logo, in orange halftone
Webflow Conf 2026: Review Beats Generation

Webflow announced a generation layer and shipped a review layer. Source is still a research preview. What you can actually use today is about control.

Industry

8 MIN READ

Six birds flying in formation against a dark red sky, with the lead position at the front of the formation drawn as an empty dotted outline.
The Test You Don't Get to Schedule

Twice in August I vanished with no notice. Delivery held. Direction did not. What an unplanned absence reveals that a planned one never can.

Inside Rango

4 MIN READ

Orange pixel art portrait of Steve Jobs in round glasses and a black turtleneck, hand on his chin
No Middle Layer

AI cuts coordination overhead, giving small teams more bandwidth and clearer ownership.

AI

2 MIN READ

Frequently asked questions

Straight Answers. No fluff.

How much does a website migration cost?

Every migration is quoted after a short audit, and the price is fixed for the agreed scope before work starts. It depends on how many URLs and CMS items move, which forms and integrations need rewiring, and whether the site is redesigned on the way. Contracts are in USD.

How long does a website migration take?

It depends on the size of the site, the amount of CMS content and whether the move includes a redesign. You get a timeline with the redirect map and plan after the audit, before any build work starts, and weekly reviews show where it stands.

How do you use AI in a website migration?

Claude and Claude in Chrome read the live site alongside a crawler, the sitemap and CMS exports, and pull out copy, links, metadata, schema and embeds. Claude drafts the URL map and flags differences between old and new pages. A designer then checks every page by eye, engineers review every redirect, and we run content, SEO and page speed checks before launch. Your content moves as it is, not rewritten by AI.

Can you migrate a large website?

Yes. We inventoried 2,344 live URLs on a WordPress site, including custom post types its sitemap missed, for a move to Webflow now under way. On another WordPress to Webflow move, live since July 2026, we moved 53 members-only lessons, converted their formulas so they render, and carried over their videos. Large sites move in phases, with the URL map and content model agreed before any build starts.

Why do companies migrate their website?

Usually because the marketing team waits on developers for every change, the plugin stack needs constant security patching, or pages are slow. Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 91% of them in plugins. In HTTP Archive's August 2026 US data, 80.1% of Webflow sites and 80.3% of Framer sites passed Core Web Vitals on mobile, against 62.9% of WordPress sites. Those are different sites, not before and after results, so we measure the new build either way.

Will migrating our website hurt our search rankings?

Any platform change can move rankings for a while, and nobody can honestly promise otherwise. Google says a medium-sized site can take a few weeks or more for changed URLs to settle in its index. What we control is the process: unchanged URLs kept, every changed URL given a tested 301 kept for at least a year, metadata, schema and internal links carried over, and Search Console, 404s and rankings watched during the agreed monitoring period.

Which platforms do you migrate between?

We move sites onto Webflow, Framer, Next.js, WordPress, Shopify, Lovable and Ploy, from WordPress, HubSpot CMS, Webflow, Framer, Next.js or a custom build. Because Claude reads the live site rather than an export, the platform you are leaving matters less than how the new one is set up.

Which platform should we move to?

It depends on who edits the site and what it connects to. Webflow and Framer suit marketing teams that want to publish without engineers. Next.js suits teams whose engineers own the site or need it close to the product. We recommend a platform after the audit, not before.

What happens to our forms, CRM and analytics?

Forms are rewired to HubSpot or your CRM, and scheduling tools, chat widgets and tracking scripts are reconnected. Analytics, Tag Manager and conversion events carry over, and every route is tested end to end on staging before cutover.

Who owns the site and the accounts after the move?

You do. The new site is built in your own hosting, repository and CMS accounts, and the IP is assigned to you. Nothing is held on our side, so ending the engagement is a matter of removing our access.

If you’re considering
Working Together