Stocky's export window is closing. Your records don't have to.
Stocky's own migration guide tells merchants to export completed purchase order reports, stocktake history and historical cost data as separate CSV files before read-only access ends. This turns those exports into one linked, searchable, offline archive — with an honest statement of what it does and does not prove.
See a worked examplePreview your own export before you pay; the exact price is confirmed first.
Read your Stocky exports
Upload your purchase order report CSV — plus stocktake history, historical cost data and attachments when you have them — bounded to 25 MiB and 20,000 purchase-order rows. Get back a self-contained ZIP: an offline HTML index, normalized CSV and JSON with your original values preserved, a dangling-link and missing-table report, and a completeness statement.
Your result archive-rescue.zip
$29.00 one-time
Start with your exportShow the work
Fictional purchase orders. Actual output.
A ZIP containing purchase_orders.csv, stocktakes.csv, cost_history.csv and two attachments — one linked, one dangling on purpose, to show how that is reported.
Download this inputThe actual output on the input at left: index.html, purchase_orders.csv, orders.json, stocktakes.csv, cost_history.csv, manifest.json and the original file, unmodified.
Download this result| PO Number | Supplier | Status | Outstanding Amount |
|---|---|---|---|
| PO-EX-1001 | Fictional Ceramics Co | received | 0.00 |
| PO-EX-1002 | Fictional Ceramics Co | partial | 90.00 |
Rule version: archiverescue.v1
This archive contains 2 purchase order header rows and 3 SKU line rows as received, hashed at a0e269f5ec22. No authoritative total purchase-order count was supplied with this archive, so completeness is UNKNOWN: the hash proves the integrity of the bytes received, not that they represent the merchant's entire Stocky purchasing history. 2 attachment file(s) were found; 1 could not be matched to any purchase order in this file and are listed as dangling. Stocky does not support exporting a separate supplier list ("Suppliers can't be exported from Stocky", per Shopify's migration guide). A supplier identity in this archive is only whatever the Supplier column of a purchase-order report row itself contains; there is no independent supplier directory to reconcile against.
Report existence and read-only export window confirmed https://help.shopify.com/en/manual/products/inventory/transitioning-from-stocky (fetched 2026-09-22): completed purchase order reports, stocktake history and historical cost data are exportable as CSV; read-only access continues at least 90 days after 2026-08-31 (>= 2026-11-29, a floor not a deadline). Shopify does not publish this package's exact CSV column headers; the column set used here is DERIVED from the report fields Shopify's guide and independent migration playbooks describe, and is labeled as derived, not an official Stocky export spec.
Export compatibility
Shopify's migration guide states, verbatim: "You'll have read-only access to export your data for at least 90 days after" August 31, 2026 — a floor of at least November 29, 2026, never a countdown deadline we sell against. It names three exports as CSV files: completed purchase order reports, stocktake history, and historical cost data. It also states "Suppliers can't be exported from Stocky" and "Historical Stocky purchase orders can't be imported into Shopify".
Shopify does not publish the exact CSV column headers for those reports. This tool's column set is our own derivation from the report fields Shopify's guide and independent migration writeups describe in prose, labeled as derived everywhere it appears — never presented as an official Stocky spec. An export missing the one required column, "PO Number", is refused as unsupported, not guessed at.
No supplier directory — Stocky does not export one, so a supplier name is only whatever appears inside a purchase order row itself. No live Shopify or Stocky connection, no automatic import back into Shopify, no guarantee this covers your entire purchasing history. Confirm your own current Stocky export access directly; this page's citation is not a substitute for checking your own account.
Read-only export access from Stocky is documented to last at least 90 days past August 31, 2026. Confirm your own account still has export access before relying on this workflow, and export while you still can — this tool cannot restore data Stocky itself has already removed.
Know before you start
A purchase_orders.csv report, or a ZIP of that CSV plus stocktakes.csv, cost_history.csv and an attachments folder. Up to 25 MiB compressed, 2,000 archive members, 20,000 purchase-order rows. Path traversal, symlinks and unrecognized file types are refused, not silently skipped.
A hash proves the bytes you gave us were preserved intact. It does not prove this is your complete Stocky purchasing history — there is no authoritative total to check it against, and the archive says so explicitly. This is not a complete backup and not a guaranteed recovery of anything Stocky itself has already deleted.
This hosted journey sends your file to our server only after you confirm the transfer disclosure. Your uploaded file is retained for up to 30 days, or sooner when you request deletion. Your delivered archive is retained for up to 7 days after it is built. No automated system decides what your data means beyond the documented parsing rules above.
An archive with no purchase_orders.csv is refused before any scope is priced. A zero-row purchase order file is still a valid, priced result — it is common for a new or empty Stocky account.