Migrating to a new Shopify store, and you sell nicotine pouches. Migrate everything to a new Shopify store.
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.
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.
What you are looking at
- CSV export sits in your email, but it contains only SKUs, prices, handles and text fields — no images, no metafields, no order history, no discounts
- The new store builds, products look half-finished, and redirects are gone so search traffic drops immediately
- Gift card codes you issued do not appear anywhere, and no one can tell you how to get them back
- Reference metafields that pointed to collections or pages now point at nothing, leaving theme sections blank
- Custom menus you spent hours building are not there, so navigation is broken
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.
Why it happened — specifically for nicotine pouches
Shopify Payments is underwritten by Stripe, which lists nicotine products—including tobacco-free pouches—on its restricted businesses policy. The primary trigger is the product category itself: any pouch marketed as delivering nicotine is classified as a tobacco or nicotine product regardless of botanical origin. The secondary trigger is your business model. Subscription merchants are flagged more aggressively because recurring charges on age-restricted products create chargeback and fraud risk that makes processors nervous. A one-time sale can sometimes slip through; a subscription almost never does.
Rule out the easy fix first — then deal with the real one
There is no Shopify-documented route for nicotine pouches, so rule this out first. What merchants try is connecting a high-risk payment gateway and hoping the underwriting is simpler than Shopify's. It usually is not. You will still face a tobacco or nicotine merchant account application with the same underwriting questions: age verification proof, subscription billing documentation, shipping compliance in your target countries, and chargeback history. The difference is that Shopify Payments will decline you outright, while a high-risk acquirer will consider you—but that consideration is not an approval, and the gateway itself is not the bottleneck. The merchant account behind it is.
It only helps if all of these are true:
- You must prove age-gating technology is live on checkout and product pages.
- Your subscription terms must clearly state the customer's age requirement and cancellation rights.
- You must document shipping restrictions by country and your compliance checks.
- Your processor must be a high-risk acquirer; most mainstream gateways will not even quote you.
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
🔞 Requires age verification, and shipping is regulated in its own right
Migration means your age-verification flow moves too, and that flow is not just a Shopify setting—it is often a third-party app whose configuration, rules, and API keys do not travel in a standard export. You also need to know which states or countries require you to be registered as an age-restricted seller, because that registration is tied to your business entity, not your store URL. If you are using a carrier with adult-signature rules, those rules apply to the new store the moment you start shipping from it. Before you cut over, test the entire verification and checkout flow on a test order to a high-restriction state. A broken age gate does not just lose sales—it exposes you to carrier penalties and state-level compliance problems.
🔁 Recurring billing is a large share of revenue
A subscription business cannot afford downtime on stored payment methods. Your subscriber base and their billing schedules live in Shopify, and they will move with the store, but their payment method tokens are held by your processor, not by Shopify, and cannot be exported or imported at all. This means every subscriber's next billing date arrives at the exact moment you are most likely to have connectivity problems or incomplete migration. If you use Shopify Payments, tokens stay with Shopify—your new store can access them immediately. If you use a third-party processor, confirm in writing that they will release or continue to serve payment methods without interruption during the cutover window. Plan the migration for a day after your heaviest billing cycle, and notify subscribers 48 hours in advance that billing may be delayed. A lost billing cycle is revenue you will never recover.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For nicotine pouches, these are the facts that move the decision:
Implement age-gating on every product and at checkout
This is the single highest-yield fix. Every processor will ask for proof that you cannot sell to anyone under your target age—usually 18 or 21. Static text that says 'Must be 18+' is not enough. You need a live age gate: a checkbox the customer actively confirms, or better yet, a third-party age-verification service integrated into your checkout and attached to product pages. Document that service in screenshots and include the provider's name and verification method in your underwriting package.
Write clear subscription terms and obtain explicit consent
Subscription is a red flag by itself because of recurring-charge chargebacks. Write out your subscription terms in plain language: the frequency, price, cancellation mechanism and the customer's affirmative consent to being charged on that schedule. Many acquirers will ask for email evidence of customer opt-in or a recorded consent call for high-value subscriptions. Have this ready before you apply, not after.
Document your shipping and country compliance
Nicotine pouches face outright bans or heavy restriction in several countries and US territories. Build a shipping policy that lists every country you will and will not ship to, and explain why (legal ban, local customs restriction, or internal business decision). Then prove you enforce it: show how your store blocks checkout or requires additional verification for restricted regions. Acquirers will ask for this; having it ready shortens the underwriting cycle.
Gather your processing history or financial projections
If you have processed with another merchant account before—even if it was closed—bring the statements, chargeback reports and closure reason. Acquirers will check MATCH and see it anyway. If you are new, bring a realistic volume projection, your marketing spend plan and evidence of customer acquisition (email lists, social following, pre-launch signups). This is not about proving you will be huge; it is about showing you have thought through unit economics and compliance.
What underwriting will ask you for
- Proof of age-verification system (screenshots of your checkout and product-page gates)
- Subscription billing agreement and customer terms of service
- Product COA or specification sheet (nicotine content, origin, non-tobacco certification if applicable)
- Processing history from your previous merchant account or statement of volume projections
- Shipping policy showing country-by-country restrictions and how you enforce them
Getting underwritten for nicotine pouches
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite nicotine pouches. What none of them will tell you up front is the number that actually matters: what your business gets offered, once they have seen your volume, your claims and your history. Rate, reserve and settlement terms vary enormously between applicants in the same category.
Get real quotes from high-risk processors that accept nicotine pouches
Six taps and three details. We put it in front of the high-risk acquirers that actually underwrite your category and come back with what they will offer you — rate, reserve and settlement terms — so you are comparing real numbers instead of cold-emailing brokers for a fortnight.
The recovery playbook
- 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.
- 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.
- 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.
- 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.
- 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.
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:
Why this category in particular
Nicotine stores are dangerous to move by hand because subscription data lives partly in Shopify's subscription system and partly in metafields. Billing cycles, pause dates, customer consent records and dunning logic all exist in the subscription table, not as CSV; Shopify's CSV export cannot touch any of it. If you move by hand, you will copy the product and order history, but every active subscription becomes orphaned—the customer keeps paying the old store and never receives product, or the charges simply stop. For a category where recurring revenue is the model, a failed subscription migration is a financial crisis, not an inconvenience.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 600images≈ 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 | 215records≈ 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 | 2,800customers≈ 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 | 8,500orders≈ 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 | 22discounts≈ 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 |
| Blogs & pages | 20articles & pages≈ 1 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 | 8apps≈ 8 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 |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
A new legal entity will not reset a MATCH listing, so opening a second company does not erase the decline. That said, you do not strictly need a new entity to move processors. If your current entity has never processed nicotine before, and your previous processor declined you for a different category entirely, a high-risk acquirer may treat that as a clean slate. But if your entity is already on MATCH for nicotine, a new company is a delay tactic, not a solution. The honest move is to fix the compliance gaps on the entity that exists.
Frequently asked
Can I keep my current store and just switch payment processors?
No. Shopify Payments cannot process nicotine products at all, so you cannot stay on the same Shopify store and solve this with a gateway swap. You must migrate to a new Shopify store with a high-risk merchant account and a supported gateway. The new store is where you run your real business going forward. The old store becomes read-only or is shut down once customers and data have moved.
Which payment gateway will actually accept me?
Authorize.net offers high-risk merchant accounts and will quote nicotine merchants, as will specialist high-risk ISOs and acquirers such as PaymentCloud, Corepay and Easy Pay Direct. But 'will quote' is not 'will approve'. Each has its own underwriting criteria: age-verification proof, chargeback history, country restrictions and subscription terms. Rather than cold-email a dozen providers, use the acquirer network on this page or a high-risk payment broker familiar with nicotine.
Will my subscription data survive a store migration?
Only if you migrate it correctly. Shopify's CSV export does not include active subscriptions, billing cycles, pause dates or customer consent records. You must use Shopify's subscription API or a migration partner with subscription support to carry that data over. If you move by hand, every active subscription will break—customers will either keep being charged to the old store or charges will stop entirely. For a subscription business, that is a crisis.
What reserve should I expect on a nicotine merchant account?
Most high-risk acquirers hold 10–20% of your monthly volume in a rolling reserve for 90–180 days. This is not a penalty; it is standard for any restricted category with chargeback or age-verification risk. That means if your monthly volume is £10,000, you might see £1,000–2,000 held back from each month's settlement, released gradually over three to six months. Plan your cash flow around this and confirm the reserve terms before signing the underwriting agreement.
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.
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. How the migration runs, step by step →