Ecommerce migration services that account for every old URL.

What an ecommerce migration service covers#

A replatform is a house move with the shop still trading. Everything below goes in the truck, and every box gets counted at the other end.

• Data. Products, variants, categories, custom attributes, customers, orders, reviews, CMS pages and media, mapped field by field to the new platform's model and imported in the order the target documents.
• URLs and redirects. Every old URL inventoried and mapped, with a permanent redirect for each one that has a new home, then tested before launch. The method is below.
• Customer accounts. Accounts and addresses move across (a Shopify CSV carries only the default address), and customer groups map to the target's nearest equivalent. Passwords usually don't move, so the first login gets planned and the customer email gets written before launch day.
• Integrations. ERP, feeds, tax, shipping, payments and marketplaces, rewired and tested against the new platform.
• Theme and content. The new storefront itself, which is ecommerce development work, plus the pages, blog posts and files that rank.
• Cutover. A content freeze, a final sync of new orders and customers, the DNS switch and a written rollback plan.
• Post-launch monitoring. A launch-day crawl, Search Console watched for new 404s, and order and sync logs checked until the numbers settle.

Ecommerce platform migration services that stop at "the products imported" leave the expensive half undone: the URLs, the logins and the plumbing. We scope all seven before anything moves.

The routes we handle#

We move stores between Magento, Shopify, BigCommerce and WooCommerce in the directions below, and from a monolithic storefront to headless Next.js. Every route has one step that bites harder than the rest; the table names it.

Leaving Magento for Shopify? That route has its own page, B2B parity table included: Magento to Shopify migration.

Migrating to WooCommerce#

We move stores onto WooCommerce from Magento, Shopify or BigCommerce. WooCommerce hands you the code and the hosting, and coming from Shopify or BigCommerce, every job the platform did quietly becomes yours: caching, updates, security patches and backups. Products come in through WooCommerce's built-in CSV tool, variations and external image URLs included. Customers and orders go in through the WooCommerce REST API, which has create and batch endpoints for both. Owning the code has one perk on moving day: passwords from a Magento store can survive, as the password section below explains. Need a WooCommerce migration agency that keeps the site patched afterwards? That's a retainer.

How we map and test redirects#

Google's site-move guide is blunt about the short term: "Expect temporary fluctuation in site ranking during the move." Lasting losses usually come from linked old URLs that now answer 404. Its rules guard against those: map old URLs to new ones, use server-side permanent redirects, point each straight at its final destination and keep them for at least a year. Our method builds on them:

Shopify hides two rules in its small print. A redirect fires only from a broken URL: if anything still loads at the old path, the redirect is ignored. And Shopify redirects are one path to one target, capped at 100,000 below Plus. A large catalog with a long URL history can outgrow that cap, so we count the map before you pick a Shopify plan.

Our receipt for this method: tens of thousands of redirects mapped for a zero-downtime replatform.

Redirects are the floor of ranking protection, not the whole house. Benchmarks, content and internal-link parity, structured data and the post-launch Search Console watch belong to ecommerce SEO, before launch and after it.

Data migration and validation#

"The import finished" and "the data arrived intact" are different sentences. Plenty of ecommerce data migration services stop at the first one. We don't sign off until the second one is proven.

Before the first import, every field gets a destination on the target (a custom attribute might become a Shopify metafield), and anything with no home there is written down, not dropped. Then we import in the order the target platform documents. Shopify's is explicit: "Import your products first, then your customers, and then any historical orders," so each order can connect to its products and its customer. The same page buries a line that saves an inbox: staff set to receive new-order notifications get "a new order email for each imported order", so those notifications go off before the order import and back on after.

Before cutover, every migration passes these checks, for each entity the store has:

1. Record counts. Products, variants, categories, customers, orders, reviews and gift cards counted on both stores, entity by entity.
2. Order totals and tax. Subtotal, discounts, shipping and tax reconciled per order, and the grand total reconciled across every imported order.
3. SKU spot checks. A sample compared field by field against the old store, weighted toward best sellers and the products with the most variants.
4. Customer-group mapping. Every customer in the right group, tier or price list, so B2B buyers see their own prices the first time they sign in.
5. Attributes and media. Custom attributes, images and files present on every record that had them.
6. A signed validation report. The counts, the reconciliation and every exception we found, signed off by your team.

If a number doesn't match, the cutover waits.

Customer passwords, order history and gift cards#

Passwords usually stay behind. Shopify says it plainly: "you can't migrate customer passwords from another online store using a CSV," so "you need to invite your customers to create new passwords". That invite belongs to legacy customer accounts, which Shopify has deprecated; on customer accounts, sign-in is a one-time 6-digit code by default. Either way, Shopify's own sign-in can't take an old password. The exception is Shopify Plus with your own identity provider that imports the old hashes, which we scope per project.

Magento 1 to Magento 2 is the route where most passwords survive. Adobe's Data Migration Tool carries each customer's password hash across and tags the salted MD5 and SHA-256 hashes Magento 1 wrote, which Magento 2 still checks and upgrades the next time that customer signs in on the storefront. Passwords last set on Magento 1.9.4.3 or 1.9.4.4 are bcrypt or SHA-512 hashes that only the tool's own login plugin can check, so the tool stays installed until those customers have signed in. Hashes written by third-party extensions don't carry over.

On WooCommerce, WordPress's check_password filter lets a login plugin accept a Magento store's hashes at first login (from BigCommerce, a first-login check against its API while the old store is live), and WordPress then stores a fresh bcrypt hash, its default since 6.8. On Magento 2 and WooCommerce alike, we test real accounts of each hash type on staging before telling anyone their password still works.

Order history and gift cards go through migration apps or Shopify's Order, Transaction and GiftCard APIs, per its migration guide. The GiftCard API can recreate each card with its remaining balance, and with its original code when that code is 8 to 20 letters and numbers.

Cutting over without stopping sales#

The old store keeps taking orders while the new one is built and tested on staging. This is where an ecommerce website migration service proves itself. The switch is a rehearsed release, not a leap of faith:

1. Content freeze. Catalog, price and CMS changes stop on the old store; orders don't. Adobe's Magento 1 migration guide draws the same line: no Admin changes "except for order management".
2. Delta sync. Orders, customers and stock that changed since the main import move across in a final pass: the Data Migration Tool's delta mode on a Magento 1 move, an API job elsewhere.
3. DNS cutover. The domain moves to the new platform with every redirect already live. Same domain? Skip Search Console's Change of Address tool; Google says you only need it for moves to another domain or subdomain.
4. Rollback plan. Written before launch: what triggers it, who calls it, and how orders placed on the new store reach fulfillment if it fires.
5. Launch-day crawl. The old URL list crawled against the live site, and a test order placed and refunded through every payment method.

Then everything stays under watch until orders, syncs and new 404s are back to normal.

The integrations that move with you#

The plumbing. A new storefront means every connection behind the old one gets rewired: ERP syncs for orders, stock and prices (NetSuite or another ERP), distributor and channel feeds, tax and shipping rules, payment gateways, and eBay or Amazon connections. The failures are quiet, like a feed still reading the old store's export or a tax rule nobody re-created, and the first sign is a wrong invoice. So each connection is tested against the new platform before cutover, and a rebuilt sync runs beside the old one until the numbers match. That's the discipline behind our ERP integration work, and its proof line: ERP syncs made several times faster, with silent data loss eliminated.

Migration app or migration agency?#

Use the app when the store is simple. Call the agency when it isn't. What each tool does well:

• Cart2Cart and LitExtension are automated cart-to-cart services. LitExtension moves "products, customers, orders, blogs, and related data" and offers to carry product and category URLs across. Cart2Cart's FAQ is candid that it "cannot directly migrate customer passwords from other platforms to Shopify".
• Matrixify bulk-imports Shopify data from Excel or CSV files, redirects included: one Path and one Target per row.
• Adobe's Data Migration Tool moves Magento 1 data and settings into Magento 2, with a delta mode for the final sync, as long as its version matches your Magento 2 version exactly. Its newest release targets 2.4.8. Media files and admin users are handled outside it, and each extension's data needs its own mapping files.

Where they all stop: none of them finds the URLs that live only in your logs, backlinks and Search Console, decides what happens to a page with no obvious twin, rebuilds B2B rules the target doesn't have natively, or signs a validation report. That half is what an ecommerce migration agency is for.

Should you replatform at all?#

Sometimes the best migration is the one you don't run. An ecommerce migration company that never tells a client to stay put is selling moves, not outcomes. Before anyone maps a URL, answer three questions:

• Is the platform the problem? A slow theme, one bad extension or a version that stopped getting security patches can be fixed where it is, and that's usually a smaller job than a new platform.
• Can you upgrade in place? A Magento store on an old 2.x can take a Magento upgrade to current 2.4 and keep its URLs and data where they are.
• Does the new platform do what yours does? B2B pricing, quotes, multi-store and configurators are where platforms differ most.

When the choice is genuinely open, you want an ecommerce replatforming consultant on your side of the table before the vendor demos, not after. That's the job of a fractional head of ecommerce: the roadmap, the vendor shortlist, a P&L lens. We build on Magento, Shopify, BigCommerce, WooCommerce and headless Next.js, so there's no platform we need you to pick.

What drives the cost of a migration#

We don't publish migration prices. Two catalogs of the same size can hide very different amounts of work, and a number on a web page can't see which one you have. What sets the scope:

• Catalog and URL count: products, variants and every old URL that needs a redirect.
• Data quality: duplicates, orphaned attributes and missing SKUs get cleaned before anything moves.
• Customizations and B2B rules: custom modules, customer-group pricing, quotes and approvals to rebuild.
• Integrations: every ERP, feed, marketplace and payment connection to rewire and retest.
• Storefronts: each extra store, language or currency multiplies the mapping.
• The team on your side: who signs off on data, content and testing.

For what the market typically charges, with sources, read what a rebuild costs.