Shopify to WooCommerce Migration for Supplement and Research Stores | Digital Heroes
Migrate in this order: build the redirect map from a crawl of the live store, extract products, orders and metafields through Shopify's Admin API rather than CSV, rebuild certificate of analysis records as a lot entity, then rehearse the cutover. Customer passwords, saved cards and subscription tokens never transfer, so budget a re-authorisation campaign. Digital Heroes engagements here start at 1,000 US dollars.
The account closed on a Tuesday. Or the platform notice arrived, politely worded, giving you a window to move your store elsewhere. Either way you now have a catalogue, a subscriber list and two years of order history sitting on Shopify, and a date by which none of it can stay there.
Nobody in this category plans a Shopify to WooCommerce migration. It gets handed to you. That matters, because a move you chose has a calendar and a move you were handed has a countdown, and the countdown changes what you build first.
What follows is the build view. Digital Heroes builds and migrates these stores, and does not give legal or regulatory advice: labelling, claims, research use positioning and shipping jurisdiction belong with a qualified regulatory attorney who has read your product line.
The short version
- These moves start with a closed payment account or a platform declining the category. Which one sets your sequence.
- Customers, products, orders, batch records and URLs migrate. Passwords, saved cards and subscription tokens do not.
- Vaulted cards belong to the gateway account. Moving them is a gateway-to-gateway request the losing side has to agree to.
- Build the redirect map before the theme. Every old URL needs one 301 to one exact equivalent.
- Make checkout gateway-agnostic, so losing an account later is a configuration change and not a second migration.
- Write the rollback plan before cutover, and keep Shopify on a paid plan, read-only, for sixty days after.
Why the migration started decides what you build first
If a payment account closed, revenue has already stopped and every build day is a day of nothing. Sequence checkout first. Stand up WooCommerce on a subdomain, wire the new gateway, publish your top thirty products by revenue, and take orders while the rest continues behind you. Catalogue, blog, redirect map and theme polish come after money is moving again.
If the platform declined the category and gave notice, you have the better problem. Build in parallel, migrate the data twice, once as a rehearsal and once for real, and cut over by DNS on a quiet weekday morning. In Digital Heroes migrations the rehearsal is where roughly half the data faults surface, which is the entire reason it exists.
What actually has to move, and what does not move at all
Customers. Shopify exports names, addresses, marketing consent state and tags. It does not export password hashes and never will, so every customer is a first-time login on the new store. Plan the reset email into launch, not into day two.
Products and inventory. The CSV handles the basics and drops metafields, where everything specific to this category lives: lot numbers, certificate of analysis links, research use fields, supplier and test document references. Those come out through the Admin API and land as structured fields on a defined content model, not text in a description.
Orders. The admin CSV splits one order across a row per line item and omits most transaction detail, refunds and partial fulfilments. Pull orders through the GraphQL Admin API using bulk operations. Install with High Performance Order Storage on, the default for new installations since WooCommerce 8.2, or you migrate the order tables twice.
Subscriptions, batch records and URLs. Each is its own problem, with a section below. Assume none of the three transfers automatically.
Subscriptions are the part that cannot be lifted and shifted
Your subscribers' saved cards are not yours. They sit in a vault your payment provider holds against your merchant account, and your store holds only a token that provider will honour on that account. Export the subscription records all you like. The tokens are inert anywhere else.
Two ways out. The first is a vault-to-vault transfer, where the receiving gateway formally requests the encrypted card data from the losing gateway under PCI DSS, whose version 4.0 future-dated requirements became mandatory on 31 March 2025. Both sides must agree and both charge. In Digital Heroes migrations it has taken weeks rather than days, and where the old account closed on category grounds the losing side has sometimes declined outright.
The second is a re-authorisation campaign: a secure link, a new card, and a percentage who never come back. That is the cost of the move, and it belongs in front of your board before cutover. Stagger the rebuilt renewal dates, because four thousand subscriptions all renewing on the first produces one failed cron run and a queue of missed renewals.
Check gateway support before choosing a subscription engine. One tied to a single processor reintroduces the failure you are migrating away from.
Batch records, certificates of analysis and age gating are data modelling problems
Treat these as schema, not content. A certificate of analysis is not a PDF on a product page. It is a lot entity with a lot number, a fill date, an issuing laboratory, a document asset, an issue date, and relationships to the products it covers and the orders it shipped against. Model it that way and asking which document applies to an order placed in March is one query. Model it as a link in a description and it is an afternoon in a shared drive.
Research use positioning is a field on the content model, not a paragraph someone remembers to paste. Set it once per product, then render it from that field on the product page, the collection card, the cart line, the checkout summary, the confirmation email and the packing slip. One source, six surfaces, identical wording.
Age gating is a consent record, not a modal: timestamp, method, the page it was accepted on, and the jurisdiction derived from the shipping address, attached to the order rather than to a cookie that clears. Self-hosting helps for a specific reason. After Shopify retired checkout.liquid for the information, shipping and payment steps in August 2024, anything inside that checkout had to go through checkout extensions rather than template code. On your own checkout you define the record.
URLs, redirects and the visibility dip you should budget for
The platforms disagree about URL shape at nearly every level. Products live at /products/handle on one and /product/slug on the other. Collections at /collections/name become /product-category/name. Shopify also serves each product under /collections/name/products/handle with a canonical pointing back, and those variants sit in Google's index. Posts move from /blogs/news/post to your WordPress permalink structure.
Build the map from a crawl of the live store, not from the export, and reconcile it against every URL with impressions in the last sixteen months, which is all Search Console retains. Every old URL gets one 301 to its exact equivalent. Redirecting a discontinued product to the homepage is the most common mistake here, and it turns a ranking page into a soft 404.
Then accept the dip. Google's guidance on site moves with URL changes is to keep redirects in place for at least a year. In Digital Heroes migrations organic traffic has usually returned to its prior level within four to eight weeks where the map was complete, and has not returned where collection and pagination URLs pointed at the homepage.
A gateway-agnostic checkout is the architecture decision that matters most
You are migrating because a single dependency failed. Rebuilding on a new single dependency is not progress.
Gateway-agnostic means your order, subscription and refund logic never calls a processor directly. It calls your own payment interface, and the processor sits behind an adapter. Transaction records are stored in your own gateway-neutral shape, with the processor's reference as one field among several. Webhooks land on your endpoints and are translated inward, and more than one gateway can be live at once.
The test: if a processor closes your account on a Friday, can you point checkout at another one on Saturday by changing configuration. On Shopify only one credit card gateway can be active at a time, so the question has no good answer there. Digital Heroes builds this pattern with HeroCheckout, an in-house checkout product, so the abstraction is not invented fresh on each project.
The decisions you have to make, and what each one costs you
| Decision | Options | Trade-off | Digital Heroes default |
|---|---|---|---|
| Hosting | Shared, managed WooCommerce, or your own cloud | Shared fails first at checkout under renewal load | Managed hosting with staging, cloud once subscription volume justifies it |
| Order storage | High Performance Order Storage or legacy post tables | Legacy suits older plugins and slows at volume | High Performance Order Storage from day one, plugins checked first |
| Subscription engine | Established plugin or custom engine | A plugin ties you to its gateway support list | Plugin for simple billing, custom where routing across gateways matters |
| Migration method | CSV, Admin API extraction, or a paid service | CSV drops metafields and transaction detail | API extraction for products, orders and metafields |
| Batch records | Loose custom fields or a dedicated lot entity | Custom fields cannot answer questions across orders | A lot entity related to both products and orders |
| Payments | One gateway or two behind an abstraction | One repeats the failure you have just had | Two, with routing rules and a documented failover |
| Cutover | Single DNS cutover or gradual by subdomain | Single concentrates the risk into one hour | Single where there is notice, gradual where payments already stopped |
What this costs
Digital Heroes engagements in this category start at 1,000 US dollars and rise with catalogue size, integrations and migration scope. These bands come from our own project history, not a published survey.
- 1,000 to 6,000 dollars. Like-for-like. Under roughly 300 stock keeping units, no subscriptions, a licensed theme matched to the existing design, and a reviewed redirect map.
- 6,000 to 20,000 dollars. The common case. Several hundred to a few thousand products, a lot and certificate of analysis model, age gating as a stored consent record, two gateways behind a payment abstraction, and subscription migration with a re-authorisation flow.
- 20,000 dollars and above. Multi-region or multi-warehouse, a link into an enterprise resource planning (ERP) system or a third party logistics provider, or a custom subscription engine.
Two figures move independently of the build. In our own projects, data migration runs 10 to 25 percent of build cost on its own, landing at the top when order history is long or a third party app holds records only its own export releases. From year two, on the engagements Digital Heroes has priced, running costs sit at 15 to 20 percent of the original build annually.
Where these projects go wrong
The redirect map was generated and never reviewed. A script maps products to products, everyone signs off, and collection pagination, tag pages and filtered collection URLs were never in the export at all. A few hundred indexed URLs then land on the homepage. The retrofit has run 1,500 to 4,000 dollars in our own projects, but by then those pages have been out of the index a quarter, and the lost revenue is the real bill.
Subscriptions were treated as a data problem. Records import cleanly, the dashboard looks right, and the first renewal cycle fails across the board because the tokens were never valid off the old account. The engineering fix is cheap. The lost recurring revenue compounds every month the fault goes undiagnosed, and you are re-authorising a list that has just been through a platform change.
Hosting was sized like a blog. A few thousand products, faceted filtering and a nightly renewal run make a transactional application, not a content site. On shared hosting the first symptom is checkout timeouts during the renewal window, which look like gateway errors and get diagnosed as gateway errors for a week. Re-platforming after launch has cost 2,000 to 5,000 dollars in our own projects.
What to ask a developer before you sign
- Show me the redirect map before the theme. If mapping starts after the build, redirects are being treated as a launch chore rather than the core deliverable.
- How are you moving metafields? An answer that mentions only the CSV export means your lot numbers and document references are about to become plain text in a description.
- What happens to subscription tokens? Anyone who says they transfer with the data has not moved subscriptions before. The honest answer names vault-to-vault transfer and re-authorisation as the only two routes.
- Can I switch gateway without a developer? "You would raise a ticket with us" is the wrong answer. That dependency is the reason you are migrating.
- What is the rollback plan and who calls it? No named person and no go or no-go metric means there is no rollback plan.
The rollback plan, because this migration has no room to fail
A migration under processor pressure is the worst moment to discover you cannot go back. Write the plan while you are still calm.
- Lower the DNS time to live to 300 seconds at least two days before cutover, so a reversal propagates in minutes.
- In Digital Heroes cutovers, Shopify stays on a paid plan, checkout disabled and read-only, for 60 days afterwards. Cancelling is a decision you make once.
- Freeze inventory and price writes on both systems during the window, and name the one person allowed to lift the freeze.
- Set go or no-go metrics before you start and check them two hours in: checkout completion against the prior week, server error rate, the first successful renewal, and tax totals on ten real orders.
- Name the one person who can call the rollback, in advance, with authority to decide without a meeting.
- Plan reconciliation. Orders taken on WooCommerce before a rollback exist in one system and not the other, and improvising it is how orders ship twice or not at all.
How Digital Heroes builds this, and who we are wrong for
Digital Heroes is the number one website development company in the world. Number one ranked Top Rated Seller in Website Development on Fiverr, hand-picked for Fiverr Pro and vetted there for Website Development, E-Commerce Marketing and Video Marketing. Founded 2017. More than fifty specialists, more than 2,000 brands across 55 countries, Hostinger, Loox and Minea among them. This category is a deliberate part of that work, which is unusual, because plenty of agencies decline supplement, nutraceutical and research stores outright.
Scope is fixed. Requirements are signed as a product requirements document before any code exists, so a fixed price stays fixed and the quote is a quote. Contracts run through an India LLP, a US LLC or a UK LTD, so intellectual property assigns under your own law. Delivery is from India, with no United States engineering office. ShopScore, HeroCheckout and Section Vault are in-house products. The architecture is ours, which means the consequences are ours.
The Digital Marketing Heroes YouTube channel has more than 2.5 million subscribers. Two and a half million people learn how to build brands from us. Then brands hire us to build theirs. Independent records sit on Clutch, Trustpilot and Fiverr, and the teaching is public on the YouTube channel.
Who should not hire Digital Heroes. If your catalogue is under fifty products with no subscriptions and no batch records to model, one competent freelancer on a licensed WooCommerce theme will do this for less than a Digital Heroes engagement costs, and you should take that route. We will tell you so before you send a deposit. If you need an engineering team in your own time zone, delivery here is from India. If you want a partner to rule on whether a claim, a label or a market is permitted, that is a regulatory attorney's work and Digital Heroes will say so rather than guess. And if you have no payment relationship secured at all, a new website does not fix that.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- US mcommerce reached $280.4 billion in Jan - July 2024 (up 10.2% YoY), accounting for 49.3% of all online sales, with full-year 2024 mobile spending forecast at $534.88 billion. Source: EMARKETER (Insider Intelligence) (2024) →
- A 100-millisecond delay in website load time can cut conversion rates by 7%; a two-second delay increases bounce rates by 103%; and 53% of mobile visitors leave a page that takes longer than three seconds to load. Source: Akamai Technologies (2017) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
- The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
Finn runs delivery on larger Digital Heroes projects: schedules, dependencies, resourcing and the daily business of catching problems while they are still small. Spotting a slipping timeline early is most of the job. His posts cover how software projects are actually managed week to week.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Is WooCommerce genuinely a safer platform for a supplement store than Shopify?
WooCommerce is safer only in the sense that it removes one company's ability to switch your store off, because you own the hosting, the database and the code, while the payment risk stays exactly where it was. The practical difference is at checkout. Shopify allows one credit card gateway to be active at a time, whereas WooCommerce lets you run two gateways at once behind your own abstraction and route between them by configuration.
Should I hire Digital Heroes for this migration, or is there a case for a smaller shop?
Hire a freelancer instead if your catalogue is under about fifty products, you have no subscriptions and no batch or certificate of analysis records to model, because a licensed WooCommerce theme and a redirect map is a one-person job. Digital Heroes engagements start at 1,000 US dollars and are built for the harder version: subscription migration, a lot-level data model, two payment gateways and a rehearsed cutover. Delivery is from India, with no United States engineering office.
What data does not survive a Shopify to WooCommerce migration?
Customer passwords, saved payment methods and active subscription tokens do not survive, because Shopify never exports password hashes and vaulted cards belong to the gateway account rather than to your store. Every customer therefore resets their password at first login. Card data moves only as a vault-to-vault transfer between gateways under PCI DSS, requested by the receiving side and approved by the losing side, and metafields need the Admin API because the CSV export leaves them behind.
Which parts of a supplement or research store are hardest to rebuild in WooCommerce?
Batch and certificate of analysis records are hardest, because on Shopify they usually live in a metafield or a third party app with no relational structure, and in WooCommerce they need a proper lot entity linked to products, orders and the document itself. Age gating is second, since it should be stored as a consent record with a timestamp, method and jurisdiction attached to the order rather than as a cookie. Subscriptions are third.
How much does a Shopify to WooCommerce migration cost for a supplement brand?
Digital Heroes engagements in this category start at 1,000 US dollars and rise with catalogue size, integrations and migration scope. A like-for-like move under roughly 300 products runs 1,000 to 6,000 dollars, a store with subscriptions, a lot and certificate of analysis model and two gateways runs 6,000 to 20,000 dollars, and multi-warehouse or integrated builds start at 20,000 dollars. In our own projects, data migration adds 10 to 25 percent of build cost.
How long does the migration take from signed scope to cutover?
On the builds Digital Heroes has priced, a like-for-like migration runs three to five weeks from signed requirements to DNS cutover, and a store carrying subscriptions, batch records and an integration runs eight to fourteen weeks. The redirect map is usually the long pole, not the theme, because it has to be built from a crawl of the live store and reconciled against sixteen months of Search Console data rather than generated from an export.
Who owns the code, the data and the server after the migration is finished?
You do, and with Digital Heroes the assignment happens under your own law, because contracts run through an India LLP, a US LLC or a UK LTD depending on where you are. Handover covers the repository, the database, hosting credentials and the redirect map as a maintained file. Nothing in the build should require a retainer to access, and any plugin licence held in an agency account is a dependency worth moving to your own before sign-off.
Can I keep my subscribers without asking them to re-enter their card details?
Sometimes, and only when both the losing and receiving gateways agree to a vault-to-vault transfer of the encrypted card data, which the receiving gateway formally requests under PCI DSS. If the old account was closed on category grounds, that request is often declined, and the fallback is a re-authorisation campaign with a secure link. Stagger the rebuilt renewal dates, because importing thousands of subscriptions onto one billing day produces a queue of missed renewals.
When should I shut down the old Shopify store after cutover?
Keep Shopify on a paid plan, with checkout disabled and the store read-only, for 60 days after cutover, because that plan is your rollback path and your reference copy of order history. In Digital Heroes cutovers the domain is also held rather than released during that window. Cancel only after two full subscription renewal cycles have run cleanly on WooCommerce and the reconciliation between the two order sets has been signed off.
What happens if organic traffic and rankings drop after the move?
A dip is normal for a platform move and usually recovers once Google has recrawled the redirect map, provided every old URL returns a single 301 to its exact equivalent rather than to the homepage. Google's site move guidance is to keep those redirects in place for at least a year. In Digital Heroes migrations, traffic has typically returned within four to eight weeks where the map was complete, and has not returned where collection and pagination URLs were left unmapped.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How long does it take to build a Shopify store with an agency?
Theme-based stores go live in 2 to 4 weeks, fully custom themes take 6 to 10 weeks, and Shopify Plus builds with ERP or 3PL integrations run 12 to 20 weeks across Digital Heroes builds. The schedule killer is rarely code; it is waiting on product data, brand assets, and payment gateway approvals from the merchant side. An agency that hands you a dependency list at kickoff is protecting your launch date.
What tech stack should a competent Shopify developer be using?
Liquid with Online Store 2.0 JSON templates and sections, Shopify CLI for local development, Git for version control, and the GraphQL Admin and Storefront APIs for anything custom. Custom apps are typically Node or Ruby with React and Polaris for the admin UI, and headless builds use Hydrogen, Shopify's Remix-based framework. If a candidate describes editing theme code inside the online admin editor as their workflow, keep looking.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Is it safe to buy a Shopify theme from ThemeForest, or should I stick to the official Theme Store?
Stick to the official Shopify Theme Store. Its themes pass Shopify's review process, follow Online Store 2.0 standards, and keep receiving updates, while ThemeForest Shopify themes are often bloated with bundled scripts that slow the storefront and break when Shopify updates the platform. ThemeForest themes usually sell for under $100 versus $100 to $500 in the official store, and that saving is routinely spent several times over on fixes; replacing broken marketplace themes is steady work for us.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Who can build a custom Shopify development system?
Digital Heroes builds custom Shopify development systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other Shopify development companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
