Skip to content

Web development

Website and platform migrations

A migration moves a website or store to a new platform without losing its content, product data or search visibility. It suits businesses outgrowing their current platform who cannot afford to lose rankings, orders or historical URLs in the move.

When this helps

Problems this solves

  • A platform that can no longer support how the business trades.
  • Fear of losing search rankings and traffic in the move.
  • Product data spread across a platform, spreadsheets and supplier files.
  • A previous migration that broke URLs and was never fully cleaned up.

Scope

What's included

Every quote lists the deliverables in writing, so there is no ambiguity about what you receive.

Deliverables

  • Migration plan covering platform, catalogue, content, integrations and cutover.
  • Product and content transfer with agreed field mapping and data validation.
  • Full URL inventory and redirect mapping from old to new addresses.
  • Staging build and checks on the journeys that matter before launch.
  • Launch verification: redirects, status codes, canonical handling, tracking and sitemaps.
  • Rollback plan and a post-launch monitoring window of an agreed length.

Not included as standard

  • Ranking and traffic outcomes are not guaranteed; the aim is to avoid avoidable loss.
  • New design or new functionality is a separate scope from the migration itself.
  • Historic data that does not exist in a usable form cannot be recreated.

Anything here can be added to the scope and priced separately.

Defined starting point

Store or website migration

Fixed price after scoping

Typically includes

  • Migration plan with agreed field mapping
  • Catalogue and content transfer to staging
  • Redirect map from the full URL inventory
  • Pre-launch checks on agreed journeys
  • Launch verification and rollback plan
  • Agreed post-launch monitoring window
Price this work

Process

How the work runs

  1. Step 1

    Inventory

    List URLs, data, integrations and anything that must survive the move.

  2. Step 2

    Plan

    Agree mapping, redirects, cutover sequence and rollback.

  3. Step 3

    Build

    Migrate to staging and validate data against the source.

  4. Step 4

    Launch

    Cut over, verify redirects and tracking, then monitor.

What I need from you

  • Access to both platforms, DNS and analytics.
  • A decision on what must move and what can be retired.
  • Time from someone who knows the current data.

What changes the price

  • Catalogue and content volume, and source data quality.
  • Number of integrations to rebuild.
  • How many URLs need mapping, and whether patterns are consistent.
  • Whether design changes at the same time.

Experience

Relevant background

Career experience includes Magento 1 to Magento 2 migrations and moving server infrastructure to DigitalOcean.

Questions

Frequently asked questions

Related

Magento 2 development

Magento 2 storefront development, multi-store setups, theme improvements, catalogue functionality, integrations and scoped technical fixes.

Read more

SEO services

Technical SEO, on-page optimisation, information architecture, internal linking, structured data and migration checks.

Read more

Product data & feed management

Attribute mapping, catalogue imports, data validation, Shopping and marketplace feeds, and connected product-data workflows.

Read more

Get a fixed cost for website & platform migrations.

Share a little about your website, your goals and what is getting in the way. I'll use that to work out the right scope and next step.