Platform migrations

Change platform without
losing what you've earned.

The catalogue import is the visible part of a migration. The URL map is the part that decides whether you keep years of rankings, links and traffic, and it's the part most quotes leave out.

  • Complete redirect map, live at launch
  • Data validated against the source
  • Four weeks of monitoring afterwards
What's involved

What a migration
actually involves.

Most migration quotes describe the data transfer and go quiet about the URLs. That's backwards, moving products is largely mechanical, and preserving fifteen years of accumulated search authority is the part that needs judgement.

  1. 01

    Inventory every URL

    We crawl the existing site and list every URL, including the ones you've forgotten, old category archives, retired product pages, blog posts from three redesigns ago. Anything carrying traffic or backlinks goes on a must-preserve list.

  2. 02

    Map the data model

    Products, variants, attributes, customer groups and custom fields rarely map one-to-one between platforms. We work out where each thing lands before importing anything, and write down what gets dropped deliberately rather than losing it silently.

  3. 03

    Build and validate in parallel

    The new site is built alongside the old one, with data imported to a staging environment and checked record by record against the source. Your live site keeps trading throughout.

  4. 04

    Write the redirect map

    Every old URL gets a 301 to its closest new equivalent. Not a blanket redirect to the homepage, which passes almost nothing and is the single most common reason migrations lose rankings. You review the map before it goes live.

  5. 05

    Cut over and watch

    Launch is a DNS change with redirects already in place, so there's no window where visitors hit something broken. Then four weeks of monitoring Search Console and analytics, because migration problems surface gradually rather than immediately.

FAQ

Before you migrate

Will a platform migration cost us our Google rankings?+

Only if the redirects are incomplete. Every URL that changes needs a 301 to its closest new equivalent, live at the moment of launch rather than added afterwards. Done properly you see a short dip over two to four weeks then recovery. Done badly (partial redirects, or everything pointed at the homepage), the losses can be permanent.

How long does a migration take?+

Three to six weeks for most, longer for large catalogues, subscription rebuilds or Magento stores with years of accumulated data. You'll get an exact timeline with the fixed-price quote.

Will the site be down during the switch?+

No. The new site is built and validated in parallel. The cutover is a DNS change with redirects already in place, so there's no window where visitors hit something broken.

Can our customers keep their accounts?+

Customer records and order history transfer. Passwords cannot (they're hashed and not portable between platforms), so customers reset on first login. We build that flow and prepare the email before launch rather than letting people discover it.

What if our migration isn't listed?+

We handle pairs that aren't on this page, BigCommerce, Etsy, Drupal, custom builds and others. Describe what you're on and where you want to be on the quote form.

Get a quote for your migration.

Tell us what you're on and where you want to be. We'll come back within one business day with scope, timeline and a fixed price, including how we'll handle the redirects.

Start your free quote