Data Migration
Alfred imports the records that take longest to rebuild by hand: suppliers, purchase orders, supplied products with their cost prices, and reorder points. There are two routes. If you're coming from Stocky, connect it once and Alfred pulls your records over its API — no exports, no spreadsheets, no reformatting. If you're coming from anywhere else, or you want to bring across records the API doesn't cover, every import also accepts a CSV. Your Shopify products, inventory, and sales history need no migration at all: Alfred syncs those automatically when you install it.
Two ways in
Import from Stocky
Direct, over Stocky's API
Enter your Stocky store name and API key once, preview what will come across, then import. Alfred reads suppliers, purchase orders, and supplied products straight out of Stocky. Nothing is exported, nothing is reformatted, and nothing is retyped. Available until Stocky's API shuts down on 31 August 2026.
Upload a CSV
From any system, any time
Every import Alfred offers also accepts a CSV: suppliers, supplied products and cost prices, purchase orders, and min/max reorder points. Column names are matched for you, and rows that can't be matched are reported back rather than silently dropped.
Key Concepts
What actually transfers
Suppliers, purchase orders (with their line items), supplied products with cost prices, stock adjustments, and min/max reorder points. Products, variants, inventory levels, and sales history are NOT part of migration — Alfred syncs those from Shopify automatically as soon as you install, so there's nothing to move.
What does NOT transfer — read this before the deadline
Stocktakes cannot be migrated. Stocky's API doesn't expose them and no CSV route exists, so if you need your counting history for audit or accounting, download it from Stocky yourself before 31 August 2026 and keep it as a record. It is unrecoverable afterwards. Supplier contacts and payment terms also don't come across in full — Stocky holds more against a supplier than it exposes — so check those after importing and fill in what matters to you.
What does NOT transfer
Stocktakes and counting history don't migrate from any system — Alfred starts your count history fresh. Supplier contacts and payment terms are worth checking after any import, since most systems hold more against a supplier than they export.
How rows are matched to your catalog
Imported line items and supplied products are matched to your Shopify catalog by SKU, with barcode tried as a fallback. Anything Alfred can't match is listed back to you rather than skipped silently — always read that list, because an unmatched row is usually a SKU that differs between systems rather than a product you don't stock. Alfred identifies products by variant ID internally, so SKUs being absent or reused doesn't corrupt anything; it only affects what can be auto-matched.
Imports are safe to re-run
Running an import twice doesn't duplicate your records — Alfred recognises what it has already imported and updates rather than re-creating. That means you can import a subset, check it, and come back for the rest without cleaning up in between.
How to Use
Import from Stocky — connect
Go to Configurations → Data Migration. You'll need two things from Stocky: your store name and an API key. In Stocky, open Preferences → API and copy the key; the store name is the one in your Stocky URL. Enter both in Alfred and choose what to import — suppliers, purchase orders, or supplied products.
Import from Stocky — preview, then import
Preview first. Alfred shows you exactly what it found and what it will create before anything is written, so you can confirm the counts look like your business rather than discovering it afterwards. Import suppliers before purchase orders — POs attach to suppliers, so doing it in that order means everything lands connected. Then import, and check the summary it returns.
Import from Stocky — verify
Open two or three suppliers and compare them against Stocky while you still can. Check cost prices and which products landed where, then open an imported purchase order and check its line totals. Verifying now is free; verifying after 31 August 2026 is impossible, because there's nothing left to compare against.
Upload a CSV — suppliers first
Everything attaches to suppliers, so import them first. Configurations → Suppliers accepts a supplier CSV, or you can create suppliers inline from any product table. Add lead time, MOQ, and pack size as you go — those three fields are what let Alfred round a reorder quantity to something a supplier will actually accept.
Upload a CSV — supplied products and cost prices
Open a supplier, scroll to Supplied Products, and choose Upload CSV. Alfred recognises the common column names for SKU and cost price, matches each row to your catalog, adds new products to the supplier, and updates ones already linked. Optional columns it will also pick up: supplier_sku, pack_size, moq, lead_time, and supplier_product_name. Unrecognised columns are ignored, so you can upload a report as-is without deleting anything.
Upload a CSV — purchase orders
Upload a purchase order CSV and Alfred matches line items to your Shopify catalog by SKU. Open purchase orders matter most — those are stock you're still expecting, and they feed Alfred's inbound calculations so reorder suggestions don't double-order what's already on the way.
Upload a CSV — reorder points
Configurations → Purchase Thresholds accepts a min/max CSV. Rows match by variant ID, SKU, or barcode, and the Location column takes the location name as you'd write it — if a name doesn't match, Alfred tells you which names are valid rather than failing silently. Single-location stores have it filled in automatically. This is what makes Min/Max replenishment work on day one instead of after you've hand-set every threshold.
Run both systems in parallel before you commit
Generate a forecast and a purchase plan in Alfred, then compare it against the decision you'd have made in your old system. Switch fully once they agree. This is the step that turns a migration from a leap into a check.
Tips & Best Practices
- ✓Import suppliers before purchase orders. POs attach to suppliers, so the order matters — do it the other way round and you'll have orders that aren't connected to anything.
- ✓Always read the unmatched-rows list. A row Alfred couldn't match is usually a SKU that differs between systems, not a product you don't carry — and it's far easier to fix during migration than to notice later when a reorder suggestion looks wrong.
- ✓Selling in euros? Cost prices written as 47,91 with a comma decimal import correctly — you don't need to convert them first. Semicolon-separated exports from euro-locale spreadsheets are detected automatically, as is Excel's 'CSV UTF-8' format.
- ✓Re-running an import doesn't duplicate anything, so import a small slice first, check it, then do the rest.
- ✓Stocktakes don't migrate from anywhere. If you need your counting history, export it from your old system and keep it as a record.
- ✓Big catalog, long supplier list, or heavy PO history? Get in touch — assisted migration exists precisely for that, and 'I have 60 suppliers to move' is the case it was built for.