Ecommerce Replatforming Without Losing What You Built

Ecommerce replatforming services move a live online store from one commerce platform to another. The work covers products, customers, past orders, content, apps, integrations such as your ERP, and every public URL. A good provider also plans the cutover so orders keep flowing, and redirects old addresses so search engines and customers land on the right new page. FactoryJet moves stores to Shopify and Shopify Plus.

Replatform when the current system blocks revenue or carries a deadline: a version leaving vendor support, a checkout you cannot change, or an ERP link that breaks every update. Stay if the pain is mainly design or speed, because a theme rebuild or performance work on the current platform costs less. We say which one applies on the scoping call, before any proposal.

We move stores from Magento and Adobe Commerce, WooCommerce, BigCommerce, NetSuite SuiteCommerce, Salesforce Commerce Cloud, WordPress, Squarespace and Wix, each with its own guide linked on this page. The destination is Shopify or Shopify Plus, either with a Shopify theme or as a headless build. We do not take on moves away from Shopify to other platforms.

Website replatforming moves pages and content from one CMS to another, for example WordPress to a new CMS. Ecommerce replatforming also moves the parts that take money: catalog, prices, customer accounts, order history, tax and shipping rules, payment providers and integrations. That extra data is why an ecommerce move needs a data mapping sheet and a cutover plan on top of a content export.

Pick Plus when you need higher limits or features that only Plus offers, such as checkout extensions, or when redirect volume is large: Shopify lists 20,000,000 URL redirects on Plus against 100,000 on other plans. Plus costs $2,300 a month on a three-year term or $2,500 on a one-year term in the US, per Shopify's help center. Many mid-size stores start on a standard plan.

B2B stores carry data that retail stores do not: company accounts with several buyers, customer-specific price lists, quantity rules, payment terms, and orders that must reach the ERP the same way they do today. Each of these has to be mapped field by field and tested with real buyer logins. We run a B2B order through the new store and into the ERP before cutover.

Yes. Shopify's B2B features let you set up business customers as companies and personalize pricing, currency, products, payment and shipping methods for each one, from the same store as your retail sales or a separate B2B store. Draft orders, Shopify Flow and ERP integrations are also listed in Shopify's B2B help. We map your current price groups into Shopify catalogs before import.

The ERP usually stays and the storefront changes, so the connection is rebuilt against Shopify's APIs. We have connected stores to Odoo, NetSuite, SAP Business One and ERPNext. Before launch we test the full loop: a web order lands in the ERP, stock levels flow back, and shipment tracking returns to the customer. Our ERP integration service covers this in more detail.

We crawl the old site and pull indexed URLs from Search Console, map each one to a single new URL, load 301 redirects before DNS moves, carry over titles, descriptions and structured data, and crawl the new store before launch. Google's site move guide recommends permanent redirects and warns against redirect chains. Some ranking movement in the first weeks is normal, and we watch Search Console daily.

A chain such as old page to interim page to final page makes crawlers follow extra steps, and Google's site move guidance advises against chains. Chains often appear when a store has been replatformed before and the old redirects are kept as they are. We flatten every chain so each old URL points straight to its final Shopify address with one 301.

Shopify's help center lists a limit of 100,000 URL redirects on standard plans and 20,000,000 on Plus. Shopify only follows a redirect when the old path is broken, and it does not let you redirect its fixed paths such as /products and /collections. Large catalogs with many filter and parameter URLs are the main reason a store needs the Plus limit.

Products, customers, historical orders, gift cards, store credit, blog posts and pages, per Shopify's data transfer guide. Shopify says to import products first, then customers, then historical orders, so orders link to the right products and buyers. Settings such as tax rules, shipping rates and payment providers are rebuilt by hand, because no platform exports them in a form Shopify can read.

No. Shopify's help center says you cannot migrate customer passwords from another store using a CSV, and the old platform stores them hashed. Customers move with their emails, addresses, tags and marketing consent, then get an invite to set a new password. On Shopify Plus, Multipass can sign customers in from an outside system, which some B2B stores use during a phased move.

Shopify allows three options and up to 2,048 variants per product. Stores coming from Magento, WooCommerce or BigCommerce often have four or more attributes on one product. We decide per product line: split into separate products, move an attribute into a metafield, or offer rare choices as line-item properties. The decision goes into the mapping sheet you approve before import.

For a small, simple catalog, often yes. Shopify's transfer guide lists its Store Migration app, CSV import, third-party apps, Shopify Partners and the API as routes. Apps struggle with custom attributes, B2B pricing, subscriptions, ERP links and full redirect maps. We often use an app for the bulk product copy and write scripts for the rest.

FactoryJet delivers a custom-theme store in 3 to 5 weeks, a migration with subscriptions, B2B or heavy data cleanup in 5 to 8 weeks, and a headless or custom build in 8 to 14 weeks. ERP work and the number of integrations decide where a project lands in those ranges. We confirm the plan in writing before work starts.

We plan every cutover so the old store keeps taking orders until DNS moves. Everything is built and tested on a private Shopify store first. Just before launch we sync the latest orders and customers, switch DNS in a quiet hour and watch orders live. A written rollback rule says when to switch back if checkout or order sync fails.

Yes. FactoryJet builds a working demo on your own product data before you sign, so you can click through real products, prices and variants on Shopify. It is the fastest way to find gaps such as a missing attribute or a B2B price rule that does not map. The demo also shows how we work before any contract.

Copy first if the current design converts and the move has a deadline, such as an end-of-support date. Redesign during the move if the old theme is part of the problem, because building the theme twice costs more than building it once. A middle path is to launch on a lightly adapted Shopify theme and redesign in a second phase.

Cost depends on catalog size, the number of integrations, B2B rules, redirects and whether you want a new design. FactoryJet quotes a fixed price in writing after a short scoping call, split by phase. For published market ranges by source platform, read our Shopify Plus migration cost guide, and try the replatforming cost calculator for a first rough scope.

Fixed price per phase. We scope the source platform, data and integrations up front, then agree a written price for each phase. Defects found during the cover period agreed before work starts are fixed inside that price. Changes you ask for later are quoted and approved one at a time, and ongoing support is optional with no monthly minimum.

You do. The Shopify theme code, any custom apps or scripts we write, the data mapping sheet, the redirect map and every export file belong to you. You can take the store to another agency or an in-house team at any time without asking us for access or permission.