Magento

E-commerce Migration to Magento: A Step-by-Step Guide

Maria

9 min read

This guide is for stores on WooCommerce, Shopify, a custom PHP build or an older platform that are thinking about moving to Magento. It covers when the move makes sense, what you can carry over and what gets rebuilt, the steps of an e-commerce migration to Magento, and what drives the timeline and cost. It's based on migrations we've delivered, including two we describe below.

When moving to Magento makes sense (and when it doesn't)

Stores rarely move to Magento because of one missing feature. They move because the business has outgrown what the current platform does well. The usual signs:

  • B2B on top of B2C. Dealers, wholesale buyers or trade customers need their own prices, terms and accounts, and the current setup handles it with workarounds.
  • Several stores or brands. You run them on separate installations and copy products, prices and customers between them by hand.
  • A complex catalog. Parts that fit specific models, products sold by size or configuration, thousands of attributes.
  • Integrations that keep breaking. An ERP, warehouse or PIM connected through plugins that weren't built for that load.

Magento is not the right move for every store. If your catalog is simple and you'd rather not run servers, a hosted platform can cost less to own. We compare the two honestly in Magento vs Shopify. And if you're already on Magento 1, that's a different project: an upgrade to Magento 2.

What moves and what gets rebuilt

Moves with scripts Gets rebuilt in Magento
Products, categories, attributes and images Theme and page layouts
Customers and their addresses Custom pricing and checkout logic
Order history What your plugins or apps did, as Magento modules
Reviews Integrations with your ERP, PIM or warehouse
CMS pages and blog posts Email templates
URLs, as a map of 301 redirects Reports your team relies on

Customer passwords may not carry over, depending on how the old platform stores them. Plan a password reset email for launch day so returning customers aren't surprised.

Moving from WooCommerce

WooCommerce stores usually come to Magento when B2B or several stores stop fitting into plugins. What to expect:

  • Products. Simple products move as they are. Variable products become configurable products in Magento, and their attributes (size, color, length) become Magento attributes with options. This is the right moment to merge duplicate attributes that plugins created over the years.
  • Wholesale and dealer prices. On WooCommerce these usually live in a plugin, a user role or a spreadsheet. In Magento they become customer groups with their own prices, tier prices or price rules, so they need to be designed, not just copied.
  • Customer passwords. WordPress password hashes don't work in Magento out of the box. Either add a small module that checks the old hash on first login and saves a new one, or send a reset email at launch.
  • URLs. WooCommerce product URLs usually look like /product/name/, while Magento uses its own structure. Every product, category and blog URL with traffic needs a redirect.
  • The blog. If content lives in WordPress, you can keep WordPress for the blog and move only the store, or move posts into Magento or a separate CMS.

Moving from a custom PHP store

A custom store has no export tool and no standard structure, so the migration starts with reading the code and the database:

  • Find the business logic. Pricing, discounts and stock rules are often hidden in code that nobody has documented. Write them down before rebuilding them in Magento.
  • Export with scripts. Products, customers and orders are pulled from the old database with migration scripts, cleaned and mapped to Magento's structure.
  • Old hosting. Custom stores often run on old PHP versions that current libraries no longer support, so the old site stays frozen while the new one is built.
  • Specialist features. Parts finders, compatibility tables and configurators are usually the reason the store was custom in the first place. They are rebuilt as Magento modules, often better structured than before.

Data mapping: an example

Before any script runs, each piece of data gets a place in Magento. A typical map for a B2B store:

In the old store In Magento
Product with variations Configurable product with child products
Product attribute (size, color) Attribute with options, used in filters
Wholesale role or dealer account Customer group
Dealer price list Group prices, tier prices or a price rule
Coupon Cart price rule
Order with status Order with mapped status and history
Static page CMS page, with the old URL redirected

E-commerce migration to Magento, step by step

1. Audit what you have

List everything the current store does, not just the data: plugins and what each one is for, integrations, custom code, email flows, and the pages that bring search traffic. The traffic list comes from Google Search Console and decides which URLs need the most care.

2. Map the data

Decide how products, attributes, customer groups and prices from the old platform fit Magento's structure. This is where B2B rules get designed: which customer group sees which price, and where those prices come from.

3. Build on a staging site

Install a current Magento 2.4 release, build the theme and rebuild the custom features on a staging copy that customers can't see. Your live store keeps selling as usual.

4. Migrate the data, then test it

Run the migration scripts against staging and check the result against the source: product counts, prices per customer group, order totals, customer accounts. Run it again until the numbers match.

5. Protect your search rankings

Map every old URL that has traffic or links to its new address and set up 301 redirects. Carry over titles, meta descriptions and structured data. Fix internal links that still point to old URLs.

6. Connect the integrations

Reconnect the ERP, warehouse, payment and shipping systems to Magento and test them with real scenarios: a new order, a stock update, a price change, a return.

7. Test like a customer

Place test orders with every payment and shipping method, for every customer group. Check emails, invoices and the admin workflow your team uses every day.

8. Launch with a final delta

Freeze changes on the old store, migrate only what changed since the last run (new orders, customers, stock), switch the domain and run a final round of checks.

9. Watch the first weeks

Monitor 404 errors and crawl reports in Search Console, fix missed redirects quickly, and compare search traffic for your key pages before and after.

SEO checklist for the migration

Search traffic is the part of a migration that's hardest to win back, so it gets its own list:

  • Export every URL with impressions or clicks from Google Search Console for the last 12 months
  • Map each one to its new URL; nothing with traffic redirects to the home page
  • Keep page titles and meta descriptions, or improve them deliberately, not by accident
  • Carry over structured data for products (price, availability, reviews) and breadcrumbs
  • Keep product image file names and alt texts where they bring image search traffic
  • Generate a new XML sitemap and submit it in Search Console on launch day
  • Check that staging is closed to search engines, and that the live site isn't
  • After launch, review 404 errors and redirect chains every few days for the first month

How long it takes and what drives the cost

On our recent migrations to Magento, a first store took about 6 to 8 months, including custom B2B features. Additional stores on the same platform go faster, because the catalog, integrations and most of the code are already in place.

What drives the cost:

  • How much custom logic has to be rebuilt, especially pricing and checkout
  • The number of integrations and how well the other systems document their APIs
  • The size and cleanliness of the catalog
  • How many stores, languages and currencies you run
  • The SEO risk: how much search traffic the current URLs carry

Every project should start with a written plan and a fixed estimate, so you know the scope before any work begins.

Two migrations to Magento we delivered

From WooCommerce: a trailer manufacturer selling through dealers. A US trailer manufacturer ran two WooCommerce stores that lacked the B2B features and flexibility the business needed. We moved them to Magento 2. Today four stores run on one platform. More than 100 dealers and 130+ locations are shown on product pages, so buyers go to a dealer instead of the store competing with them, and about 37,000 dealer prices are recalculated automatically. The first two stores launched together in 6 to 8 months, and the next ones followed about every 6 months. Read the case study.

From a custom PHP store: an engine parts manufacturer. An international manufacturer of precision engine parts replaced its custom store on PHP 5.6 with Magento 2, built from scratch in 7 months by a team of four. The new store handles about 29,000 products, around 2 million compatibility links for finding parts by vehicle or engine, and 15 price levels for dealers with about 100,000 prices, with two websites in one installation. It has taken nearly 7,000 online orders. Read the case study.

Mistakes we see most often

  • Moving the data, but not the logic. Prices and discounts look right in a spreadsheet, then behave differently at checkout. Test pricing for every customer group.
  • Leaving redirects for the last week. The URL map should be ready before the build ends, not on launch day.
  • Migrating everything. Ten years of discontinued products and test customers make the new store slower and harder to manage. Clean up first.
  • One big launch with no rehearsal. Run the full migration on staging at least twice before going live.

Questions about migrating to Magento

Can you migrate my existing online store to Magento?

Yes. We've moved stores to Magento from WooCommerce and from custom PHP builds, and the same approach works for other platforms. The first step is an audit of what your store does today, followed by a plan and a fixed estimate.

Will we lose our search rankings?

Not if every URL with traffic is redirected to its new address and titles, descriptions and structured data move with it. Expect some movement for a few weeks after launch while search engines recrawl the site.

How long does a migration to Magento take?

For an established store with B2B features, plan for several months. A simple catalog with standard features takes less. The audit gives you a timeline for your store.

What about older platforms such as Interspire?

The steps are the same. Most of the work is in exporting clean data from the old system and mapping its URLs to the new store.

Can we keep selling during the migration?

Yes. The new store is built and tested on a staging site, and the old store keeps selling until launch. Only the final delta of new orders and customers is moved at the switch.

Planning a move to Magento? Tell us what you run today and what's holding you back, and we'll come back with a plan and a fixed estimate. See our e-commerce migration services, or, if you're on WooCommerce, our WooCommerce to Magento migration. For B2B pricing, dealer accounts and customer-specific catalogs, see B2B commerce on Magento.

Are we a good fit? Let's discuss.

Tell us about your store and what you want to get done. If we're a fit, you get a clear next step. If not, we'll tell you.

  • Reply within one business day
  • Fixed estimate before we start
  • No commitment