Magento 1 to Magento 2 migration.

Your catalogue, customers, orders and rankings carried across to a supported, faster store.

Magento 1 has had no security fixes from Adobe since 30th June 2020, yet hundreds of UK stores still trade on it. We move Magento 1 and OpenMage stores to Magento 2 with a Hyvä storefront, carrying the data and the search rankings across, and we keep the old store patched and trading until the day of the switch.

For
Stores still trading on Magento 1 or OpenMage
What it is
A new Magento 2 store on Hyvä, with your data migrated into it
Price
A written estimate once we have examined the store
First step
The free health check confirms your version and what is exposed

Still on Magento 1? You are not alone.

What merchants on Magento 1 tell us when they first get in touch.

  • It still takes orders every day, so we have never been able to justify the move.

    What it usually means

    A working store is a fair reason to wait. The risk is that Magento 1 has had no security fixes from Adobe since June 2020, and attackers know which stores still use it.

  • Our payment provider has written to us about PCI compliance.

    What it usually means

    Card schemes expect supported, patched software. A dated migration plan, with the old store protected in the meantime, is usually what the provider needs to see.

  • We were quoted a fortune for a rebuild, so we did nothing.

    What it usually means

    The cost depends on what the store really needs. Much of an old Magento 1 store is no longer used, and Hyvä makes the new storefront quicker to build than it was a few years ago.

What the migration includes.

Six parts, planned together so that nothing is discovered late.

  • An inventory of the old store

    Every extension, custom feature, integration and scheduled job listed, with what replaces it on Magento 2.

  • A new Magento 2 store

    Built on the current supported release, with a Hyvä storefront designed around your brand.

  • Data migration, rehearsed

    Products, customers, orders and content moved in rehearsals and checked against the old store.

  • Search rankings protected

    Every indexed URL redirected, with titles, descriptions and structured data carried across.

  • Integrations reconnected

    Payments, shipping, stock, accounts and email marketing connected and tested end to end.

  • A planned switch

    A final data transfer and the change of address at a quiet time, with the old store kept ready as a fallback.

Before and after the move.

Without us
  • A platform with no security fixes since June 2020
  • Server software that hosts are withdrawing
  • Extensions nobody maintains
  • Payment providers asking about compliance
  • A storefront built before phones mattered
  • Every change costing more than it should
With Refined Commerce
  • A supported Magento 2 release, patched as fixes arrive
  • Current PHP on hosting built for Magento
  • Maintained modules, and fewer of them
  • A clear answer for your payment provider
  • A Hyvä storefront that is fast on a phone
  • A store that is economical to change again

What the destination looks like.

Supadance: a category page of the live store on desktop
Supadance on a phone
Dance shoes, handmade in EnglandMagento 2 and Hyvä

Supadance

A British dance-shoe maker selling worldwide, moved from a desktop-era store to a mobile-first Magento 2 store on Hyvä.

Passes Core Web Vitals on mobile
  • LCP1.3 s
  • INP112 ms
  • CLS0.01

Core Web Vitals, real-user data (Chrome UX Report), mobile, 28 days to 31st October 2026. Marks show Google's thresholds.

Rowan built our new web site a short while ago, and has helped with the any upgrades and issues since, he's always quick to respond and gives a clear message without technical jargon. Highly Recommended Magento Web site developer.

Andrew ErringtonGoogle review

How we carry out the migration.

The Magento 1 store keeps trading throughout. Customers notice a faster store, and nothing else.

  1. Step 1: The free health check

    Send us the store address. A senior engineer reads its release, support status, PHP, headers, hosting and any sign of a hijack.

    Within two working days
    Access we need
    None. Publicly served pages only; nothing is tested.
    What you receive
    One page by email, with no obligation.
  2. Step 2: We examine the store and write the plan

    The extensions, custom code, integrations, data volumes and URLs, read from the code and the database.

    Within a few working days of access
    Access we need
    Read access to the code, the server and an admin account.
    What you receive
    A written plan, an estimate and dates.
  3. Step 3: The new store is built on staging

    Magento 2 with a Hyvä storefront, the replacement modules and your custom features, built where you can see it.

    Most of the project
    Access we need
    A staging environment; we arrange one with your host.
    What you receive
    A staging address and regular written progress updates.
  4. Step 4: The data is migrated in rehearsals

    Trial transfers of products, customers and orders, each one compared with the old store until the figures agree.

    Alongside the build
    What you receive
    A reconciliation of what moved.
  5. Step 5: Your team tests it

    You place orders, check the admin and try your daily tasks on staging before anything goes live.

    Before the switch
    What you receive
    A short list of what to try, and training on the new admin.
  6. Step 6: Switch, monitor, report

    A final transfer of the latest orders and customers, the redirects enabled, then orders, payments and rankings monitored closely.

    A quiet hour agreed with you
    Access we need
    Deployment and DNS access.
    What you receive
    A written note of what was done and anything still open.

What moves, what is rebuilt and what you leave behind.

A migration is the one chance to stop carrying a decade of clutter. Your data comes with you; the parts that held the store back do not.

Carried across

  • Products, categories and attributes
  • Customers, addresses and passwords
  • Orders, invoices and shipments
  • CMS pages, blocks and reviews
  • URLs, by 301 redirect
  • Tax, shipping and store settings

Rebuilt, better

  • The storefront, on Hyvä
  • The checkout
  • Extensions, as Magento 2 modules
  • Custom features and integrations
  • Search and filtering
  • Email templates

Left behind

  • Unsupported PHP and server software
  • Abandoned extensions
  • Years of unused code and data
  • Security holes with no fix
  • Slow pages on phones
  • Compliance letters from your payment provider

We price the work, not the clock.

This service
Priced as a project: a written estimate once we have examined the store.
How you pay
Usually spread across the length of the project.
Our rate
£80 an hour plus VAT, the same for every merchant.
Never charged
Account management, or the first look at your store.

Priced as a project, once we have seen the store.

No two Magento 1 stores are alike after years of trading, so we examine yours first and then give you a written plan and estimate. Where the scope is large, we agree it in phases so the estimate firms up as the detail does. Payment is usually spread across the length of the project.

  • Written plan and estimate before anything starts
  • Payment usually spread across the project
  • The old store kept patched while the new one is built
What happens first
  1. We read the extension list, the custom code and the size of the catalogue.
  2. Each extension is matched to its Magento 2 equivalent, or marked as no longer needed.
  3. You get a written note of what the move involves before the full plan is written.
How our pricing works

Is this the right service for your store?

This is for you if

  • Your store uses Magento 1 or OpenMage and still trades
  • You want to keep your customers, order history and rankings
  • Your payment provider or host is pressing you to move
  • You want to stay on Magento for its depth and flexibility

If your situation is different

Why merchants bring this work to us.

About Refined Commerce
  • 2008

    On Magento since its early releases

    Decades of collective experience across Magento 1, Magento 2, Adobe Commerce, Hyvä and Shopify. Very little about your store will be new to us.

  • 1

    Point of contact, and senior engineers only

    You deal directly with the founder. No juniors learning on your store and no account managers between you and the people doing the work.

  • 5.0

    On Google, from 23 merchant reviews

    Small stores and large ones, described in their owners' words. The reviews are quoted on this site word for word.

Questions merchants ask about this.

Is Magento 1 still supported?

Not by Adobe. Official support for Magento 1 ended on 30th June 2020, so Adobe has shipped no security fixes for it since. The community project OpenMage LTS continues to maintain a version of Magento 1, which is how many Magento 1 stores are still kept patched today.

Can Magento 1 be upgraded to Magento 2?

Not in place. Magento 2 is a different application, so the move is a migration: a new Magento 2 store is built, and your products, categories, customers, orders, content and settings are transferred into it. Themes and extensions do not carry across and are replaced with their Magento 2 equivalents.

Will we keep our customers, orders and passwords?

Yes. Customer accounts, addresses, order history, products, categories, reviews and CMS content are migrated, and customers sign in with the passwords they already have. The data is moved in rehearsals first and compared with the old store before the switch.

Will we lose our Google rankings?

Not if the move is planned for it. Every indexed Magento 1 URL is mapped to its new address with a 301 redirect before the switch, page titles, descriptions and structured data are carried across, and Search Console is monitored afterwards. A faster Hyvä storefront usually helps rather than harms.

How long does a Magento 1 to Magento 2 migration take?

It depends on the size of the catalogue, the number of extensions to replace and how much of the old store was custom. A small store can be moved in a few weeks; a large one with integrations takes longer. The written plan gives you dates before you commit, and the Magento 1 store keeps trading until the day of the switch.

What does it cost?

It is priced as a project once we have examined the store, and you get a written estimate before anything starts. Payment is usually spread across the length of the project. The first look and the estimate are free.

Can we stay on Magento 1 for now?

Yes, with care. We can move the store to OpenMage LTS or keep it patched, put a firewall in front of it and monitor it, so it stays as safe as an out-of-support platform can be while you plan. It is a bridge, and we will say plainly how long we think it should last.

Should we move to Shopify instead?

Sometimes. If you sell a simple catalogue to consumers and would rather not maintain a platform, Shopify can be the better answer; if you rely on complex pricing, several stores or deep integrations, Magento 2 usually is. We do both, so we will tell you which suits your store. See Magento to Shopify migration.

Still on Magento 1? Find out exactly what your store exposes, free.

Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.

  • Magento Open Source, Adobe Commerce and Mage-OS stores
  • No login, no access, no obligation
  • Written by a person, not a scanner
Free store health checkOne page, by email

5.0 from 23 Google reviews

Free, with no obligation. We read only what your store serves publicly; nothing is accessed or tested, and it is not a security guarantee. Privacy notice.
What you receive
Example report
Magento Security and Upgrade Health Check
example-store.co.ukNeeds attention
Platform
Magento Open Source 2.4.4-p3
Adobe support
ended 12th April 2025
PHP
8.1, end of life 31st Dec 2025
Frontend
Luma
Security headers
2 of 6 present
Hijack indicators
none found

What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.

Free health check