How to migrate from Stocky: a step-by-step guide

Step 1 — Export every CSV Stocky offers

Shopify’s own transition guide tells every Stocky merchant to export their data to CSV and states plainly that historical purchase orders cannot be imported into Shopify. API, so save the Low Stock CSV as an independent copy you control. Also save every stocktake, the Purchase Orders parent list and every individual PO, adjustments, Stock on hand, available Transfers, Average cost and other reports. Minimum order quantities are more awkward still: Stocky exposes them in neither its API nor any CSV, only on screen under Vendors → your vendor → Order limits, so copy that table per vendor.

Do this first, before comparing apps. Our Stocky CSV export guide covers what Shopify tells you to export and how to check each file is actually usable — including the classic mistake of re-saving files in Excel and corrupting them.

Step 2 — Know what Shopify keeps automatically

Not everything needs migrating. Products, variants, current stock levels and your entire sales history live in Shopify itself and are untouched by Stocky’s end of life. The layer Stocky added on top — supplier records, purchase order history, stocktake records and planning numbers — is not moved into Shopify automatically. Stocky will remain available read-only for at least 90 days, but save independent copies while you can. The full breakdown is in what happens to your Stocky data.

Step 3 — Choose where the planning layer goes

Shopify’s free native tools now manage suppliers and purchase orders, Sidekick can use sales data to recommend products and draft an order, and Flow can send low-stock notifications. They still do not provide the same persistent replenishment policy with supplier lead times and minimum order quantities — we compared them honestly here. If Stocky’s reorder suggestions were your working queue, you need a replacement app; here is how UreyukiBox compares, including where Stocky is still ahead.

Step 4 — Copy your data with a Stocky migration tool

CSVs preserve values but flatten relations: which product you buy from which supplier, which orders belong to whom. A migration tool that reads the Stocky API directly can keep those relations intact. In UreyukiBox this is a wizard on the free plan: paste a Stocky API key and it preserves suppliers, purchase-order parents and lines, stock-adjustment parents and lines, purchase tax types, API payloads and product–supplier candidates recovered from PO history.

Suppliers feed current operations. Historical purchase orders, lines, adjustments and sources can be searched and reviewed in Stocky Data, then downloaded as CSV or PDF. Copied purchase tax types remain reference data and are not assigned to products automatically.

Shopify states that every Stocky API stops working on August 31, 2026. The later read-only period does not extend this step, so the API deadline drives the schedule, not the app choice.

Step 5 — Use standalone Stocky CSV import from September 1

Open Stocky CSV import directly from the Stocky migration entry. It is an independent migration route and does not require the API copy, a Stocky API key or Shopify sync. Start with low_stock_csv.csv for reorder points and lead times. Then import each stocktake’s download_csv.csv, the purchase_orders.csv parent list, every normal purchase_order_<number>.csv, adjustments, Stock on hand, available Transfers, Average cost and other Stocky reports — the exact screens are here. UreyukiBox retains the original and normalizes tables it can parse. Minimum order quantities have no export, so paste each vendor’s Order limits table. Statistics-style tables are also supported as pasted screen tables with their filter context. For notes visible only on a Stocky screen, add a sourced manual note in Stocky Data and attach evidence when needed. The UreyukiBox walkthrough covers the exact screens and filenames.

Step 6 — Review Stocky Data, then archive the raw files

Search the retained records, open purchase-order and adjustment details, review normalized rows and their sources, and export CSV or PDF from Stocky Data. Compare against Stocky, then keep the original files somewhere safe and unmodified. They are the independent snapshot you control after Stocky becomes read-only and, later, unavailable.