Switch to Nstock in Days, Not Months

No implementation project. No consultants. Four CSV imports, a verification count, and you're running production — with a 90-day free trial so the migration costs nothing to try.

Start Free Trial Visit the Help Center

The Migration, Step by Step

1
Export your data

~1 hour

Every platform — Katana, inFlow, Cin7, Fishbowl, Craftybase, Sortly — exports products, stock, and vendors to CSV. Already on spreadsheets? You're a step ahead.
2
Import into Nstock

1–2 days

Four CSV importers do the heavy lifting: Master Products (your catalog), BOMs (recipes — components validated automatically), Stock Inventory (on-hand quantities and lots), and Suppliers. Start with your top 20% of products; expand once those are right.
3
Verify with a cycle count

2–3 days

Run a quick cycle count on your highest-value items to confirm imported quantities match the shelf. Discrepancies you find now are discrepancies your old system was hiding.
4
Go live

Week 1–2

Run production through Nstock and retire the old system. Materials deduct automatically, lots stay traceable, and your first live COGS numbers arrive with your first runs.

Coming From a Specific Platform?

Katana MRP

Export items, BOMs, and stock from Katana's data screens. BOM structures map one-to-one — including multi-level recipes.

Full comparison
inFlow Inventory

Export products and vendors from inFlow's CSV tools. Rebuild assemblies as Nstock BOMs — usually richer than what inFlow stored.

Full comparison
Cin7 Core (DEAR)

Export products, BOMs, and suppliers from Cin7's reference data. Most teams migrate a fraction of their Cin7 config — the rest was never used.

Full comparison
Fishbowl

Export parts, BOMs, and vendors via Fishbowl's CSV reports. Cloud migration means no more server maintenance.

Full comparison
Craftybase

Export materials, products, and recipes. Recipes become full BOMs — with the multi-level depth Craftybase couldn't model.

Full comparison
Sortly

Export your item list. You'll add BOMs and production workflows Sortly never had — that's the point of switching.

Full comparison

What Transfers

  • Master products: SKUs, names, units, categories
  • BOMs, including multi-level recipes
  • Current stock levels with lot numbers and expiry
  • Supplier list with contact details

Each importer validates your file and flags issues before anything is written — see the CSV field guides in the help docs.

Frequently Asked Questions

How long does switching to Nstock take?

Most small manufacturers are fully live in one to two weeks: about a day of exporting and importing, a few days of verification counts, and the rest running real production with the old system as a fallback. The 90-day free trial means the migration itself costs nothing.

What data can I import?

Master products (SKUs, names, units, categories), bills of materials including multi-level recipes, current stock levels with lot numbers, and your supplier list — each via its own CSV importer with validation and field guides.

Do I lose my history from the old system?

Your old platform's transaction history stays in its exports. Nstock starts fresh from your current stock snapshot — most teams keep a final export archive of the old system and never look at it again after the first month.

What if I'm switching from spreadsheets?

That's the most common migration. Your spreadsheets likely already match the CSV import shape — clean up column headers per the field guides, import, and run a verification count. The Startup Guide walks you through the order of operations on first login.

Can I run both systems in parallel?

Yes, and most teams do for the first week or two. Keep the old system read-only as a reference while production runs through Nstock — retire it once the numbers hold.

Your Old System Is the Risky Choice

The data conflicts, manual reconciliation, and surprise stockouts aren't the safe status quo — they're what you're escaping. Ninety days is more than enough to prove it against your real data.

Start Your Migration Free