Magento migration and replatforming
Magento migration that keeps your sales and your Google traffic
A new platform should bring more sales. Nobody wants to spend the month after launch explaining to the board why organic traffic fell off a cliff. We move you to Magento 2, Adobe Commerce or Shopify Plus with a 301 for each URL Google knows about, practice runs for the data, and a last sync that picks up orders placed on launch day.
- 15+ years on Magento 1 and Magento 2
- A 301 for each URL Google has indexed
- Practice runs before the real switch
- Magento 2, Adobe Commerce and Shopify Plus
18
Database tables mapped in one platform rebuild
100%
Of indexed URLs given a tested 301 redirect
20,000+
Products moved in one platform rebuild, none lost
Magento 1 or OpenMage stores moving to Magento 2 or Shopify Plus
Magento 2 stores moving to Shopify Plus to stop paying for servers and upkeep
WooCommerce and older-platform merchants who've outgrown their setup
Stores where organic search and order history are too valuable to gamble with
Businesses moving Magento to new hosting or Adobe Commerce Cloud
Migrations rarely go wrong because of the new platform. They go wrong because of what nobody counted on the old one. URLs change and the category pages that brought in most of the organic revenue get no redirect. Custom attributes, tier prices and configurable products get squashed in a CSV export, and customers find the missing sizes on launch day. Metadata, structured data and internal links stay behind, so pages that ranked for years come back thin. Orders placed while the new store was being built never arrive. Then traffic dips, and because nobody saved a Search Console baseline, nobody can say which pages dropped or why. Plan the SEO, the data and the switch-over as part of the job and you avoid all of it.
signs-you-need-this.log
- ›A big slice of your revenue comes from organic search
- ›Earlier migration quotes never mentioned redirects
- ›Your catalogue relies on custom attributes, configurables or B2B pricing
- ›Losing order history or customer accounts isn't an option
- ›The ERP, PIM or payment links have to work from the first hour
- ›A past replatform cost you rankings and nobody could say why
Six stages, each one signed off by you. SEO gets a stage of its own because it's too important to sit on a launch checklist.
- Step 01
Discovery and data audit
We go through the old store: entities, attributes, store views, customer groups, order volumes, extensions and integrations. Each item is marked to move, rebuild, replace or drop, and we catch messy data before it reaches the new platform.
- Step 02
Architecture and mapping
We choose the target stack and write the mapping document, showing where each product type, attribute, price rule, customer and order ends up. Integrations get an agreed spec. Nothing gets imported until you've approved the mapping.
- Step 03
SEO plan
We pull your indexed URLs from the sitemap, Search Console, analytics and server logs and build a 301 map with no chains. Titles, descriptions, structured data, canonicals and internal links are all mapped, and we save Search Console and analytics baselines to compare against later.
- Step 04
Build and practice runs
The code, theme and integrations are built on staging while the data goes across in practice runs. After each run we compare product, customer, order and review counts, and test the redirect map against the staging site.
- Step 05
The switch, with a final sync
The old store keeps trading until the moment we switch. A last sync then brings over any orders, customers and products created during the project. Redirects go live with the DNS change, and we can still go back if we need to.
- Step 06
Watching traffic after launch
We crawl the new store and compare it with the old crawl, check redirects, 404s and indexing in Search Console, and track organic landing pages, conversion and revenue against the baseline.
You'll see exactly what happened to rankings
We save Search Console and analytics baselines before work starts and compare the crawl after launch with the one before. If a page slips, you'll know which one and why, and we'll already be fixing it.
We know the Magento database
After 15+ years on Magento 1 and 2, we read the old database directly. Configurables, store-view overrides, tier prices and custom attributes get mapped properly instead of disappearing in an export.
Practised before the real night
The data goes across in several practice runs and we rehearse the switch on staging. On one rebuild we moved 476,648 rows across 18 tables and checked every count.
Advice that doesn't favour a platform
We build on Magento 2, Adobe Commerce and Shopify Plus, so we've no reason to push you one way. If we think you shouldn't move at all, we'll tell you before you spend anything.
From our clients
They rebuilt the entire site on a clean hardened server, migrating 20,000+ products, auditing 54 modules, and delivered a professional cutover report documenting every single step. Best developers I've worked with in 20 years of running web businesses.
Reviews from real clients. We leave their names off.
Related services
Magento 2 development
New Magento 2 and Adobe Commerce stores, B2B, Hyvä and ERP links, built to cope with your busiest day.
Performance optimisation
Faster category pages, checkout and admin, with every change measured before and after.
Magento 1 to 2 migration
Products, customers, orders and Google rankings moved from Magento 1 to Magento 2.4.9, with a practised launch.
Magento to Shopify migration
Products, customers, orders and every URL Google ranks, moved from Magento to Shopify or Shopify Plus.
Tell us what you're planning for the store.
You'll speak to one of the developers. We'll tell you which route we'd take, what usually goes wrong on projects like yours and where we'd start.
Happy to sign an NDA · Everything tested on staging first · The code is yours