Migrating to a new Shopify store, and you sell bullion and precious metals. 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 bullion and precious metals
Stripe, which powers Shopify Payments, lists bullion and precious metals on its restricted businesses. The primary trigger is the economics: five-figure order values and high product liquidity make these transactions textbook targets for fraud and chargeback abuse. Acquirers price this risk by holding reserves and running enhanced due diligence. The secondary trigger is AML and KYC obligations — depending on your jurisdiction, you may be obliged to verify customer identity and source of funds, which is compliance work that Shopify Payments does not support on your behalf.
Rule out the easy fix first — then deal with the real one
Rule this out first, because there is no documented Shopify route for this category. Some merchants try to list under a different MCC — collectibles, antiques, general retail — to slip past the restriction. That fails at underwriting because your transaction history and product photos declare what you actually sell. The honest equivalent is that you will need to source a high-risk acquirer directly, through a broker or by finding one that advertises metals. That acquirer will run a full application, verify your business and your compliance posture, and decide whether to take you on their high-risk MID.
It only helps if all of these are true:
- No documented platform route exists for bullion dealers on Shopify Payments.
- You will need to apply to a high-risk acquirer separately.
- Application approval is not guaranteed and depends on your volume and history.
- Most acquirers will hold a rolling reserve for the duration of your account.
- Bank transfer or ACH rails may be required alongside card processing.
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.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
Your metafields and metaobjects do not travel in Shopify's CSV export, which means any custom data—size matrices, distributor stock levels, compliance tags, pricing rules—either gets rebuilt by hand or gets lost. For a catalog of thousands of SKUs, hand-rebuild is impossible. You need a migration tool or script that can read your metafield schema from the old store and write it to the new one, field by field. Also watch for reference-type metafields that point to other products or collections: if they are copied naively, they still point at objects in the old store, so pages render with sections silently empty. Your distributor feeds—if they push data to product fields—will also break during migration because the feed is configured against the old store's API endpoints. Before you migrate, audit which custom fields are reference-type and which are populated by external feeds, then arrange for those to be re-pointed or rebuilt on day one. A catalog-heavy store that loses reference resolution looks live but serves broken pages.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For bullion and precious metals, these are the facts that move the decision:
Document your AML and KYC procedures in writing
This is the single highest-yield fix because it is the gap most bullion dealers overlook. You are not required to build a full compliance programme unless your jurisdiction mandates it, but you must be able to describe how you verify customer identity — at what order threshold, using what documents, and what you do if a customer refuses. Write a one-page policy covering red flags (cash payments, multiple orders in series, requests for refunds as wire transfers) and how you handle them. You do not need software; you need clarity. An acquirer reviewing a bullion application will ask for this, and having it written down is the difference between 'approved pending review' and immediate decline.
Prepare a complete transaction and chargeback history
Acquire or rebuild 12–24 months of processing records from your current or previous processor — settlement reports, dispute logs, and final outcomes. Bullion dealers who have not looked at their chargeback rate often discover it is far higher than they realised, usually because friendly-fraud claims ('I didn't receive it') are easy for buyers to file on high-value orders. If your rate is elevated, prepare an explanation: describe your shipping process, your insurance coverage, and the verification steps you take to prevent reshipping fraud. An acquirer will use this to set your reserve and monitor your account.
Audit your product claims and grading language
Review every product page and description for clarity on weight, purity, certification and grading. Vague claims like 'investment-grade' without a standard, or conflicting grades across variants, create buyer disputes and chargebacks. If you source from third parties, ensure their certificates are embedded or linked on your product pages so a buyer knows exactly what they are getting. Acquirers are sensitive to authenticity disputes, so clarity in your listings is compliance work.
Verify your supplier documentation is complete
Prepare invoices, certificates of authenticity or wholesaler agreements that prove your access to inventory. If you are a reseller, your suppliers must be legitimate and traceable. If you source from private sellers, document your vetting process. Acquirers will ask whether your stock comes from reputable sources, especially for higher-value items, because counterfeit or conflict materials create legal risk. A folder of clear, dated supplier documents will speed underwriting.
What underwriting will ask you for
- Proof of precious metals inventory or supplier relationships — invoices, certificates of authenticity, or agreements with wholesalers showing your access to stock.
- KYC documentation for your business — government ID, articles of incorporation, business license and proof of address.
- Bank statements for the last 12–24 months showing legitimate transaction history and absence of chargebacks.
- AML policy documentation — your customer verification procedures, transaction monitoring and red-flag protocols if you have them.
- Product photography and descriptions from your store showing the exact items you sell and how they are graded or certified.
- Processing history from any previous payment processor — statements and chargeback reports to show your dispute rate.
- Customer refund and chargeback log for the last 12 months to demonstrate your claims handling practices.
Getting underwritten for bullion and precious metals
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite bullion and precious metals. 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 bullion and precious metals
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
Precious metals stores are dangerous to move by hand because certification and grading data lives in metafields. Certificate of Authenticity references, weight specifications, purity percentages and assay details are stored as text or file references that a CSV export cannot read at all. If your metafields point to PDFs or images hosted on your old store, those links break silently — a customer clicks 'View Certificate' and gets a 404, but your product page still renders. On a regulated product with audit and authenticity requirements, that is a compliance gap, not a cosmetic one. A proper migration tool reads those metafields and re-homes the file references to your new store.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 6,800images≈ 28 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 | 850descriptions≈ 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 | 2,550variants≈ 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 | 5,100metafields≈ 34 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 | 990records≈ 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 |
| Product videos | 12videos≈ 48 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 | 1,200customers≈ 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 | 3,400orders≈ 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 | 8discounts≈ 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 | 30articles & 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 | 10apps≈ 10 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?
You do not need a new legal entity to apply for high-risk processing. If you have a history of chargebacks or disputes under your current business name, opening a new company will not reset your record — acquirers perform due diligence on the person behind the business as well as the business itself. A fresh entity may delay your application further while the acquirer waits for operating history. The honest move is to address the underlying risk — lower your chargeback rate, strengthen your compliance, improve your shipping — and apply as yourself.
Frequently asked
Which payment gateway will accept a bullion dealer account?
The gateway is the easy part; the merchant account is the hard part. Several high-risk acquirers publicly underwrite precious metals dealers — PaymentCloud, Corepay, Easy Pay Direct and others — and they typically integrate via Authorize.net or direct bank connections. But which acquirer will take your application, at what reserve level and with what monitoring, depends entirely on your volume, your chargeback history and the strength of your compliance documentation. Rather than send you to cold-email a dozen brokers, use the high-risk acquirer comparison on this page.
What reserve should I expect to hold?
Most acquirers hold a rolling reserve of 10–20% of your turnover for 90–180 days. This means if you process £50,000 in a month, the acquirer holds £5,000–10,000 and releases it slowly after the reserve period ends — typically 90 to 180 days after each transaction. The exact percentage depends on your chargeback rate and dispute history. Bullion dealers with clean histories get the lower end; those with elevated friendly-fraud claims get the higher end. Ask for the reserve policy in writing before you sign, because it directly affects your cash flow.
Will my product certifications and COA data survive a store move?
Standard Shopify exports cannot carry metafields — the database fields where you store Certificate of Authenticity references, weight specs and assay details. If you move by hand or use a basic CSV tool, those fields are left behind and your product pages become incomplete. Your migration service must specifically extract metafields from your old store, re-home any file references, and push them into your new store alongside products and images. Always ask your migration provider whether they handle metafields, because on a regulated product like metals, losing that data is not a minor inconvenience.
Do I need a new company to get approved for payment processing?
No. Opening a new entity will not help and may delay you further. Acquirers perform due diligence on the person running the business as well as the business itself, so a new company does not reset your history if you have a record of chargebacks or disputes. The real move is to address the underlying risk: document your AML procedures, lower your chargeback rate, strengthen your shipping and verification, and apply as yourself. A clean application from an established business is stronger than a fresh entity with no operating history.
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 →