Shopify's transition guidance says Stocky operational access ends after August 31, 2026. That creates two separate jobs: choosing a future inventory workflow and preserving the historical records already held in Stocky. Treat them as separate projects. A new system may accept products and current quantities while still failing to preserve purchase-order status, received quantities, supplier links, or the context behind old cost decisions.
1. Assign an owner and a deadline
Choose one person who is responsible for the archive. Record the store name, export date, Stocky user who produced the files, and the date on which the archive was checked. Do not leave the export until the final day. Large or older accounts may require several export passes, and an unreadable or incomplete file is much easier to fix while access is still available.
2. Export the historical record
The exact exports available depend on the workflows used by the store. At minimum, look for records covering:
- Purchase orders and their line items.
- Ordered and received quantities.
- Suppliers and supplier references.
- SKU and variant identifiers.
- Unit costs, currencies, freight, duty, and landed costs.
- Stocktakes, expected quantities, counted quantities, and variances.
- Any reports used for accounting, reconciliation, or supplier disputes.
Keep each raw CSV exactly as downloaded. Put edited copies in a different folder so an import mistake cannot overwrite the original evidence.
3. Verify that the exports are complete
A file existing on disk is not proof that it contains useful history. Open every CSV and check the header row, total data rows, earliest and latest dates, and whether important identifiers are populated. Blank supplier names, missing PO numbers, invalid quantities, and truncated files should be investigated before migration.
Compare a small sample against the Stocky screen: choose an old order, a partially received order, a closed order, and a recent order. Confirm that the exported quantities and costs match what the team expects.
4. Reconcile operational exceptions
Migration is a good time to find unresolved differences rather than copy them silently. Review ordered versus received quantities, repeated PO and SKU combinations, stocktake variances, and large cost changes. A repeated line may be a valid split receipt, but it may also be an accidental duplicate. Record the decision instead of deleting evidence without explanation.
5. Build a portable archive
A useful archive should not depend on one employee's spreadsheet knowledge. Keep the original exports, cleaned tables, a list of detected issues, summaries by supplier and SKU, a manifest of file names and fingerprints, and a human-readable report. Store at least two copies in locations controlled by the business.
6. Test the replacement workflow separately
Do not assume that importing a CSV recreates the old operational history. Test a small representative file first. Confirm which fields the destination keeps, which fields it ignores, and whether historical statuses or supplier relationships are changed. Preserve the archive even when the new system accepts an import.
Final sign-off
- All required Stocky exports exist in an untouched folder.
- Row counts, dates, suppliers, SKUs, quantities, and costs were checked.
- Receipt differences, duplicates, and stocktake variances were reviewed.
- The archive includes a manifest and can be opened without Stocky.
- A second person knows where the archive is stored.
For product-specific deadlines and limitations, review Shopify's official Stocky transition guide.
Check the files before you archive them
The free browser-only scan recognizes purchase-order and stocktake exports, checks common integrity problems, and never uploads CSV contents.
Run the free Stocky scan