Export Your Stocky Data Before August 31: What Comes Out, What Doesn’t, and What to Check

Stocky stops working on August 31, 2026. The app and its APIs both go on that date, and Shopify’s migration guide commits to read-only access to export your data for at least 90 days afterwards.

Read that grace period for what it is. It is read-only, so anything still in flight on the last day of August has to be closed out before then, not during it. It is scoped to export, so the APIs your other tools rely on are already gone. And “at least 90 days” is a floor Shopify sets rather than a date you can plan a quarter around. Treat August 31 as the deadline and the 90 days as the margin you hope not to use.

Most of the advice circulating about this is about which tool to move to. That decision can wait a fortnight. The export cannot. Do this first, evaluate replacements second.

What comes out

Purchase orders. The main export, and it runs through Stocky’s reports rather than a single export button. Go to Apps → Stocky, open the Reports menu, and run the Purchase Orders report. It carries arrival destination, delivery status and payment status per order, plus the quantity originally ordered on each line and the amount still outstanding across open orders. Save the report, then download it as CSV.

For a supplier-facing or SKU-level view, the SKU/Variant report is the one to shape: set your filters, choose your columns, save it, then download CSV or PDF. This is where cost per unit and selling price per variant come out.

Shopify’s guidance is the same, and worth quoting because it sets the scope: export “all completed purchase order reports, as CSV files,” using Stocky’s built-in reports. There is no one-click “export everything” in Stocky. You are running reports and saving each one.

There is also a per-PO route if you need a single order: Apps → Stocky → Purchases, open the PO, click Send, tick Attach CSV. Or open the PO and use Download for PDF, plain text, CSV, or CSV for Dymo. Fine for one-offs, impractical for a whole history.

Stocktake records. Your count history and the variances that came out of it. This is the audit trail behind your current on-hand numbers, and it is the thing you will want the first time a number looks wrong in the new system. Download a stocktake as CSV at any point during the count, and note Shopify’s own warning that Stocky does not save historical inventory data — so a stocktake you never downloaded is not sitting somewhere waiting to be retrieved. The file carries product name, SKU, barcode and Shopify ID alongside expected stock, counted stock and the variance.

Product cost data. Cost prices as Stocky holds them. Pull this even if your new system will import costs from Shopify, because the two are not always the same number and you will want something to reconcile against.

What does not come out

Supplier records. This is the one that catches people, and Shopify states it in four words in the migration guide: suppliers can’t be exported from Stocky. Names, lead times, minimum order quantities, payment terms, contacts — the configuration you built up over years — has to be rebuilt by hand in whatever you move to.

The same goes for anything you built in Stocky’s custom fields. Shopify’s FAQ is explicit that Stocky’s custom fields work only within Stocky, so they were never visible in your admin and they do not arrive anywhere by default.

The PO export is your best salvage. Vendor names and, by inference, real lead times sit inside that file: order date to receipt date, across a history of orders, is a better lead-time estimate than the one you originally typed in. MOQs and payment terms are not in there and will need to come from your own records, your emails, or your suppliers directly.

Budget real time for this. For a brand with thirty suppliers it is an afternoon. For one with three hundred it is a project, and it is the reason to start now rather than in the last week of August.

The order to do it in

1. Purchase orders, first and completely. Everything else can be partially reconstructed from Shopify or your accounting system. This cannot.
2. Stocktake records. Count history, variances, and dates.
3. Product cost data. Then reconcile it against what Shopify holds and note where they disagree.
4. Supplier reconstruction. Build a spreadsheet from the PO export — vendor, typical lead time, order cadence — and fill the gaps from your own records while the app is still there to check against.
5. Screenshot your settings. Reorder points, forecasting configuration, low-stock thresholds. These are not exportable either, and they encode decisions someone made for a reason.

What to check before the window shuts

An export that runs is not the same as an export that is complete. Open the files and look for:

• Blank cost fields. Common, and invisible until you try to calculate a margin six months later.
• Missing SKUs. Compare the SKU count in the export against your product count in Shopify. If they diverge, find out why now.
• Duplicate rows. Some exports repeat line items across paginated pulls.
• Truncated history. Check the oldest PO in the file against the oldest you remember. If the export capped at a date or a row count, you want to know while you can re-run it.
• Character encoding. Supplier names with accents or ampersands are a classic place for a CSV to mangle itself.

Fix problems while the source still exists. Re-running a report is trivial while the app is live and awkward once it is read-only.

There is one more thing to close out rather than export. Shopify’s advice is to stop raising new purchase orders in Stocky about a fortnight before the cutoff, and to receive and close every open, in-transit order before the deadline. Anything still open at cutover has to be recreated in Shopify as a purchase order or transfer for the remaining quantities only, because historical purchase orders cannot be imported. Native CSV upload adds line items to a new draft order and carries across no status, no received quantities, and no supplier links.

Why cost history matters more than it looks

Of everything on this list, cost history is the item whose loss compounds.

Landed cost, contribution margin by channel, and any decision about which SKUs deserve reorder budget all run off what you paid and when. Rebuilt from invoices and bank records, that history takes weeks and comes out approximate. Rebuilt from memory, it does not come out at all. And unlike inventory levels, it is not something your new system can derive from Shopify — Shopify knows what you sold, not what you paid a supplier eighteen months ago.

If you export one thing properly, make it this.

Then, and only then, choose a replacement

With the data safe, the replacement decision gets easier and less rushed. The short version: Shopify Admin absorbed transfers, adjustments and purchase orders, so if that is all you used Stocky for, the native tools cover you. What thinned out is the planning layer — supplier lead times and minimum order quantities survive only as reference metafields that Shopify says are independent of ordering and receiving calculations, there is no reorder-point field, and forecasting is now a conversation with Sidekick rather than a configurable model. If you used Stocky to decide what to buy, that is the gap to price.

Which one depends on where your demand comes from, and we have laid the options out in the best Stocky alternatives, including the case for staying on Shopify native. For the detail behind that case — what Admin absorbed and what thinned out — see Shopify’s native inventory vs Stocky. If reordering is the part you are worried about, working out what to buy in Shopify Admin covers the manual method and the point at which it stops scaling.

One thing worth deciding deliberately rather than by default: a forced migration is expensive whether you replace like-for-like or land somewhere with more headroom, because the cost is mostly the moving. If wholesale, retail EDI, or marketplaces are also drawing down your inventory, this is the cheapest moment you will get to put all of it on one system rather than bolting a second planning tool onto a Shopify-shaped view of demand. Endless Commerce vs Stocky is the head-to-head on what that looks like.

If you are reading this after the cutoff with the export still undone, the read-only window is probably still open: what you can still get back picks up from there, and rebuilding cost history covers the part no export will hand you.

Sources

Everything above is drawn from Shopify’s own documentation rather than from vendors selling a replacement. The shutdown date, the read-only window, the inability to export suppliers, and the list of what to export all come from Shopify’s migration guide at help.shopify.com/en/manual/products/inventory/transitioning-from-stocky. The export routes come from Shopify’s Stocky documentation on purchase orders, report types, supplier reports and stocktakes.

Two things still warrant a look at your own screen. Shopify says some Stocky features “might work differently or might not yet be available” in Shopify without enumerating them, and plan level changes what you get — ABC analysis, for one, needs an app on Basic and Lite. If your admin shows something different from what is described here, trust your screen and give yourself more time, not less.