Skip to content

FIG 01 · Website Migration

Website migration services that protect your rankings

Platform, CMS, domain and hosting moves planned URL by URL, tested on staging and watched in Search Console after launch, by the team that builds on WordPress, Webflow, Shopify and Next.js.

See how it works
Developer moving an old website layout to a clean new one across two monitors, with a progress bar filling

FIG 02 · Quick answer

What are website migration services?

Website migration services move a site to a new platform, CMS, domain or host without losing traffic. Elgrith inventories every URL, maps 301 redirects, migrates content and media, tests on staging, launches with a checklist, then monitors Search Console and analytics. Google says to keep redirects for at least one year.

Redirects kept live, as Google advises
1 year+
Projects delivered since 2015
1,000+
Clients across the USA, UK and India
250+
Your redirect map, content and accounts
100%

FIG 03 · Why it matters

Google is clear about migrations. Most promises aren’t.

From Google Search Central and Search Console Help. Many providers promise “no ranking loss”; Google itself says visibility may fluctuate for a while.

FIG 04 · Definition

What is a website migration?

A website migration is any change to a site’s platform, URLs, domain, protocol or hosting that can affect how search engines crawl and rank it. Each type carries a different risk and calls for different Google tools.

Website migration types, risk and the Google tools that apply
Migration typeExampleRisk to rankingsWhat Google’s tools need
Domain changeoldbrand.com to newbrand.comHigh301 redirects plus Search Console’s Change of Address tool
Platform or CMSWordPress to Webflow or ShopifyMedium to high: URLs and templates change301 redirects, new sitemaps, structured-data parity
HostingShared hosting to a cloud host, same URLsLow to mediumNo URL changes; expect a temporary crawl-rate dip
HTTPShttp:// to https://Low301 redirects; no Change of Address needed
RedesignNew templates, navigation and contentMedium: internal links and content changeContent parity checks and redirects for removed pages

Many projects combine types, such as a new CMS and a new domain. We plan each change separately so problems can be traced.

Read the website migration checklist (2026)

FIG 05 · What you get

Our website migration services

Platform, CMS, e-commerce, domain and hosting moves, each one planned URL by URL by a team that builds on the platforms it migrates between.

Pencil sketch of a messy sitemap redrawn as a tidy one, joined by blue arrows, beside a progress bar
Website Migration · built in-house

01

Platform and CMS migrations

Platform migration services between WordPress, Webflow, Shopify, Wix, Squarespace, Drupal and headless CMSs, with templates rebuilt and content mapped field by field.

02

WordPress migration services

WordPress hosting moves, multisite splits and moves from WordPress to Webflow or Next.js, with plugins audited and replaced.

03

E-commerce replatforming

WooCommerce and Magento to Shopify, with products, customers, orders and SEO data moved and every product URL redirected.

04

Domain and brand changes

New domain or merged sites, with page-to-page redirects and Google’s Change of Address tool set up in Search Console.

05

Hosting and server moves

Moves to a new host or CDN with the same URLs, DNS TTLs lowered first and SSL ready before the switch.

06

HTTPS migrations

Site-wide 301s from http to https, updated canonicals, sitemaps and internal links, and mixed-content fixes.

Deliverables

12

deliverables, in writing

Included in every build, written into your fixed quote before work starts.

FIG 06 · Migration paths

Where we move sites from, and to

Every path runs through the same redirect map, staging environment and launch checklist.

  • WordPress
  • WooCommerce or Magento
  • Wix or Squarespace
  • Old domain
  • Webflow
  • Shopify
  • Next.js
  • New domain
  • WordPress to Webflow

    Why
    Visual editing and fewer plugins
    Watch for
    URL structure and blog slugs
    Webflow Development
  • WooCommerce or Magento to Shopify

    Why
    Hosted checkout and less upkeep
    Watch for
    Product, collection and variant URLs
    E-commerce Development
  • WordPress to Next.js

    Why
    Speed and custom features
    Watch for
    Editor workflow and structured data
    React & Next.js Development
  • Wix or Squarespace to WordPress

    Why
    Ownership and flexibility
    Watch for
    Auto-generated URLs and image paths
    WordPress Development
  • Domain or brand change

    Why
    Rebrand, merger or market change
    Watch for
    Change of Address and backlinks
  • Hosting move

    Why
    Speed, cost or reliability
    Watch for
    DNS, SSL and a temporary crawl dip
    Cloud Migration

FIG 07 · Flagship build

Proof: the team that builds the platforms moves sites between them

Our engineers build on WordPress, Webflow, Shopify and Next.js every week, and designed and engineered Kenerate AI, our flagship AI image and video studio. It is not a migration project; it shows the engineering behind our migrations.

  • 200+ AI models behind one app, one login and one credit balance
  • 23+ studios and tools, with up to 4K output
  • MCP & CLI: use Kenerate inside Claude, ChatGPT, Cursor and 19+ AI apps
  • 1,000+ projects for 250+ clients since 2015
Kenerate AI agent page: Kenerate inside Claude, ChatGPT and Cursor through MCP and CLI

Agent: Kenerate inside Claude, ChatGPT and Cursor

AI models in one app
200+
Studios and tools
23+
Maximum output
4K
Guides
500+

FIG 08 · SEO

How we protect SEO during a migration

Google’s site-move guidance comes down to mapping every old URL to its new home, keeping redirects in place and helping Google discover the change. We do each step in writing.

06principles

  • Full URL inventory

    Every URL from crawls, sitemaps, Search Console and analytics, including PDFs, images and pages with backlinks.

  • Page-to-page 301 map

    Each old URL redirected to its closest new equivalent, not the home page, and tested before and after launch.

  • Content and metadata parity

    Titles, descriptions, headings, body copy, alt text and canonical tags carried over or deliberately improved.

  • Structured-data parity

    Schema compared page type by page type, so rich results and AI-search signals survive the move.

  • Sitemaps and Search Console

    New XML sitemaps submitted, old ones kept briefly for discovery, and Change of Address used for domain moves.

  • Crawler access

    robots.txt, noindex tags and AI crawler access checked on launch day, so staging rules never reach production.

    Technical SEO

FIG 09 · Rollback

Our rollback plan

Every migration has a written rollback plan before launch day: what triggers it, who decides and how the old site comes back.

04principles

  • The old site stays ready

    The previous site, database and DNS records are kept intact until the rollback window agreed in your scope closes.

  • Clear triggers

    Broken checkout, failed forms, mass 404s or a blocked crawl: the conditions that trigger a rollback are agreed in advance.

  • A rehearsed switch-back

    DNS or redirect changes reversed in a tested order, so going back is a procedure, not a scramble.

  • Fix, then relaunch

    Issues fixed on staging and re-tested before the second launch, with the redirect map updated.

FIG 10 · Measurement

What to expect after launch

Google says it can take a few weeks or more to show the new URLs, and visibility may fluctuate temporarily. After a hosting move a temporary drop in crawl rate is normal. These are the checkpoints we work to, as agreed in your written scope.

Post-launch monitoring checkpoints
CheckpointWhat we checkWhy
Launch dayRedirects, robots.txt, noindex tags, forms, checkout, analytics tagsCatch blocking errors in the first hours
First weekCrawl errors, 404s, indexing of key pages, crawl rateGoogle starts discovering the new URLs
First monthImpressions, clicks and rankings for key pages against the baselineSpot pages that lost ground and fix them
180 daysDomain moves: the end of the Change of Address windowGoogle’s forwarding signals run for 180 days
1 yearRedirect review before any clean-upGoogle advises keeping redirects at least 1 year

We don’t promise zero ranking change. We plan for the fluctuation Google describes and fix what the data shows.

FIG 11 · Process · 7 steps

Inventory first, then move

A fixed written quote after the inventory, and a rollback plan signed off before launch day.

  1. Step 01

    Inventory

    Crawl the site, pull Search Console and analytics data and list every URL, template, integration and backlink target.

  2. Step 02

    Plan

    Redirect map, content mapping, launch checklist and rollback triggers, in a written scope with a fixed quote.

  3. Step 03

    Build and migrate on staging

    New templates built, content and media migrated, redirects loaded, all on a staging site blocked from search.

  4. Step 04

    Test

    Redirects, metadata, structured data, forms, checkout and speed tested against the old site before anything switches.

  5. Step 05

    Launch

    DNS and redirects switched in a planned window, sitemaps submitted and Change of Address started for domain moves.

  6. Step 06

    Monitor

    Search Console, analytics and crawl checks at the agreed checkpoints, with fixes as the data comes in.

  7. Step 07

    Close out

    A final report, the redirect map and the handover, with the old site retired once the rollback window has closed.

FIG 12 · What you get

Everything included

Written into your fixed quote, so you know exactly what you are paying for before work starts.

12items

  • Full URL inventory
  • Written scope and fixed quote
  • Page-to-page 301 redirect map
  • Content and metadata mapping
  • Structured-data parity check
  • Staging site blocked from search
  • Pre-launch test report
  • Launch-day checklist
  • Written rollback plan
  • Search Console and sitemap setup
  • Post-launch monitoring report
  • Redirect map, content and accounts, all yours

FIG 13 · Tech & tools

The tools behind the work

Proven, well-supported tools, chosen for your project and set up in accounts your business owns.

  • Screaming Frog
  • Google Search Console
  • GA4
  • Change of Address tool
  • WordPress
  • WooCommerce
  • Webflow
  • Shopify
  • Magento
  • Drupal
  • Wix
  • Squarespace
  • Next.js
  • Cloudflare
  • Vercel

FIG 14 · Who it’s for

Website migrations for every kind of site.

The risk is different for each, so the plan is too.

3 audiences

Marketing sites

Keep the pages that bring leads.

Service pages, blog posts and landing pages moved with their rankings protected, and forms tested end to end.

  • Redirects for every blog post
  • Forms and CRM tested
  • Content parity checks
  • Search Console monitoring

FIG 15 · Working with us from the USA and UK

Built in New Delhi. Run on your hours.

Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.

Three ways to work together

  1. 01

    Fixed-scope project

    A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.

  2. 02

    Dedicated team

    Designers and engineers on your roadmap every month, billed monthly.

  3. 03

    White label

    For US and UK agencies: our work, your brand, unbranded deliverables.

Every engagement

  • Fixed quote in USD, GBP or INR after a free 30-minute call
  • NDA before discovery. You own all code, designs and content
  • A working demo every sprint, not status slides
  • Reply within one business day, calls inside your hours
Book a call

Calls on ET or UK hours

FIG 16 · Checklist

How to choose a website migration company

Most website migration companies say they protect SEO. Ask how.

How to choose a website migration company
Ask forWhy it mattersWhat good looks like
A full URL inventoryUnlisted URLs can’t be redirectedCrawl, sitemaps, Search Console and analytics combined
A page-to-page redirect mapRedirecting everything to the home page loses rankingsEach old URL mapped to its closest new page
Staging testsProblems are cheaper to fix before launchA staging site blocked from search, tested against the old one
A rollback planLaunches can failWritten triggers and a rehearsed switch-back
Honest expectationsGoogle says visibility may fluctuateNo “zero ranking loss” promises
Post-launch monitoringIssues show up over weeks, not hoursCheckpoints agreed in the scope

FIG 17 · Compare

Migrate and redesign at the same time, or one after the other?

Migrate and redesign at the same time, or one after the other?
Migrate first, redesign laterMigrate and redesign together
RiskLower: fewer changes at onceHigher: more variables if rankings move
Diagnosing problemsEasier to trace what caused a dropHarder to separate cause and effect
CostTwo projectsOne project, often less total effort
Time to the new lookLongerShorter
Best forSites that rely heavily on organic trafficSmall sites, or sites with little to lose in search

FAQ

Frequently asked questions

Straight answers about Website Migration with Elgrith.

It can if it is done badly. Done well, rankings usually settle once Google has processed the move. Google itself says visibility “may fluctuate temporarily during the move”, so we don’t promise zero change. We protect rankings with a full URL inventory, page-to-page redirects, content parity checks and Search Console monitoring.

Free 30-minute call

Move your site. Keep your rankings.

Tell us what you are moving from and to. After a free migration review call you get a URL inventory plan, a written scope and a fixed quote.

connect@elgrith.com+91 96039 20001Start a project

Pick a day for your call

Open

Pick a day. You'll choose a time in your own time zone on the next step.

See all times