Home / Payments recovery / Migrating to a new Shopify store
Migrating to a new Shopify store

Your store needs a new home. Keep everything that matters when you move it.

You are moving to a new Shopify account — whether because a payment processor cut you off, you are restructuring your business, or you simply need a fresh start. The email to yourself feels straightforward: export the old store, import into the new one, done. Here is what actually happens. Shopify's own CSV export cannot carry metafields, metaobjects, orders, gift card codes, videos, themes, menus, discounts or redirects. Those things exist in your store right now. They will not come with you on their own. Even when data does move, reference-type metafields copied naively will still point at objects in the old store, so pages render with sections silently empty — your customer sees a broken layout and you do not know why. This is not a failure of process. It is the real shape of the problem. The only way through is to move deliberately, then run the whole migration a second time and compare counts — products, orders, customers, redirects, all of it — so you know what is actually missing before you flip the switch.

No card. Read-only. It shows you exactly what would move before you pay anything.
Fixed price from $247Read-only — we never write to your old storeLive in as little as 48 hoursVerified twiceFull refund if we can't migrate you1,500+ migrations
19,630
records in your storeproducts, images, variants, metafields, customers, orders
43 hrs
to move it all by handabout 1 working week of your time, and only if nothing goes wrong
8 of 14
have no CSV route at allorders, metafields, menus, theme content, videos, apps, gift cards
$247
to have all of it donefixed price, and we only ever read from your old store
That is what is sitting in a store your size right now, and what a hand-move would cost you. Scroll for the line-by-line breakdown — or move the whole thing for a fixed price.
Fixed price · verified twice · zero downtime

Move all of it into a new store, from $247

One-time packages, no per-record metering, no quotes. The order form unlocks the moment you pay, counts are matched against your old store, and the entire migration then runs a second time — the second pass has to create nothing.

Standard DIY Migration
$247
$349
Fully automated migration up to 20,000 entities: products, collections, customers, pages, blogs, menus, redirects, files, metafields, theme.
Complete Migration
$397
$549
Everything in Standard DIY up to 100,000 entities, plus full order history with tracking, discounts, gift cards, product reviews, markets and translations, Klaviyo & review app reconnection, and a scheduled zero-downtime DNS cutover.
Concierge Cutover
$497
$699
Everything in Complete up to 250,000 entities, plus a full app-stack reinstall & reconfiguration session (Klaviyo flows, pixels, loyalty), Recharge subscription coordination, priority scheduling and 30 days of post-launch support.
Enterprise Migration
$797
$1199
Base fee for unlimited entities, multi-store and franchise rollouts, dedicated migration engineer with a direct line, weekend/overnight cutovers, unlimited re-migrations within 90 days and 60 days of support.
Not ready to pay while your payouts are frozen? Run the free demo scan first → — read-only, no card, and it shows you exactly what would move.

And then there is the part that actually loses businesses

If you do need a new store, the payments problem turns out to be the easy half. This is what is sitting in your current store right now, and what happens to each piece when someone tries to move it by hand:

What a hand-move actually costs · a typical store
What you ownHow much of itWhat breaks doing it by handWhat we do instead
Product images 750images≈ 3 hrsbulk re-upload, ~15 sec each By handthe CSV carries image URLs and alt text, but they point at your OLD store's CDN — so the moment the old store goes, every image 404s. Re-upload and Shopify appends a dedupe suffix to the filename, which breaks every theme section and product description that referenced the original URL Automatedevery file re-uploaded through the API with its alt text and variant attachment intact, its content type preserved so image-restricted fields still accept it, and every reference to the old URL rewritten
Product descriptions 150descriptions≈ 2 hrsone pass to repair inline image links — the CSV carries the text By handdescriptions are full of inline images and links pointing at the old store's CDN. Paste them into the new store and the text survives perfectly while every embedded image quietly dies — which you usually discover from a customer, not from a report Automatedbodies copied verbatim, then a second pass rewrites every source-CDN URL inside them to the re-uploaded file on the new store
Product attributes & variants 450variants≈ 45 minthe CSV carries these; the time is verifying option order By handoption ORDER is part of the product's identity. Rebuild "Size, Colour" as "Colour, Size" and every theme swatch, saved customer URL and app that keys on variant position breaks — silently, because the product page still renders Automatedvariants upserted by SKU with option names and order preserved, so swatches, deep links and app data keep working
Metafields & metaobjects 900metafields≈ 6 hrsonly the reference, JSON and metaobject fields, ~1 min each By handthe product CSV carries simple text and number metafields — but not metaobjects, and not reference or JSON types, which is exactly where app data and theme content live. Reference fields are the real trap: copy the value and it still points at objects in the OLD store, so the page renders and the custom block is silently empty Automatedwritten in dependency order after their targets exist, with embedded references re-pointed at the new store's objects — and any value whose reference cannot be resolved is dropped rather than written broken
SEO data & redirects 252records≈ 2 hrsredirects one at a time, plus a handle audit By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing
Your custom theme 1theme≈ 6 hrs2–10 hrs depending on how customised it is By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing
Product videos 8videos≈ 32 minre-upload and re-attach, ~4 min each By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed
Customers 5,000customers≈ 2 hrsCSV import, then cleaning up the rows that fail By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were
Order history 12,000orders≈ 8 hrsa paid third-party importer, plus a day of mapping and reconciliation By handShopify's own CSV importer cannot create orders at all, so the hours here assume you buy a third-party importer — key them in by hand instead and 9,400 orders is closer to 390 hours, which is why nobody does that and why order history is simply abandoned in most DIY moves. Then support cannot answer a warranty claim, repeat-purchase segments are empty, and every returning-customer flow starts from zero. Getting the mapping wrong duplicates orders or re-dates them to today, and both are worse than not importing at all Automatedfull order history recreated through the API with line items, properties, customers re-associated, original dates and tracking numbers intact
Navigation menus 3menus≈ 1 hrsabout an hour to rebuild and relink them all by hand By handmenu items store resource IDs, not paths, so nothing about them is portable — every link has to be re-pointed at the equivalent collection, page or product on the new store Automatedmenus rebuilt with their nesting, and every item re-pointed at the equivalent object on the new store
Discount codes 25discounts≈ 1 hrsabout 1 hr via the discount CSV, or ~3 hrs rebuilt by hand By handthe discount CSV covers basic codes, but automatic discounts, quantity breaks and combination rules are not in it and have to be reconstructed by hand. A subtly wrong rule is worse than a missing one, because nobody notices until it has been over-discounting for a fortnight Automateddiscounts recreated through the API with their rules, usage limits and dates intact, including automatic and free-shipping types
Gift card balances 40gift cardsno manual routecannot be moved by anyone By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them
Blogs & pages 42articles & pages≈ 3 hrsrecreated one at a time, ~4 min each By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten
Apps & app data 9apps≈ 9 hrsabout 1 hr per app to reinstall, reconfigure and re-test By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store
19,630
records in your storeproducts, images, variants, metafields, customers, orders
43 hrs
to move it all by handabout 1 working week of your time, and only if nothing goes wrong
8 of 14
have no CSV route at allorders, metafields, menus, theme content, videos, apps, gift cards
$247
to have all of it donefixed price, and we only ever read from your old store
We move every one of those records, match the counts against your old store, then run the entire migration a second time — the second pass has to create nothing, which is how you know everything we exported actually landed.
Free · read-only · no card

See these numbers for YOUR store, free

That is a typical mid-size store. The read-only scan counts yours — every product, variant, image, customer, order and metafield — so you know what is actually at stake. No card required.

▶ Run the free demo scan

What you are looking at

Your held balance
No payout clock runs during a store migration — you are setting up infrastructure, not moving money yet.
Your checkout
The new store is not live until you finish the migration and switch over. Until then, checkout is disabled because the store is not yet receiving orders.
Is an appeal realistic?
Not applicable — this is not an appeal against a decision.
Appeal timeline
Migration time depends entirely on store complexity. There is no standard timeline. What matters is validation time — the period when both stores are running and you can verify the new one is complete before switching traffic over.

The real urgency is data loss, not speed. A reference-type metafield pointing at the old store will stay broken once you flip traffic to the new one, and by then fixing it means downtime. The genuine deadline is the period before you go live — you must validate everything works while you still have both stores running and can check the old one. After cutover, the old store is usually deleted and there is no way back.

Find out what you would actually loseThe free audit connects read-only to your store and counts every product, variant, image, metafield, customer and order in it. No card, and it never writes to your store.
▶ Start the free audit

The recovery playbook

  1. Audit what your store actually containsList everything that matters: products, orders, customers, discounts, redirects, gift cards, navigation menus, theme choice, metafields and metaobjects. Do not assume you know. Log into your current store and count. Orders and gift card codes will not export through CSV — you will need those lists for manual verification later. Make a spreadsheet with baseline numbers for every category. This is the document you will compare against in step 5.
  2. Get a verified copy of your store out while you still have access — todayBefore you create the new account, request a full backup from Shopify support in case something goes wrong. This is the step people skip, and it is the only one with a deadline you do not control. A migration is not an instant thing — it can take days or weeks, and you will still have the old store running. But the moment you delete it, a full backup becomes impossible. If a metafield is misconfigured in the new store, or a theme does not carry over, or reference data points nowhere, you may need to look at the old store to understand why. Once it is gone, that information is gone. Backups are the only insurance you have.
  3. Export and move what CSV can carry, manually handle what it cannotRun Shopify's CSV export. It will contain products, variants, prices, handles and text fields. It will not contain metafields, metaobjects, orders, gift card codes, videos, themes, navigation menus, discounts or redirects. Move the CSV into the new store. Then handle the missing categories one by one: metafields must be recreated (some third-party apps can help, but none are universal); orders must be exported from reports as a separate archive; gift card codes cannot be read through any Shopify API and must be re-issued; videos and media must be re-uploaded; themes must be selected and configured again; navigation menus must be rebuilt; discounts must be recreated; redirects must be re-entered or exported from a third-party SEO app if you used one.
  4. Check reference metafields point to the new store, not the old oneIf you use reference-type metafields — fields that link to collections, pages, products or other objects — those references will still point at the old store after migration. Pages will render with sections blank or broken. You must systematically update each reference to point at the equivalent object in the new store. If a metafield references a collection called 'Summer Dresses', find that collection in the new store and re-link it. This is tedious. There is no way around it. Skipping it is why new stores launch with invisible sections.
  5. Run the migration again, count everything, and compareBefore you go live, treat this as a full second migration. Export the old store's data again. Import it into the new store again, overwriting what is there, so you capture any changes made in the old store since you started. Then count: products in old store versus new store, orders in old store versus new store, customers, redirects, discounts, everything. If all counts match, you have moved what can be moved and you know what is missing. If a count does not match, find out why before you switch traffic over. Once the old store is deleted, you cannot go back. This step is what separates a successful move from a move that looks successful until customers and search engines find the broken pieces.
Before you talk to any processorKnow exactly what your store contains and what a move would involve. It costs nothing and it works even if your storefront is already offline.
▶ Start the free audit

New company, new merchant account — the honest version

What a MATCH listing actually is

What a new merchant account requires

The entity

Formation documents, EIN or company number, and a business bank account in the company's name with a voided cheque or statement.

The people

Government ID and personal details for every beneficial owner. Underwriting is done on the humans as well as the company — which is why a new company with the same owners does not present as a new applicant.

The history

Three to six months of processing statements if you have any, plus bank statements. A prior termination is disclosed here. Concealing it is the fraud, not the termination.

The website

A live, compliant storefront: clear billing descriptor, contact details, terms, refund and shipping policies, SSL, working checkout, and no claims that contradict your category.

The product

Supplier agreements, certificates of analysis for anything ingestible, licences for anything regulated, and evidence of how you fulfil.

The numbers

Expected monthly volume, average order value and your chargeback history. Understating volume to get approved is a fast route to a frozen account.

A MATCH screen

Run against both the business and its principals. This is the step that decides the application, and there is no way around it — only through it, by disclosing and finding an acquirer who underwrites anyway.

If you do need a new entity, these are the routes people actually use

Costs and timelines below are indicative and go out of date — treat them as a starting point, not a quote.

US flag
US — Delaware LLC or C-corp
$500 one-time, registered agent ~$100/yr after year one
1–2 business days to incorporate; EIN can take longer without a US SSN
Worth knowing before you pick it: Atlas onboards you into Stripe — the same underwriting engine that runs Shopify Payments. Excellent for forming a company; not a route back to card processing for a category Stripe declines.
US flag
US — any state
~$39 + state filing fee; registered agent ~$125/yr
Days, depending on the state
The cheapest credible US route. You handle the EIN yourself, which is free and straightforward with an SSN.
US flag
US — Delaware or Wyoming
~$399 including state fees; ~$299/yr agent
About a week end to end
Built for non-US founders, which is the case where the extra cost over a bare filing actually buys you something.
UK flag
UK — private limited company
Packages ~£110–160 + VAT (the Companies House fee rose to £100 on 1 Feb 2026)
Same day to 24 hours
Non-resident packages exist. A UK company does not by itself give you a UK bank account — that is a separate application.
UK flag
UK — private limited company
Comparable tiers to the above
Same day to 24 hours
Functionally interchangeable with Companies Made Simple; pick on the address and secretarial add-ons you actually need.
UK flag
UK — private limited company
Free formation — you pay only the Companies House fee
24–48 hours including the bank account
The cheapest UK route by a wide margin, because the formation is a loss-leader for the bank account. Fine if you want the account anyway.
Estonia flag
Estonia — OÜ
e-Residency card €100–150, company state fee €265, address and contact service €200–400/yr
2–5 weeks — collecting the card is the bottleneck
A real EU company with real EU obligations, not an offshore shell. Slower than it looks because of the card collection step.
Hong Kong flag
Hong Kong — private company limited by shares
Roughly US$600–1,200 for the first year via an agent, including secretary and registered address
1–4 days to incorporate; banking is the slow part
Incorporation is fast and banking is not. Most merchants end up using a fintech account rather than a traditional bank.

Wyoming is the default for an ecommerce LLC: ~$100 to file, ~$60/yr to maintain, no state income tax and strong owner privacy. Delaware is the investor standard and costs $300/yr in LLC franchise tax for governing law most DTC stores will never rely on. If you are not raising money, Wyoming is almost always the right answer.

Fixed price · verified twice · zero downtime

Move everything for a fixed price

One-time packages — no per-record metering, no quotes. The migration order form unlocks the moment you pay, and the whole migration re-runs a second time before any cutover.

Standard DIY Migration
$247
$349
Fully automated migration up to 20,000 entities: products, collections, customers, pages, blogs, menus, redirects, files, metafields, theme.
Complete Migration
$397
$549
Everything in Standard DIY up to 100,000 entities, plus full order history with tracking, discounts, gift cards, product reviews, markets and translations, Klaviyo & review app reconnection, and a scheduled zero-downtime DNS cutover.
Concierge Cutover
$497
$699
Everything in Complete up to 250,000 entities, plus a full app-stack reinstall & reconfiguration session (Klaviyo flows, pixels, loyalty), Recharge subscription coordination, priority scheduling and 30 days of post-launch support.
Enterprise Migration
$797
$1199
Base fee for unlimited entities, multi-store and franchise rollouts, dedicated migration engineer with a direct line, weekend/overnight cutovers, unlimited re-migrations within 90 days and 60 days of support.
Not ready to pay while your payouts are frozen? Run the free demo scan first → — read-only, no card, and it shows you exactly what would move.

How the migration runs

  1. Book & pay — fixed price, secure Stripe checkout. The order form unlocks immediately after payment.
  2. Submit your stores — domains and details in the order form; then provide revocable API tokens in your customer area (we never ask for your Shopify password).
  3. We migrate everything — your live store keeps selling throughout; it is only ever read from.
  4. Verified twice — the entire migration re-runs and must change nothing; you get the count-matched verification report before any cutover.
Free · read-only · no card

See exactly what would move — before you spend anything

The demo scan connects read-only to your current store and counts every product, variant, image, customer, order and metafield in it, then tells you what a migration would carry across. It never writes to your store, and it works even if your storefront is already offline.

▶ Run the free demo scan

What this looks like in your industry

The mechanics above are the same for everyone. What differs is why you were flagged, who will underwrite you, what reserve to expect, and what is sitting in your store that has to survive a move. Pick your category:

Hemp & cannabinoids
Supplements & ingestibles
Nicotine & inhalables
Adult
Weapons & self-defense
High-value goods
Alcohol
Beauty & food
Medical devices
Other regulated categories

Frequently asked

Can I just export and import the CSV and call it done?

Not unless your store contains only text fields and product SKUs. Shopify's CSV export leaves behind metafields, metaobjects, orders, gift card codes, videos, themes, menus, discounts and redirects. The things most stores rely on. You can move the CSV, but then you have half a store. You need a plan for each missing category before you go live.

What happens to my customer data and order history?

Orders do not export through CSV. You must download them separately from your reports or ask Shopify support for an export. Customer email addresses and account records do not appear in CSV either — those must be exported separately as well. Customer data is critical, especially if you have consent timestamps for email marketing. Treat orders and customers as a separate export, verify the counts match the old store, and keep that list safe before you delete the old store.

Will my gift card codes transfer?

No. Gift card codes cannot be read through any Shopify API — no one can extract them, not even Shopify. That means they cannot be automatically moved. You must issue new gift cards in the new store. If you have outstanding balance on old codes that you want to honor, you will need to track and re-issue manually, or accept the loss. Check what gift cards you have issued before the move so you know what you are dealing with.

What about my theme and navigation menus?

Themes and menus do not export through CSV. You must select a theme in the new store and configure it from scratch, or pay a developer to replicate your current theme's customizations. Navigation menus must be rebuilt manually. If you used a third-party app to manage menus, check whether that app can export and re-import. The theme and navigation are visible to every customer, so do not skip them.

How do I know nothing was left behind?

Count everything. Before you go live, export the old store's data one more time. Import it into the new store again. Then compare: product count, order count, customer count, discount count, redirect count. If counts match, you have moved what can be moved. If a count is off, investigate why before you switch traffic. Do not assume the migration is complete until you have verified it. Once the old store is deleted, verification becomes impossible.

Still weighing it up?Start with the free read-only audit. It tells you what would move, what would break if you did it by hand, and which package your store actually needs.
▶ Start the free audit
Ready when you are

Move everything, verified twice, from $247

Pick a package and the migration order form unlocks immediately. Your existing store is only ever read from — we never write to it, so nothing you still have can be made worse.

Standard DIY Migration
$247
$349
Fully automated migration up to 20,000 entities: products, collections, customers, pages, blogs, menus, redirects, files, metafields, theme.
Complete Migration
$397
$549
Everything in Standard DIY up to 100,000 entities, plus full order history with tracking, discounts, gift cards, product reviews, markets and translations, Klaviyo & review app reconnection, and a scheduled zero-downtime DNS cutover.
Concierge Cutover
$497
$699
Everything in Complete up to 250,000 entities, plus a full app-stack reinstall & reconfiguration session (Klaviyo flows, pixels, loyalty), Recharge subscription coordination, priority scheduling and 30 days of post-launch support.
Enterprise Migration
$797
$1199
Base fee for unlimited entities, multi-store and franchise rollouts, dedicated migration engineer with a direct line, weekend/overnight cutovers, unlimited re-migrations within 90 days and 60 days of support.
Not ready to pay while your payouts are frozen? Run the free demo scan first → — read-only, no card, and it shows you exactly what would move.
Play it straightA migration moves your data — it is not a way around a platform or processor rule, and it will not get a decision reversed. You remain responsible for fixing whatever triggered the review, for telling a new processor the truth about your business and your history, and for complying with Shopify's Terms of Service and your new provider's rules. What we make certain of is narrower and more useful: that when you do have somewhere to sell, none of your catalog, customers, order history, content or SEO got lost getting there.