Moving from Stocky to UreyukiBox, start to finish

Before you start: one API key

The only thing to prepare is a Stocky API key — the credential that lets UreyukiBox read your Stocky data on your behalf. In Stocky, sign in as the store owner, click the person icon at the top right, open Preferences, choose API access, and press Generate.

Two cautions. The key is displayed once, so copy it there and then. And it is a credential: paste it into the UreyukiBox migration screen and nowhere else. A read-only key is all the migration needs, and you can delete it in Stocky once you are done.

The copy wizard, in four screens

1. 1. What will be copied

   The opening screen lists the data groups and the deadline so there are no surprises. Read the scope and continue.

2. 2. Paste the API key

   The connection is tested on the spot. If it fails you get a message rather than a silent stall — a truncated copy-paste is the usual cause, so copy the key again from Stocky.

3. 3. Wait for the copy

   A spinner is shown while the server runs the one-shot copy. There is no made-up percentage or per-stage progress. If you reopen the wizard, it shows whether the copy is still running or has ended. A few minutes is typical.

4. 4. Check the counts

   You get a count for each resource type that was saved. If a stage failed, the successful records are already stored and you can run the whole copy again. Existing Stocky IDs are upserted, so re-running does not create duplicates.

Standalone Stocky CSV import from September 1

Open Stocky CSV import directly from the Stocky migration entry. It does not depend on an API copy, API key or Shopify sync. UreyukiBox keeps the original CSV and normalizes every table it can parse. For what to export and how to keep the files usable, follow the Stocky CSV export guide; the short version is to save the raw files and resist re-saving them in a spreadsheet app.

Low Stock: reorder points and lead times

In Stocky open Reports → Low Stock → SKU/Variants → CSV and save low_stock_csv.csv. The importer reads reorder points and supplier lead times, then previews additions and overwrites before anything is applied.

Stocktake history

Open Inventory → Stocktakes, open every stocktake you want to retain, and download its download_csv.csv. Browser suffixes such as download_csv (1).csv and download_csv (2).csv are accepted without renaming. You can select several at once. The CSV itself has no date or location; choose the matching row from the copied Stocky stocktake-list metadata, or leave the value unknown and correct it later. Importing records the counts without moving any stock — Stocky already pushed those adjustments to Shopify when they were run, so re-applying them would double-count. What you get is the paper trail.

Purchase orders, adjustments and reports

From Reports → Purchase Orders save the parent purchase_orders.csv, then open every purchase order under Purchases and download its normal purchase_order_<number>.csv. Import adjustment reports, stock_on_hand.csv, Transfers only where Stocky shows a CSV button, Average cost and other Stocky reports with the category and filter conditions used to obtain them. Do not substitute the Received Only or Not Received Only PO exports for the normal individual file.

Minimum order quantities

MOQs are in neither the API nor any CSV, but Stocky lists them per vendor: open Vendors → your vendor → Order limits (headed “Variant minimum order values”) and you get a table of Product / Variant / SKU / Min Order. Select it, copy it, and paste it into the MOQ box in UreyukiBox.

You do not need to tidy it into a spreadsheet. Stocky right-aligns the quantity, so copying often drops the number onto its own line. UreyukiBox reads the paste by meaning rather than by position — it pairs each SKU with the next quantity that follows it — so header rows and wrapped lines are fine. Anything it could not match, whether an unknown SKU or a quantity with no SKU, is listed back to you rather than silently dropped.

Notes and screen-only evidence

Fields present in an API payload or CSV are retained with their source. Stocky does not provide a verified API or CSV route for every supplier or purchase-order note, so UreyukiBox does not pretend those fields exist. If a note appears only on screen, add a sourced manual note in Stocky Data and attach a screenshot or file as evidence when needed; the source and acquisition context remain visible.

What it costs, and the guarantee

Migration itself runs on the free plan. Historical purchase-order and adjustment details, imported reports, normalized rows, source files and evidence can be reviewed in Stocky Data and downloaded as CSV or PDF. Generic normalized rows beyond the plan allowance are masked on the server rather than delivered to the browser. Copied purchase tax types are retained as reference data and are not assigned to current products automatically. Paid operational features come with the store’s single 14-day standard trial (or the remaining time if the store changes plan or resubscribes).

If the API copy fails to complete for a reason on our side, we refund the billing month immediately following the migration in full. Stocky CSV imports and Order limits/Statistics table imports are outside that guarantee — whether a file imports cleanly depends on its columns, encoding and how Stocky wrote it, none of which we control. If one gives you trouble, write to support@ureyukibox.app and we will look at it with you.

Common questions

Does this change anything in Stocky?

No. The copy only reads. Stocky is left exactly as it was, so you can keep using it as a reference during active use and Shopify’s later read-only window.

Can I run the copy more than once?

Yes. Each run fetches the resources again and upserts them by Stocky ID, so existing rows are updated rather than duplicated. Running it again close to the deadline can pick up changes made in Stocky in the meantime.

Do I have to use Stocky to use UreyukiBox?

No. The migration is optional. A store that never used Stocky syncs from Shopify and starts drafting purchase orders from that alone.

What if I miss August 31?

The API copy is no longer possible: every Stocky API stops that day. Shopify says Stocky remains read-only, with exports, for at least 90 days, so use the standalone Stocky CSV import route to save every available CSV. Paste Order limits (MOQ) and Statistics tables in their supported importers, attach evidence and verify what you saved.

Stocky migration FAQ

Is the Stocky migration free?

Yes. One Stocky migration entry provides the API-copy route and, from September 1, a standalone Stocky CSV import route that does not require API copy. Order limits (MOQ) and Statistics are supported as pasted screen tables; manual notes and evidence retention are also included without a paid tier. Historical records and original files can be reviewed by data type in Stocky Data and exported as CSV or PDF. Normalized generic rows beyond the plan allowance are masked on the server. Copied purchase tax types are retained as reference data and are not assigned to products automatically. If the API copy fails for a reason on our side, we refund the billing month immediately following migration in full; Stocky CSV imports and Order limits/Statistics table imports are excluded. The free plan caps active operations at 100 products, but the migration itself is not subject to that cap.

How long is Stocky migration still possible?

The API copy must finish by 31 August 2026, when Shopify says every Stocky API stops. Shopify will keep Stocky available read-only, including exports, for at least 90 days after end of life, but that does not extend API migration and Stocky history is not moved into Shopify. If you use the API-copy route, finish it by the deadline. Separately, save independent CSVs now and use standalone Stocky CSV import from September 1 without relying on API copy.

What Stocky data can be migrated automatically?

Through August 31, the API-copy route in Stocky migration preserves suppliers, purchase-order parents and line items, stock-adjustment parents and line items, purchase tax types, API payloads and product–supplier candidates recovered from PO history. From September 1, the standalone Stocky CSV import route in the same entry accepts Low Stock, stocktakes, PO lists and individual POs, adjustments, Stock on hand, available Transfers, Average cost and other reports without requiring API copy. MOQs and Statistics-style tables use their supported paste importers; manual notes and evidence preserve screen-only information.

Will migrating change my Shopify stock levels?

No. Syncing and the migration are read-only against Shopify inventory. Stock only moves when you act in UreyukiBox afterwards: receiving a purchase order, making a stock adjustment, finishing a stocktake or transferring between locations.