Halloween is the rehearsal. Black Friday is the horror show.Black Friday season is here. Every slow second costs you sales. Try Nightmare Mode →

MAGENTO 1 MIGRATION

From Magento 1
to Magento 2 and Hyvä

Adobe ended support for Magento 1 in June 2020. We move the store to Magento 2 on Hyvä: products, customers, orders and 301 redirects for the old addresses.

What staying on Magento 1 means in 2026

  • On Magento 1No security patches from Adobe since June 2020.

    On Magento 2 with HyväA platform that receives security updates.

  • On Magento 1Modules and integrations that fewer and fewer people maintain.

    On Magento 2 with HyväPayments and couriers maintained together with the platform.

  • On Magento 1Pages that load slowly on phones. At Equitana, shoppers waited up to 4.2 s for the main content.

    On Magento 2 with HyväAt Equitana, after the move: 1.1 s on phones, measured by Google on real shoppers.

  • On Magento 1Core Web Vitals failed, on phones and on desktops (Equitana, August 2026).

    On Magento 2 with HyväCore Web Vitals passed on both, in real-user data.

Case studies

From our case studies

  • Equitana

    Equitana sold on Magento 1 until August 2026. We rebuilt the store on Magento 2, Hyvä and the Liquid Framework in five days, and moved 14,500+ products, 300+ categories, 3,400+ customer accounts and 12,000+ orders. On phones, the main content now appears in 1.1 s instead of 4.2 s.

    Read the Equitana case study
How it runs

The move from Magento 1, step by step

The same steps for every store. How long it takes depends on the catalog, the integrations and what you want to keep.

  1. 1. The inventory

    We go through the current store: catalog, customers, orders, modules, integrations (ERP, couriers, payments), content pages and the blog. Together we decide what moves, what gets replaced and what stays behind.

  2. 2. The new store, on a platform that already exists

    We start from the Liquid Framework: Magento 2 with Hyvä, Hyvä Checkout and maintained modules. The time goes into your store, not into the basics.

  3. 3. Moving the data

    We move the products, categories, customer accounts and order history, then check the counts on a test store.

  4. 4. The page addresses

    We keep the old addresses where we can and set 301 redirects where they change, so links from Google and from your campaigns reach the right page.

  5. 5. Testing

    You walk through the new store before launch: search, cart, checkout, payments, couriers. We fix what you find.

  6. 6. Launch and the first weeks

    We switch to the new store and watch orders, speed and errors. After launch the store stays in our care, on the Liquid Framework.

What moves and what changes

What moves

  • Products and categories
  • Customer accounts
  • Order history
  • Page addresses, with 301 redirects where needed

What changes

  • The theme: a Magento 1 theme does not run on Magento 2, so we build it on Hyvä
  • The checkout: Hyvä Checkout
  • The modules: Magento 1 modules are replaced with maintained equivalents
  • The hosting: the store runs on the Liquid Framework infrastructure

The blog and the content pages do not move by themselves. We put them in the inventory on day one, so they are not left behind.

FAQ

Questions about moving off Magento 1

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

It depends on the catalog, the integrations and how much content the store has. At Equitana, building the new store took five working days, and about a month passed from the start of the work to launch, with testing and the data move. We give you a date after the inventory.

What does the migration cost?

We quote each store after the inventory. The price depends on the catalog, the integrations and what you keep from the old store.

Do customers and orders come along?

Yes. We move the customer accounts and the order history. At Equitana that was 3,400+ accounts and 12,000+ orders, going back to 2019.

What happens to our Google rankings?

We promise no rankings. What is in our hands: we keep the page addresses where we can, set 301 redirects where they change and move the content listed in the inventory. Pages that do not move, a blog left behind for example, lose their traffic. That is why they go into the inventory from the start.

Do we have to move to Hyvä too, or only to Magento 2?

A Magento 1 theme does not run on Magento 2, so the visible part of the store is rebuilt either way. We build it on Hyvä from the start, so you do not pay for two rebuilds.

Our store runs Magento 1 on a hosted platform. Can it move?

Yes. Equitana ran Magento 1 on a hosted platform and moved to Magento 2 with Hyvä. The case study has the details.
Get in Touch

Ready to Transform Your Magento Store?

Fill out the form below and we'll get back to you within one working day.

Contact Us Illustration

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Working Hours

Monday - Friday

9:00 AM - 6:00 PM

Saturday - Sunday

Closed

Critical Incidents

Clients with a support contract open a ticket in ClickUp: critical incidents (store down or payments broken) get a response within 2 working hours. Not a client yet? Write to contact@liquidlab.ro.

OR

Schedule a Meeting

Book a convenient time to discuss your project with our team

Schedule a Meeting