Skip to content
Aerial view of a shipping port with cargo containers, cranes, and vessels representing the movement of ecommerce operations during replatforming
ShopifyOct 8, 202619 min

Ecommerce Replatforming: A Guide and Checklist

Ecommerce replatforming means moving your online store to a new platform. Your products, customers and past orders can be imported. The rest of the project is everything an import doesn’t bring over: the storefront design, any custom checkout work, saved credit cards, subscriptions, email automations, your products’ performance history in Google Merchant Center, shipping and tax settings, and your domain.

What Is Ecommerce Replatforming?

What is replatforming in ecommerce? It’s moving your online store from one platform to another while the store stays open. You sign up for the new platform, build a new storefront on it, import your old store’s data, and reconnect the tools that plug into the store, like email, payments and shipping. You’ll also see it called an ecommerce migration. The two terms mean the same thing.

Ecommerce Replatforming vs. an Upgrade, a Redesign and Going Headless

An upgrade, a redesign and a headless build each change one part of your store and keep you on the same platform. Replatforming changes the platform itself, so you have to decide what happens to every other part of the store.

Project What changes What stays the same
Upgrade The version of the platform you run, and its patches Your platform, your data and your integrations
Redesign or new theme The theme and page templates Your platform, your data and your checkout
Headless build The front end, which is replaced by a custom storefront The commerce back end and its checkout
Replatform The platform, the storefront, any custom checkout work and the connection to every integration Your business, your domain if you keep it, and the data you choose to import

An upgrade keeps you on the same platform with the same data and moves you to a newer version. Adobe recommends upgrading every patch release cycle (opens in new tab) and ties it to the card industry’s security standard, called PCI DSS and usually shortened to PCI: “To remain PCI-compliant, merchants must be on the latest patch or security patch.”

A redesign changes your theme and keeps you on the same platform. An older theme can limit what you get from the platform, though. On Shopify, some new features need an updated theme architecture (opens in new tab), and those won’t be applied to the theme you already have.

Headless means the front end of your site (the part shoppers see) and the back end (the part that runs products, orders and checkout) are independent. A headless build replaces only the front end. On Shopify, a custom storefront (opens in new tab) replaces the Online Store channel and connects to Shopify as the back end, and customers still check out using Shopify Checkout.

BigCommerce works as the back end for a headless storefront (opens in new tab) in the same way. So if your storefront is what’s holding you back and the back end isn’t, headless is the alternative to replatforming. It’s the build we cover under headless Shopify and Hydrogen development.

Deadlines That Push Stores Toward Ecommerce Replatforming

Every Adobe Commerce version has an end date for support. Each version gets three years of standard support (opens in new tab) from the date it becomes generally available. If your store runs on Adobe Commerce on Cloud, that deadline is enforced: starting June 1, 2027, Adobe stops maintaining Cloud environments that run unsupported Commerce versions. Adobe says it will suspend traffic to those environments, which takes the storefront offline.

The end dates differ by version. We list them in our guide to Adobe Commerce support dates by version.

WooCommerce and self-hosted Adobe Commerce both run on PHP, the programming language underneath them, and PHP has a support schedule of its own. Security support for PHP (opens in new tab) ends on December 31, 2026 for version 8.2 and on December 31, 2027 for version 8.3. WooCommerce asks for PHP 8.3 or greater (opens in new tab) and is tested up to PHP 8.4. It still works on some older PHP and database versions, but those have reached their official end of life and may expose your site to security vulnerabilities.

Adobe’s support doesn’t cover that underlying software. Adobe doesn’t provide security and quality fixes for third-party software an Adobe Commerce store depends on, such as PHP and MySQL, when that software reaches end of life during the store’s three-year or extended support period.

A PHP deadline is a reason to upgrade first. It turns into a reason to replatform when the upgrade, the extensions that have to be rewritten because of it, and the hosting behind it cost more than you can justify spending on the store.

Shopify Retires Features on a Date Too

When you move to a hosted platform like Shopify, the vendor takes over security patches and server software upgrades. The vendor also decides when its own features get retired.

Shopify deprecated Scripts on June 30, 2026 (opens in new tab). Any Scripts still published on a store were deactivated and no longer work. Shopify Functions is the replacement.

Custom checkout code went the same way. The checkout.liquid layout (opens in new tab), which renders the checkout, is available only to Shopify Plus merchants, and it’s no longer supported for the Information, Shipping and Payment steps of checkout.

On the Thank you and Order status pages, checkout.liquid and additional scripts were retired for Plus stores on August 28, 2025. Script tags on those two pages were retired on August 28, 2025 for Plus stores and on August 26, 2026 for all other stores.

When an Upgrade Beats Ecommerce Replatforming

You can meet each of these deadlines without leaving your platform. On Adobe Commerce, that’s the upgrade Adobe recommends every patch release cycle. Or it’s Adobe’s own hosted version, Adobe Commerce as a Cloud Service (opens in new tab), where Adobe runs the software for you. So you can move to a hosted platform and stay with Adobe.

On WooCommerce, it’s upgrading PHP and your database to the versions WooCommerce requires. On Shopify, it’s rebuilding a retired Script as a Function. The Shopify Scripts customizations report (opens in new tab) in your admin lists the customizations that were active.

We’d replatform when the platform itself is the problem: what it costs to run, how much upgrade work it demands, or something it can’t do and won’t be able to do with a new theme, an app or a version upgrade. If a theme, an app or an upgrade fixes the problem, that’s the smaller project. Get a price for it first.

What Moves in an Ecommerce Replatforming Project, and in What Order

A store moving to Shopify typically brings over products, customers and historical orders (opens in new tab), meaning orders that have already been fulfilled. Gift cards, certificates and store credits come too, along with blogs and pages like your shipping policy, contact page or about page. Import products first, then customers, then historical orders. That order lets each imported order connect to the right product and the right customer.

After the import, the remaining steps cover checking your products, your theme, shipping, taxes, your payment provider, test orders, staff, your domain, point of sale (POS) and optional SEO setup. Shipping and taxes are things you set up on the new store.

There are four ways to move the data (opens in new tab): a CSV import (a spreadsheet file you upload), a third-party migration app, a migration service, or a custom integration built through the API. CSV works best for simpler product catalogs and smaller customer lists. It handles products and customers. Historical orders, gift cards, blogs and pages go through migration apps or the APIs.

What you’re moving How it gets to the new store What to know
Products CSV import, migration app, migration service or API Import these first
Customers CSV import, migration app, migration service or API Import these second; passwords don’t come over by CSV
Historical orders Migration app or API Import these third, after products and customers
Gift cards and store credit Entered by hand, the Gift Card API or a migration app Import these right before launch
Blogs and pages Migration app or API Clear out old content before importing
Discounts Migration app Clear out old ones before importing
Shipping and taxes Set up on the new store Test with orders to different addresses
Saved card numbers Transferred from one payment processor to another Plan requirements and a paid service apply
Subscription contracts Recreated through your subscription app After the payment methods have moved
Email flows and segments Cloned and given a new trigger in your email platform After your past order data is in the new store

Product details that aren’t part of Shopify’s default product listing go into metafields, which are custom fields you add to a product.

You don’t have to bring everything. A migration can be a good time to clear out old content that isn’t performing.

Importing orders also sends email. Every staff member set up to get new order notifications, the account owner included, gets a new order email for each imported order. Turn off new order notifications before the import and turn them back on when it’s done.

Passwords, Gift Cards and Order History

Do customer passwords transfer in an ecommerce platform migration? Not if you’re moving to Shopify with a CSV file. Passwords are encrypted outside of Shopify (opens in new tab), so a CSV can’t carry them over from another online store.

The rest of the customer record does come over, including contact details, addresses and marketing preferences. Your customers may not need a password on the new store either. Once you turn on sign-in links (opens in new tab) for Shopify’s customer accounts, a customer enters their email address and gets a one-time 6-digit verification code to sign in.

If your gift cards can still be used on the old store, move them last, right before the Shopify store launches. If a customer spends a card on the old store after you’ve imported it, Shopify will be holding the wrong balance, and an imported gift card can’t be deleted and loaded again.

You can’t reuse a gift card number either, even after the original card with that number has been deactivated. That means you can’t fix a bad import by deleting the cards and entering the same numbers again. Check the gift card file before you load it.

For order history, bring over at least every historical order that’s still within your return policy window. Shopify recommends importing orders from the past 2-5 years. Neither one is a limit. Pick your cutoff based on how far back your support, returns and reporting need to look.

Moving Saved Cards and Subscriptions When You Replatform

Can saved credit cards be migrated to a new ecommerce platform? The card numbers can move, and they go straight from your old payment processor to the new one. Stripe’s position is that its customers own the sensitive data (opens in new tab) they give to Stripe. It’ll only send the cards to a processor that meets the same security standard: “To meet PCI compliance obligations, we can only transfer your card data to another PCI DSS Level 1-compliant payment processor.”

Braintree asks for proof first. Before it sends card data to another processor, it needs a formal statement that the processor is PCI compliant (opens in new tab), called an attestation, from a qualified provider. It also limits you to two exports: one for the bulk of your customers, and one for any new customers created while your processing was being switched over.

When card data is imported into Braintree, the old processor encrypts the file (opens in new tab) and uploads it to Braintree’s secure server. Braintree sends back a log of the customer IDs and payment method tokens it created. A token is the reference a system stores in place of the card number, so if the tokens changed, every system that holds the old ones needs the new ones.

Card changes made during the transfer can get lost. On an import into Stripe, any changes customers make to their payment information (opens in new tab) with your previous processor between the data transfer and the finished import are lost.

Shopify has its own rules for bringing card numbers in. Migrating the card numbers themselves requires the Shopify Plus or Enterprise plan (opens in new tab) and goes through Shopify Professional Services, which is a paid service. If you need saved card numbers to come over, bring it up when you scope the project with your Shopify Plus agency. Payment tokens have fewer requirements: you can migrate them on any Shopify plan, with support from your subscription app’s developer.

The card number service only moves credit card numbers. It doesn’t support accelerated wallets such as Venmo, Apple Pay and Google Pay, or bank account information. PayPal billing agreements can’t be migrated through it either.

If you’re on Shopify’s Enterprise plan, you can also save customers’ cards for one-time purchases, not only for subscriptions. Moving payment methods can get complicated because the data is sensitive and encrypted, and you might run into limits with unsupported payment gateways and local payment methods. A payment gateway is Shopify’s term for the service that processes your card payments, such as Stripe or Authorize.net.

Your other option is to leave the cards where they are. Shopify calls this the slow drip method. A secondary gateway keeps billing your existing subscriptions through the old processor, and each card moves over when its customer updates their billing details.

Shopify’s own estimate is that it can take months or even years to move every payment method this way, depending on when customers choose to update their billing details. On plans other than Plus and Enterprise, keep the secondary gateway active until the last payment method has moved.

Subscriptions Have to Be Recreated on the New Store

A subscription is a saved payment method plus a subscription contract. The payment method can be moved. The contract has to be created again on the new platform.

Once the payment methods are in Shopify, your existing subscription contracts get recreated through Shopify’s APIs. That step belongs to you or your subscription app vendor. So does importing or creating the customer records.

To sell subscription products, you need Shopify Payments as your primary payment provider (opens in new tab). To migrate existing subscriptions, you need Shopify Payments, Authorize.net or Stripe as your primary payment gateway (opens in new tab), and the migration process is designed by third-party apps, not by Shopify. If your subscriptions are billed through Stripe, Braintree, PayPal Express or Authorize.net, the contracts can be imported into Shopify without moving the card numbers (opens in new tab). This covers pay-as-you-go subscriptions.

What comes over in that import depends on the gateway. From Stripe, it’s credit card payment methods only. From Braintree, it’s only credit cards and Apple Pay. If you sell in more than one currency, know that Braintree’s older gateway connection doesn’t support multi-currency subscriptions.

If your new setup has you importing saved cards into Stripe, flag them correctly as cards on file, because card issuers that can’t confirm the cardholder agreed to recurring payments might decline them.

The Tools Connected to Your Store Have to Be Reconnected

Many ERPs and other third-party systems already have a connector app for Shopify. Search the Shopify App Store for one before you build a custom integration. Install the apps you need early in the store setup, so you have plenty of time to test them before launch.

Klaviyo Flows After You Switch Platforms

You can switch ecommerce platforms and keep the same Klaviyo account (opens in new tab). Move all of your past purchase data from the old platform to the new one first, and only then connect the new platform to Klaviyo. The whole switch is nine steps. It starts with migrating historical data and integrating the new platform, moves through onsite tracking, sign-up forms, flows, the welcome series and segments, and ends with turning off the old integration.

Some of your flows, which are Klaviyo’s automated message series, won’t keep working by themselves. Many flows are triggered by a metric, which is an event your store sends to Klaviyo, and each metric belongs to one platform’s integration. After the switch, no more data comes into Klaviyo from the old platform, so those flows stop picking up new contacts.

You can’t change a flow’s trigger directly. Clone the flow and choose the new platform’s metric as the trigger.

The emails and segments need the same work. The template tags in an abandoned cart flow, which are the placeholders that pull in details like cart contents, are different from one platform to the next. Any segment with metric-based conditions has to be recreated using the new metric.

Set your cloned flows to Draft or Manual so they don’t start sending during the migration. Be careful with the old metrics, too: deleting one also deletes all the historical data tied to it in your account. We include flow rebuilds in the Klaviyo email marketing work we scope into a migration.

Google Merchant Center Product IDs and Tracking

If you send a product feed to Google Merchant Center, Google wants a stable ID for each product (opens in new tab). Once a product has an ID, don’t change it. Merchant Center and Google Ads use that ID to track the product’s performance history, and changing it overwrites the product and its history.

So if your new store’s feed sends different IDs for the same products, that history gets overwritten. Before you import the catalog, decide which ID the new feed will send, and make it match what Merchant Center already has.

Your tracking gets rebuilt too. On Shopify, pixels are added as app pixels or custom pixels (opens in new tab) in the Customer events section of the admin. That’s where you recreate the tags that lived in your old platform’s templates.

What Ecommerce Replatforming Costs

Some replatforming costs are published prices you can look up. Others only come in a quote.

Cost How it’s priced Where it applies
Platform subscription, lower plans Published prices Shopify Basic, Grow and Advanced; BigCommerce Core, Growth and Scale
Platform subscription, top plan Published starting price, then custom or variable pricing Shopify Plus; BigCommerce Performance
Enterprise suite license By quote only Salesforce Commerce Cloud
Open-source software Free to use; hosting, extensions and payment processing are priced separately WooCommerce
Card rates and third-party transaction fees Published types of fees, which vary by plan Shopify
Moving card numbers Paid service Shopify Professional Services
Apps, themes and migration tools Priced by each vendor Any platform
Build, integrations, redirect mapping, QA and training By quote only Your agency or your own team

Shopify publishes prices for Basic, Grow and Advanced (opens in new tab), each with a monthly rate and a yearly rate. Shopify Plus (opens in new tab) has a starting price that depends on the length of your contract. Larger, more complex businesses pay a variable platform fee instead, based on their revenue and business model.

BigCommerce lists Core, Growth and Scale (opens in new tab). Core and Growth each have a sales cap measured over the last twelve months. Go over it and you’re moved up to the next plan automatically. Scale charges a percentage on sales above a monthly cap, and Performance shows custom pricing above a published starting price.

Salesforce shows “Contact for pricing” on every Commerce edition (opens in new tab). WooCommerce is free to download and use (opens in new tab), and you pay separately for hosting, extensions and payment processing.

On Shopify Plus and on BigCommerce, what you pay for the platform can change with your sales. Work out the platform fee at the sales volume you’re planning for, not only the volume you have today.

On Basic, Grow and Advanced, Shopify’s rates and fees (opens in new tab) include the monthly price, credit card rates and third-party transaction fees. That last one applies when you use an outside payment provider. Then two parties charge you: Shopify charges third-party transaction fees that vary by plan, and your payment provider separately charges its own credit card rates.

Credit card transaction fees aren’t returned to you when you issue a refund. No Shopify plan has a setup fee.

One Shopify fee depends on when the store was created. On Shopify stores created on or after May 12, 2025, orders that include store credit or gift cards as a payment method are charged third-party transaction fees on the amount paid with store credit or gift cards. Stores created before May 12, 2025 don’t pay those fees. Check the creation date of the store you’ll launch on.

Everything else is quoted per project or priced by each vendor: apps and extensions, a paid theme, data migration tools or services, the build and integration work, redirect mapping, QA and training. Your old platform also keeps billing you until you switch over, so a longer project means more time paying for two platforms.

Does Ecommerce Replatforming Take Care of PCI Compliance?

Does moving to a hosted platform make a store PCI compliant? Shopify’s claim about its own PCI compliance (opens in new tab) is “Shopify is certified Level 1 PCI DSS compliant. This compliance extends by default to all stores powered by Shopify.”

The PCI Security Standards Council, the body behind the standard, published e-commerce guidance (opens in new tab) in April 2017, written against PCI DSS v3.2. It says of hosted shopping carts that “The use of such a solution can alleviate many but not all of the merchant’s PCI DSS responsibilities.” The council also says “it is the responsibility of the merchant to vet the service provider and monitor its compliance to PCI DSS.”

Going by the council, moving to a hosted platform reduces the PCI work you carry but doesn’t remove it. Ask each platform on your shortlist to put in writing who’s responsible for what, and give that to whoever signs your PCI self-assessment.

Protecting Your SEO During Ecommerce Replatforming

Replatforming changes your URLs and page templates, and Google treats that as a site move. The list of URLs to plan for is longer than your pages. Google wants the URLs of embedded content (opens in new tab) in the plan too: videos, images, JavaScript and CSS files.

You’ll also need to update links that live outside your site. That includes profile links on Facebook, Twitter and LinkedIn, and your ad campaigns, which need to point to the new landing pages.

Our SEO migration checklist covers the redirect map, the staging rules and the launch sequence. We do redirect mapping and SEO migration as part of the build.

Launching the New Store: The Last Steps of Ecommerce Replatforming

Your first data import happens before launch, and your old store keeps taking orders after it. So you need a second, smaller import to catch up. That’s called a delta migration: the transfer of any new data added to your old store after the cutoff point you chose for the first import.

There’s no right or wrong amount of time between the cutoff and launch, but a shorter gap makes the delta migration easier. More than orders builds up in that gap. Along with new orders and customers, any products or content you added to the old store might need to be added to the new one, with 301 redirects, which permanently send an old URL to a new one.

If you stop making catalog and content changes on the old store during that gap, there’s less to catch up on.

How long does the DNS switch take in an ecommerce migration? DNS is the system that points your domain name at your store. After you point the domain at Shopify, the DNS change (opens in new tab) usually takes effect within two hours, but it can take up to two days. To speed that up, ask your domain host to lower the TTL to 300 about a week before you go live. TTL is the setting that controls how long the rest of the internet keeps using your old address before checking for a new one.

While the change spreads, both stores can get visitors, so some customers might land on the old store and others on the new one. Consider turning off checkout on the old store during that time. That also stops new orders and gift card redemptions from landing on the old store after your final delta migration.

Before launch, place test orders. Try discount codes, different payment methods, different shipping addresses (pay close attention to how the tax is calculated) and failed transactions. After that, test the notification emails, the fulfillment flow and a refund.

At launch, turn off test mode in Shopify Payments first. Then switch the primary domain, point your DNS records to Shopify, submit your sitemap to Google and turn off private mode.

Your fallback is the old store. Keep it intact until you’ve confirmed the delta migration caught everything and the new store has processed real orders. A low TTL is what lets you point the domain back quickly if you need to. Shopify doesn’t back up your store data by default, so export the imported data once you’ve checked it.

Ecommerce Replatforming Checklist

Work through this ecommerce replatforming checklist in order. First, decide whether to replatform at all.

  • Write down what's forcing the decision, and the exact product, version and plan it applies to
  • Get prices for the upgrade, your vendor's own cloud offering and a headless front end before you get a price for replatforming
  • List what your current platform still couldn't do after an upgrade

Then take stock of the store before anything gets built.

  • Export every URL, including images, scripts and other embedded files
  • List every app, integration and tracking tag, who owns it and what data it holds
  • Ask each app vendor that holds customer-facing data, such as reviews, loyalty balances and subscriptions, to put in writing how that data gets exported and imported
  • Write down every customization in the cart, the checkout and your pricing rules
  • Note your payment processor, the saved cards on file and every active subscription
  • Note the product ID your Merchant Center feed sends today

Build the store and move the data.

  • Build the storefront and install apps early enough to test them
  • Import products, then customers, then historical orders
  • Put product details that don't fit Shopify's standard fields into metafields
  • Set up shipping and taxes on the new store
  • Turn off staff order notifications before importing orders, then turn them back on

Move payments and reconnect your tools.

  • Request the card data transfer between processors and confirm the receiving processor's PCI attestation
  • Confirm the plan you need to import card numbers, or plan the token route with your subscription app's developer
  • Recreate subscription contracts once the payment methods have moved
  • Connect the new platform to Klaviyo after your past order data is in, clone flows as drafts, and rebuild metric-based segments and template tags
  • Recreate tracking as pixels and set the feed's product ID to match Merchant Center
  • Connect your ERP or fulfillment system and run a test order all the way through to a refund

Switch over to the new store.

  • Lower the DNS TTL ahead of launch
  • Stop making catalog and content changes on the old store
  • Run the delta migration, then import gift cards last
  • Place test orders with different payment methods, shipping addresses and discount codes, plus a failed transaction
  • Turn off checkout on the old store, switch the domain and submit the sitemap

Finish up after launch.

  • Test your redirects, fix any not-found errors and resubmit the sitemap
  • Update your profile links and ad destinations
  • Turn off the old platform's integration in Klaviyo
  • Keep the old store intact until you've confirmed the delta migration caught everything

Who Does the Work in an Ecommerce Replatforming Project

BLKDG is a Shopify agency, and every migration we run includes building the Shopify store. That keeps the data move, the storefront and the integrations in one plan, under our Shopify migration services. If you’re leaving a specific platform, we’ve written separate guides to a WooCommerce to Shopify migration and a Wix to Shopify migration.

If you’re weighing ecommerce replatforming against an upgrade, schedule a free Growth Audit. It’s a no-obligation look at why your store isn’t getting seen or converting, with a roadmap for how to fix it.

About the author

BLKDG Team

Not sure where the gap is? That's exactly what the Digital Marketing Growth Audit is for.

A free, no-obligation look at where your site can win more traffic and conversions, with a clear digital marketing roadmap to get there. Just a straight read on where your digital presence stands and where it's headed.