From Magento 1 to Magento 2, properly.
Magento 1 went end-of-life in June 2020. If you're still on it, you're patching with community releases (OpenMage / Mage One) and slowly running out of extension vendors. Migration to Magento 2 isn't a copy-paste job — it's effectively a rebuild with data carried over. Done well, it's the platform you'll happily run for the next 5+ years.
Who this is for
- Magento 1 store still trading, with declining vendor support around you
- Failed a PCI assessment because of M1 end-of-life
- Want to consolidate before peak trading season
- Outgrown your current Magento 1 build technically or visually
What we'll do
The actual sequence, not a vague promise.
- 01Discovery and audit
Full audit of your current M1 store: extensions, customisations, theme, data volume, integrations. Honest assessment of what carries over and what gets rebuilt.
1–2 weeks - 02Migration plan and quote
Written plan covering data migration approach, extension replacements, theme rebuild scope, SEO preservation, training. Fixed quote based on actual scope, not guesswork.
1 week - 03Build phase
M2 environment provisioned, theme built, extensions installed and configured, customisations rewritten. Iterative reviews so you see progress, not surprises.
4–8 weeks - 04Data migration
Customers, orders, products, categories, CMS pages, URL rewrites — all carried over using Magento's migration tool plus custom scripts for anything bespoke.
1–2 weeks - 05QA and stakeholder sign-off
Full regression pass, performance testing, SEO check, accessibility check. You walk through it before we cutover.
1–2 weeks - 06Cutover and stabilisation
Final data sync, DNS change, monitoring on. 30 days of intensive support included to catch and fix anything real traffic surfaces.
30 days
What you get
Every engagement starts with a fixed quote. The price doesn't move once we've agreed it — if scope changes mid-project, we agree the variation before any work happens.
Common questions
How long does an M1 → M2 migration take?+
Typical project: 8–14 weeks calendar time. Small stores with stock theme can be 6 weeks; complex B2B with custom workflows can stretch to 5+ months. The audit phase gives you a real number, not a guess.
Can you preserve our SEO during migration?+
Yes, and it's a major focus. Every URL gets a 301 redirect, every meta tag is carried over, every internal link is rewritten, sitemap and robots.txt are managed through cutover. Properly done, you should see no SEO impact.
What about our M1 customisations?+
Some carry over, some don't. M2's architecture is fundamentally different — observers, plugins, and DI replace M1's class rewrites. Magento Patches catalogues every customisation up front and confirms what is a port, what is a rebuild, and what is obsolete.
Do we have to migrate to Magento 2 now?+
Not always. Magento Patches can stabilise Magento 1 in the short term where that is commercially sensible, then plan the Magento 2 migration properly. If security, payment compatibility or extension support has become too risky, the recommendation will be to move.