Stocky Migration

Use Stocky migration tools to move practical supplier, mapping, purchasing reference, and sales-history context into BackstockOps without claiming full Stocky parity.

Plan Requirement

Migration import testing is available during trial and development. Full supplier and mapping imports require Ops or higher. Starter has limited import capacity.

Role Or Permission Requirement

When workflow roles are enforced, use a role that can manage suppliers, manage settings or imports, and view reports as needed for validation.

App Path

Shopify Admin > Apps > BackstockOps > Stocky migration.

Direct app path: /app/migration.

What Maps From Stocky

BackstockOps can help with:

Supplier records
Supplier SKU mappings
Preferred supplier context
Supplier costs and pack or order details where present in the imported data
Supplier PO CSV column definitions
Stocky purchase order references for operational history
Sales history imports used by forecasting and reports

What Does Not Fully Map

BackstockOps does not claim full Stocky parity. It does not replace every Stocky report, setting, label workflow, or historical screen. Shopify remains the source of truth for products, variants, locations, and current inventory.

Stocky API Behavior

When a Stocky API key is used, it is used for the connection/import workflow. BackstockOps does not store Stocky API keys as a long-term secret.

Recommended Migration Workflow

Open Stocky migration.
Test the Stocky API key if using API-assisted import.
Import suppliers.
Import product-supplier mappings.
Import supplier PO CSV columns if suppliers require custom files.
Import Stocky purchase order references if useful for context.
Review inferred supplier-variant mapping suggestions.
Approve correct suggestions and dismiss incorrect suggestions.
Import sales history if Growth reports or forecast profiles need it.
Validate by opening Suppliers, Replenishment, Purchase orders, Reports, and Settings.

Shopify Read And Write Behavior

Migration imports write BackstockOps supplier and operational records. They do not rewrite Shopify products, variants, locations, or current inventory.

Expected Success State

Suppliers and mappings appear in BackstockOps, replenishment rows can use preferred supplier context, draft purchase orders can use supplier SKUs and costs, and reports reflect imported data where supported.

Common Troubleshooting

A row cannot match a variant: check Shopify SKU, barcode, and duplicate SKU/barcode settings.
A supplier appears twice: merge or archive the duplicate after confirming mappings.
Costs are missing: verify the import column and Settings cost visibility.
Sales reports remain data-required: confirm sales history import completed.
Imported PO references are not editable live POs: treat them as reference context unless they were created as BackstockOps purchase orders.

Replace Stocky-Era Workflows
Supplier Mapping CSV Imports
Create and Manage Suppliers
Map Supplier SKUs to Shopify Variants
Use BackstockOps reports

Search Keywords

Stocky migration, Stocky API key, Stocky import, supplier import, mapping import, inferred mappings, PO references, sales history, Stocky replacement, Stocky parity