Migration
Getting your data out of Stocky before you lose it
Most of what Stocky held also exists somewhere else in Shopify. Two things do not, and if you lose those you are rebuilding them by hand from invoices.
Checked 29 September 2026
The two things that only exist in Stocky
Cost prices. What you paid for each item. Shopify has a cost per item field, but if you were maintaining costs in Stocky it is entirely possible yours were never written back to the product. Check a handful of products in Shopify admin before you assume it is safe. If the field is empty, that number lives in Stocky and nowhere else, and losing it means you cannot calculate margin on anything until you rebuild it from supplier invoices.
Supplier and lead time records. Which supplier you buy each item from, what they charge, and how long they take. Shopify has no concept of a supplier at all, so there is nothing for this to fall back to.
What you can safely leave behind
Stock quantities are already in Shopify, because that is where Stocky was writing them. Sales history is in Shopify. Product data is in Shopify. You do not need to export any of it, and exporting it will just give you a stale copy to confuse yourself with later.
Received purchase orders are a judgement call. The stock movement is already reflected in your inventory, so operationally you lose nothing. What you lose is the audit trail of what you ordered and what actually arrived. If you have ever had a supplier dispute, keep them.
Export order
| Order | What | Why it is that urgent |
|---|---|---|
| 1 | Cost prices per SKU | Cannot be reconstructed from Shopify. Margin reporting depends on it |
| 2 | Supplier list with contacts and lead times | Shopify has no supplier object to fall back to |
| 3 | Open purchase orders | Stock you have paid for but not received |
| 4 | Received purchase order history | Only matters for disputes and audit |
| 5 | Stocktake history | Rarely needed once the counts are in Shopify |
Do one and two today even if you have not decided what you are moving to.
Where the data goes next
If you land on a spreadsheet, put cost price and supplier on the same row as the SKU and nothing else. Every store that starts with a clever multi tab workbook ends up with one flat sheet within a quarter.
If you land on an app, check before you commit whether it will import a supplier list at all. Several in this category expect you to type suppliers in by hand, which is fine at thirty and miserable at four hundred.
If you land on a build, the export is the specification. What you carried out of Stocky is by definition the part you were using.
Want a second pair of eyes on the export?
Send me what you have pulled out and I will tell you what is missing before the access goes rather than after.