Skip to main content

Website Migration

Move your website without losing traffic, orders or email

Hosting moves, domain changes and platform switches go wrong in predictable ways. We plan migrations around those failure points, rehearse them on staging and keep a rollback route open until the new site is proven.

Zero data loss checksDNS cut-over planned

Business impact

What a poorly planned migration can cost

Most migration problems are not visible on launch day. They show up over the following weeks as missing enquiries, falling search traffic or email that quietly stopped arriving.

Search visibility

Changed URLs without correct 301 redirects, lost metadata or a staging noindex tag left in place can cause a significant drop in organic traffic.

Email and integrations

DNS changes made without carrying over MX, SPF, DKIM and DMARC records can interrupt business email, while hard-coded IP addresses break integrations and payment callbacks.

Data loss during cutover

Orders, form submissions and account registrations made between the final sync and the DNS switch can be lost unless the cutover is planned around them.

Common issues

Problems we regularly solve

Missing or chained redirects

Old URLs returning 404 errors, or redirecting through several hops, wasting link equity and frustrating visitors who arrive from bookmarks and search results.

DNS records left behind

Only the website records moved, while email, verification and subdomain records are forgotten, breaking services that nobody associated with the website.

High TTLs slowing the switch

DNS records with long time-to-live values, so some visitors keep reaching the old server for hours after the change.

Environment differences

A different PHP version, missing extensions, changed file permissions or cron jobs not recreated on the new server.

Staging settings in production

Search engine blocking, test payment keys or disabled emails accidentally carried over to the live site.

No rollback plan

The old environment cancelled too early, leaving no way back if a serious problem appears after launch.

What's covered

What's included in website migration

We handle hosting migrations, domain changes, HTTPS moves, server consolidations and platform changes, such as moving from Magento 1 or OpenCart to a supported platform. Each migration follows the website migration checklist approach, adapted to your site.

Discovery and inventory

Cataloguing pages, URLs, DNS records, email routing, integrations, scheduled tasks and server dependencies before anything moves.

Redirect mapping

Building a one-to-one redirect map from old URLs to new ones, prioritising pages with traffic, backlinks and conversions.

Environment build and rehearsal

Preparing the new environment with matching software versions, running a full trial migration and testing it before the real cutover.

DNS and email continuity

Lowering TTLs in advance, replicating every required record and checking email authentication. See domain, DNS and SSL management.

Cutover and data sync

A scheduled cutover with a content or order freeze where needed, a final data sync and immediate post-launch verification.

Post-migration monitoring

Watching for 404 errors, crawl issues, performance regressions and integration failures in the weeks after launch.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

On onboarding

  • Full inventory of site, DNS, email and integrations
  • Baseline crawl and performance measurements
  • Verified backup of the source environment

On demand

  • Trial migration and test plan run
  • Final sync, cutover and DNS change
  • Rollback if acceptance checks fail

Daily

  • Post-launch error and 404 monitoring during the stabilisation period
  • Form, checkout and email delivery checks

Weekly

  • Search Console coverage and crawl review after launch
  • Redirect map refinement based on real traffic

Our methodology

How we work

  1. 1

    Discover

    We inventory everything the website touches – content, URLs, DNS, email, integrations, cron jobs – and record a baseline of traffic, rankings and performance.

  2. 2

    Plan

    A written migration plan sets out the redirect map, cutover timing, freeze periods, acceptance tests and rollback criteria, agreed with you in advance.

  3. 3

    Rehearse

    A full trial migration to the new environment is tested end to end, so the real cutover follows a proven sequence.

  4. 4

    Cut over

    With TTLs already lowered, we perform the final sync, switch DNS and run acceptance checks, keeping the old environment ready for rollback.

  5. 5

    Stabilise

    We monitor errors, search coverage and integrations after launch and hand over documentation of the new environment.

Business benefits

What you gain

Lower risk to search traffic

Careful redirect mapping and post-launch monitoring are designed to protect the visibility you have built.

Uninterrupted email

DNS and email records are migrated deliberately so business communication continues during the switch.

A way back

A tested rollback plan means a serious problem becomes a short delay rather than a crisis.

Documented new environment

You finish with written documentation of the new hosting, configuration and DNS.

Technologies supported

  • rsync
  • mysqldump
  • WP-CLI
  • Composer
  • Cloudflare
  • Google Search Console
  • Screaming Frog
  • Nginx
  • Apache
  • cPanel
  • AWS
  • Let's Encrypt

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs website migration?

Businesses changing hosts

Companies leaving shared hosting, a previous agency's server or an unreliable provider. See also hosting management.

Stores replatforming

Retailers leaving an end-of-life or outgrown platform who need products, customers, orders and URLs carried across.

Organisations rebranding

Businesses moving to a new domain that need old links, email addresses and search visibility handled properly.

Industry guidance: E-commerce · Professional Services · Education

FAQs

Website Migration: common questions

Will my website be offline during the migration?
For most sites the switch is designed to avoid noticeable downtime, because the new environment is fully prepared before DNS changes. Stores and sites with frequent data changes may need a short freeze window, which we schedule for a quiet period.
Will we lose search rankings?
Some short-term fluctuation is normal after any significant change and nobody can guarantee rankings. Careful redirects, preserved metadata and post-launch monitoring are designed to keep disruption to a minimum.
What happens to our email when DNS changes?
We record every existing DNS record before the move, including MX, SPF, DKIM and DMARC, and recreate them at the new provider. Email hosted separately from the website should continue working throughout.
What access do you need?
Access to the current and new hosting, the domain registrar or DNS provider, the website admin, and any services that integrate with the site. Access is time-limited to the project unless you move into ongoing maintenance.
Can you roll back if something goes wrong?
Yes. We keep the old environment intact and agree rollback criteria in advance. Rollback normally means pointing DNS back, and we plan how to handle any data created on the new site in the meantime.
Is a redesign or rebuild part of migration?
No. Migration moves an existing site or its data to a new environment or platform. Design and rebuild work can run alongside it but is scoped and quoted separately.

Plan your migration before you move anything

Book a consultation to talk through your migration, the risks specific to your site and the plan we would follow to move it safely.