Migration guide
Cin7 Omni to Cin7 Core: when the move makes sense (and when it doesn’t)
Same vendor, different product. Most Cin7 Omni features have a Cin7 Core equivalent, the licensing usually drops, and the operational simplicity goes up. But Omni does some things Core doesn’t — here is the honest assessment.
Short answer
Cin7 Omni is the vendor-managed, EDI-heavy, larger-footprint product. Cin7 Core is the modern, self-serve, faster-moving product. If you are on Omni and not using its EDI, vendor-portal, or 3PL features heavily, you are probably overpaying for capability you don’t need. Most SMEs end up cheaper, faster, and happier on Core.
When the move from Omni to Core makes sense
Light EDI use
If you only have one or two EDI trading partners (or none), Core is enough. Omni’s EDI infrastructure is overkill at that volume.
You want to self-serve config changes
Omni changes typically go through Cin7’s implementation team. Core is configurable by you (or a partner) without raising tickets for every tweak.
Annual licensing fatigue
Omni’s pricing is higher and typically annual upfront. Core is monthly per-plan and significantly cheaper at the SME end.
Modern integration stack
Core has a wider ecosystem of native modern connectors (Shopify, Amazon, Starshipit, Klaviyo, etc) and Make.com / Zapier work cleanly with its API.
When you should stay on Cin7 Omni
Heavy EDI
Multiple major retail trading partners (eg Woolworths, Coles, Bunnings, Officeworks) with full EDI. Omni’s EDI is best-in-class and migrating it is non-trivial.
3PL integrations at scale
Omni has mature 3PL/WMS connectors that Core doesn’t replicate one-for-one. If you are running multiple 3PLs with custom flows, Omni is likely the right home.
Vendor portal / B2B at enterprise scale
Omni’s B2B portal is more configurable and more stable at high concurrent user counts than Core’s.
Complex multi-entity / multi-currency
Omni handles multi-company structures more elegantly. Core can do it but with more workarounds.
What carries across cleanly
- Product master (with manual SKU mapping for legacy Omni naming)
- Customer and supplier master
- Opening stock balances by location
- Open sales orders and purchase orders
- Chart of accounts mapping (rebuilt for Core)
- Pricing tiers (mapped, not lifted)
What needs rebuilding
- EDI trading partner setups — different infrastructure
- 3PL integrations — rebuilt via Core connectors or Make.com
- B2B portal config — Core’s portal is a different beast
- Custom reports — moved to BI tool or rebuilt in Core
- Workflow automations — Omni’s automation differs from Core’s
- Document templates — rebuilt in Core
Omni → Core engagement
Larger and more careful than a fresh implementation — typically 8–12 weeks.
- Suitability assessment. Two-week deep dive: are you actually a Core fit? Honest answer in writing before any migration work begins.
- EDI / 3PL plan. If you have these, we plan their replacement (or rule out the migration) before anything else.
- Core tenant setup. Fresh Cin7 Core tenant configured to match your operational model.
- Data migration. Master data + opening balances. Historical transactions stay in Omni for reference.
- Integration rebuild. Channels, accounting, shipping, 3PLs — all reconnected via Core connectors.
- Parallel run. 1–2 weeks of running both systems in parallel to verify reconciliation.
- Cutover. Switch trading to Core. Omni archived, kept read-only for the financial year.
- Aftercare. Extended 60-day support window — Omni-to-Core projects throw more edge cases than fresh implementations.
Omni → Core migration FAQ
Will I save money by moving from Omni to Core?
Almost always, yes. Omni licensing for an SME-sized op is typically 2–4x what Cin7 Core costs at the equivalent functional tier. Even after one-off migration costs, payback is usually under 12 months. We model this for you during the suitability assessment.
Is Cin7 Core a downgrade?
It depends what you use Omni for. For pure operational inventory, sales, purchasing, and standard ecommerce — Core is equivalent or better, faster, more modern. For heavy EDI, multi-3PL, or enterprise-scale B2B portal use — Core is a downgrade and you should stay on Omni.
Can I move my historical transactions across?
You can, but most clients don’t. We export historical data from Omni for archive and analytics, but Core starts fresh with opening balances and open orders. This keeps the migration clean and avoids dragging years of legacy quirks into the new system.
What happens to my Omni tenant after migration?
Typically kept read-only for 6–12 months covering at least one full financial year, then decommissioned. You lose access to live edits but retain ability to look up historical records during that window. We help you negotiate the wind-down with Cin7.
Will Cin7 try to talk me out of moving from Omni to Core?
Cin7 (the vendor) will give you their honest assessment but they obviously prefer to retain Omni revenue. As an independent partner that implements both, our job is to tell you which fits your business — not which fits the vendor’s P&L. Sometimes that means recommending you stay on Omni.
What if I need EDI but only with one or two partners?
Cin7 Core can do basic EDI via integration partners (eg SPS Commerce, B2BGateway) or via Make.com middleware for simpler setups. We scope this case-by-case. If your EDI is genuinely simple, Core + middleware is materially cheaper than staying on Omni for the EDI alone.
Get an honest Omni vs Core assessment
We implement both. Our suitability assessment tells you straight whether the move makes sense for your business — including saying “stay on Omni” if that’s the right answer.