Migrating to a new Shopify store, and you sell gift cards and stored value. 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 gift cards and stored value
Shopify Payments is underwritten by Stripe, and Stripe explicitly restricts stored value products. The primary trigger is the nature of the product itself: once a gift card is redeemed, the transaction is effectively irreversible and the funds are instantly liquid. This makes it a favourite target for card-testing fraud and stolen-card schemes. The secondary trigger is your chargeback history — any merchant with meaningful gift card volume typically shows elevated chargebacks, which alone can bring a decline even if the product category were permitted.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a specific platform route for gift cards and stored value the way it does for some other restricted categories. What merchants usually try is requesting an exception through Shopify Support, citing low fraud or a clean chargeback record. That request is almost always declined because Stripe's policy is not negotiable at the Shopify level. The honest equivalent is that you need to move to an acquirer who specifically underwrites this category — one willing to price in the reserve and the chargeback risk — and then migrate your store to a payment gateway they actually support.
It only helps if all of these are true:
- Your chargeback ratio must be below 1% and documented for the last 12 months.
- You must have been processing for at least 24 months with no gaps or escalations.
- Your gift card terms must clearly state that cards are non-refundable and have an expiry date.
- You must be able to show that card-testing attempts have been blocked by your fraud tools.
- Your annual gift card sales volume must be under a threshold the acquirer sets during underwriting.
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
💎 High average order value, so fraud and disputes cost more per event
A single dispute or fraud event on a high-value order is material to your reserve and your processing relationship, so your new store's fraud rules—velocity checks, address matching, 3D Secure settings—must be configured before you migrate traffic, not after. Those rules live in your payment processor, not in Shopify, so they do not move automatically. Confirm your processor has copied your rule set to the new gateway account. Also confirm that your address verification and CVV matching rules are identical between old and new, because a sudden drop in fraud detection or a change in decline thresholds will show up immediately in your dispute rate. High-value orders attract more scrutiny from underwriters, so any hiccup in fraud screening during migration looks like a control failure. Test a high-value transaction on the new store before you cut over, using the same card type and geography as your typical customer.
🔁 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 gift cards and stored value, these are the facts that move the decision:
Document your chargeback and card-testing history in detail
This is the single highest-yield fix because every acquirer in this category will ask for it. Pull 24 months of chargeback reports from your current processor and sort them by type: true chargebacks from customers disputing legitimate gift card purchases, versus card-testing attempts that succeeded because the card was stolen. Acquirers assume stored value attracts fraud; your job is to show that you have either kept it out or handled it so well that the risk is containable. If your chargeback ratio is high, that alone may make you uninsurable, and no other fix will matter.
Rewrite your gift card terms to remove any refund obligation
Most gift cards sold online come with implicit or explicit promises that they can be refunded or converted to store credit under certain conditions. Stripe and conservative acquirers read any refund language as a liability: it means the cardholder can claim the transaction was unauthorised, then you will refund it, and then they will get the original card issuer to refund them too. Your terms must state plainly that gift cards are non-refundable once purchased, that they are not insurance or an escrow, and that redemption is final. Display this prominently and get legal counsel to review the language for your jurisdiction.
Set a hard expiry date on every gift card issued
Gift cards without expiry dates look to underwriters like you are holding customer funds indefinitely — a liability and a reserve driver. Set an expiry of 12 to 36 months from issue, depending on your business model, and enforce it in your system. Make the expiry date visible on the card itself and in the customer's account, and warn them at redemption time if they are close. This converts an open-ended liability into a time-bound one and signals to an acquirer that you have thought about risk.
Audit your fraud tooling and document what card-testing you have blocked
You need to show that you are not a soft target. Run a fraud filter on all gift card purchases — basic velocity checks (more than three purchases from the same card in one day), BIN mismatch, and AVS or CVV failures — and keep logs of what you blocked. Pull those logs and include them in your application. Acquirers assume you will see fraud attempts; they want to know you are catching them before they become chargebacks. If you are not running any fraud tooling at all, that is a compliance failure you must fix before applying.
What underwriting will ask you for
- Gift card terms and conditions exactly as displayed to the customer at point of sale.
- Chargeback and fraud reports for the last 24 months, broken down by card-testing versus customer disputes.
- Bank statements and processing reports showing gift card revenue separately from merchandise sales.
- Your current fraud filter settings and any third-party fraud tools you run.
- Customer service logs showing dispute resolution for common refund requests on gift cards.
- A breakdown of your gift card redemption rate and average time-to-redemption by cohort.
- Proof of any chargeback management or reserve agreements you have held with previous processors.
Getting underwritten for gift cards and stored value
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite gift cards and stored value. 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 gift cards and stored value
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
Gift card data is dangerous to move by hand because Shopify's gift card codes themselves are unreadable through any API — they are encrypted and stored server-side. If you try to export them, you get the structure but not the codes, so you cannot re-issue them into a new store. Outstanding balances can only be re-issued as new codes or as store credit, which means a real migration must plan for either a manual reconciliation window or a commitment to honour old codes in the old store while directing new customers to the new one. Get this wrong and you will either lose balances or expose yourself to double-redemption disputes.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 540images≈ 2 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 | 180descriptions≈ 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 | 180variants≈ 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 | 1,440metafields≈ 10 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 | 337records≈ 3 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 |
| Customers | 8,500customers≈ 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 | 35discounts≈ 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 | 4,200gift 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 | 37articles & pages≈ 2 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 help you here and will not reset your MATCH listing. Stripe's restriction on stored value is categorical, not a judgment on your company's history. What matters to an acquirer is your processing history as a person or business — chargebacks, card-testing volume, redemption patterns — all of which follow you across entities. A new company is more likely to fail underwriting, not less, because it has no history at all.
Frequently asked
Which payment gateway can actually process gift cards for me?
The gateway is straightforward — Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct all advertise this category. The real question is which acquirer behind them will take you. That depends on your chargeback ratio, your fraud history and your redemption speed. Rather than cold-email brokers, use the quote form on this page to connect with acquirers who specialise in stored value.
Why is my reserve so large, and how long will it be held?
Stored value is the highest-reserve category because the funds are instantly liquid and nearly impossible to reverse once redeemed. An acquirer will typically hold 10–25% of your monthly volume in rolling reserve for 180 days or more. That money is insurance against fraud chargebacks and card-testing losses. The exact percentage and hold period depend on your chargeback history and your sales volume — a cleaner history gets a smaller reserve and a shorter hold.
Can I move my outstanding gift card balances to a new store?
No. Shopify gift card codes are encrypted and cannot be read through any API, so you cannot export the actual codes. Outstanding balances must be re-issued as new codes in the new store, or you must honour them in the old store indefinitely and direct customers to redeem there. Plan for a reconciliation window where you issue replacement codes or store credit to customers who ask, and budget for a small loss from cards that go unredeemed.
If I get declined by one acquirer, will another even look at me?
Yes, but the clock is ticking. If you apply to multiple acquirers quickly without being declined, each will see a clean application. If you get declined, that decline is recorded in the industry database and subsequent acquirers will see it and be more conservative. Apply to one or two at a time and wait for a clear yes or no before moving on. Declining merchants commonly improve their application and reapply after six months.
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 →