Getting your data out before an inventory app shuts down
A standing export discipline for inventory apps: what to export quarterly, data-ownership questions to ask before buying, and a shutdown-week checklist.
InventoryX is in development and not available today. ClearStock is the live Shopify app.
The misconception: exporting your inventory data is a moving-day chore, something you do in the tense week between apps. By then it's often partly too late — the shutting-down app may already be degrading, the export that runs on the last day may drop two years of history without an error message, and there's nobody left to ask about the missing column. The better frame: an export is your proof that you own the data, and the only reliable time to test that proof is while the app still works. Below are three deliverables you can set up today — a quarterly export checklist, seven data-ownership questions to ask before buying any tool, and a shutdown-week timeline you'll hopefully never need.
If the app in question is Stocky specifically, the Stocky export guide covers exactly what that export contains and what it leaves behind; if you're moving between two live tools, the migration guide handles the move itself. This article is the standing habit that makes both of those easier — and the safety net when either comes too late.
What actually happens when an inventory app shuts down
The usual sequence: an announcement with an end date (sometimes), the app pulled from the Shopify App Store, API access to your store cut off, and finally deletion of server-side data per the vendor's privacy policy. Deletion windows in those policies are typically measured in weeks, sometimes days, after closure or uninstall — the number that matters is the one in the policy of the app you actually use, and it's worth reading that clause now, while it's academic. Uninstalling an app cuts its API access to your store immediately, though your own Shopify records are untouched (Shopify Help Center, accessed November 2026).
That last point is the reassurance and the trap. Your Shopify store keeps products, inventory levels, and order history natively — no app can take those. What dies with the app is the value-added layer: computed reorder points, velocity corrections, lead-time records, custom fields, PO history if the app was the system of record for it, alert configurations, dashboards. Some of that is re-derivable from Shopify's data with effort; some — the corrections and the history the app collected while Shopify wasn't looking — exists nowhere else.
Sellers in r/shopify describe realizing only after an uninstall that two years of history they'd built lived nowhere but inside the tool (paraphrased from r/shopify discussions, 2026). The data wasn't stolen and wasn't lost by negligence — it was never exported, because exporting felt like a task for a day that never came.
What to export, in priority order
| Priority | Export | Why it matters | If it's lost |
|---|---|---|---|
| 1 | Raw sales history by SKU (daily or order-level) | The irreplaceable one — the input to every baseline, velocity, and seasonality calculation | Only partly rebuildable from Shopify orders, minus the app's corrections |
| 2 | Inventory snapshot (SKU, on hand, cost, location) | Reconciles any migration against physical reality | Annoying but re-countable |
| 3 | PO history (order/receive dates, quantities, supplier) | Often the only source for measured lead times | Rebuilt from emails and spreadsheets, painfully |
| 4 | Supplier records and lead times | Re-entering them resets reorder math to guesses | Re-measurable, at the cost of a few bad cycles |
| 5 | Reorder settings (min/max, reorder points, coverage targets, custom fields) | Represents hours of calibration | Re-derived from history |
| 6 | App configuration (locations, rules, users) | Speeds up re-setup anywhere else | Re-derivable |
Priorities 1 through 3 earn their rank precisely because Shopify can't natively hand back the app's computed corrections, and the PO record is gone if the app held it. What usually won't export cleanly: dashboards, charts, alert rules, in-app notes. Screenshot those — cheap to capture, annoying to reconstruct, and the one part of an export that's guaranteed to survive every format quirk.
Seven data-ownership questions to ask before you buy
Ask these during the trial, while leaving is still free:
- Can I export everything, including history? Not just the current catalog — order history, PO history, computed fields. Ask for a demo of the export screen, not a yes.
- What format, and can I trigger it myself? CSV at minimum, self-serve, without a support ticket. If full export is gated to a top plan, treat that as a dealbreaker rather than a detail.
- What happens to my data on uninstall or closure? Get the deletion window from the privacy policy, and note whether export remains possible after you cancel.
- Is the app the system of record for anything? If it holds the only copy of PO history or lead times, price that risk into the decision or fix it with the quarterly export habit.
- Where does the data live, and who is the legal controller? Data residency and the named controller matter once customers are involved.
- Is my data used to train models or shared with partners? Check the policy's AI and training clauses — now a standard section in most terms of service.
- Can I get my data out structured and machine-readable? If you sell to EU customers, GDPR grants a right to data portability over data you provided and data generated through use (GDPR Article 20, accessed November 2026), and the UK ICO's guidance spells out the practical scope (ICO guidance on the right to data portability, accessed November 2026). A vendor that can't meet that bar for its own export feature is telling you something before you pay. The same questions are worth re-asking at a whole-store acquisition, where the tool stack changes hands with the stock — the buying-a-store inventory audit covers that side.
Run the same list against the inventory app evaluation checklist before any trial converts into a subscription — the answers belong in that evaluation, not in a post-mortem.
The shutdown-week timeline
| When | Do |
|---|---|
| Announcement day | Run the full export the same day. Tools sometimes degrade between announcement and shutdown — staff move on, integrations break, the export feature itself gets flaky. Don't wait for the deadline. |
| Same week | Verify row counts against your SKU count and spot-check entries (below). Screenshot dashboards and configuration screens. |
| Two weeks out | Fill gaps; re-export anything that came down partial. Decide on the replacement now if you haven't — moving between tools is its own project with its own sequence. |
| Final week | One last export after the final sync, so recent sales and receipts are captured. Confirm the deletion-window clause and save a copy of the policy. |
| After shutdown | Cancel paid tiers. Keep the export copies for at least a year. Note the policy's deletion date. |
One rule within the timeline: don't start a replenishment cycle in a dying tool. A PO raised two weeks before shutdown, received into a system nobody is syncing, becomes a blind spot you built on purpose — the stock arrives, nothing records it, and the successor tool starts life disagreeing with the shelf.
Verify the export actually captured everything
- Row counts. Exported SKU rows against your product count in Shopify; PO rows against your PO log. A silent truncation at 1,000 rows is the classic export failure.
- Spot-check 10 SKUs. One bestseller, one slow mover, one discontinued, one recently received. Do on-hand, cost, and last-sale date match what the app shows on screen?
- Open the file in a spreadsheet before you need it. Date formats (ISO or locale?), negative quantities, blank cost columns, truncated SKUs. Problems you find now are fixable; problems you find mid-migration are just problems.
- Keep two copies in two places. Local disk plus cloud. A single file on the laptop that dies in January is not a backup, it's a memory.
The real test of an export is opening it cold six months later and answering a question with it — run that test once now, while the app is still alive to cross-check you, and you'll never have to wonder whether the file is complete.
Common questions
How often should I export my inventory data? Quarterly is the working rhythm: often enough that your most recent export is never more than three months stale, rare enough that it stays a ten-minute task. Export immediately after any announcement touching your app — acquisition, pricing overhaul, sunset — and before any uninstall, whether yours or the vendor's.
What data should I export from an inventory app? In priority order: raw sales history by SKU, an inventory snapshot with costs, PO history, supplier lead-time records, reorder settings like min/max and custom fields, then configuration. Sales history is the irreplaceable one — Shopify holds orders natively, but the app's computed corrections and its PO record die with it.
What happens to app data after I uninstall? The app immediately loses API access to your store, but your Shopify records — products, stock levels, orders — stay intact. What the vendor retains on its own servers, and for how long, is governed by its privacy policy, with deletion windows typically measured in weeks. Read the clause before you uninstall, while you can still export.
Can an inventory app hold my data hostage? Legally, no in most cases: GDPR grants EU customers' data a right to portability, and reputable vendors offer self-serve CSV export regardless. Practically, some gate full history or API access behind top tiers or support tickets. Treat a paid or ticket-gated export as a red flag to check before buying, not after.
Is a CSV export enough? Usually, yes — CSV opens in any spreadsheet and outlives any vendor. Two caveats: confirm the CSV carries history and computed fields, not just the current catalog, and screenshot what can't tabulate, like dashboards and alert rules. Also keep two copies in different places; one file on one laptop isn't a backup.
Next step
Put a recurring 15-minute calendar entry on the first Monday of each quarter: run the priority-order export above, check row counts against your SKU count, and open the file in a spreadsheet. If your current app can't produce a complete export in one sitting, that finding belongs in your next tool evaluation — the evaluation checklist is where it goes.