Migration guides
Migrate to Cin7 Core without losing data, history, or sleep
Source-specific migration playbooks from a partner that has done this dozens of times. Pick your starting platform and read the honest version of what changes, what carries across, and where the traps are.
Pick your starting platform
The mechanics of a Cin7 Core migration depend heavily on where you are coming from. Below are the four most common starting points we handle for Australian businesses. Each guide covers what carries across, what doesn’t, the typical gotchas, and a realistic timeline.
Migration guides by source platform
DEAR → Cin7 Core
The smoothest path — same vendor, same product DNA. Mostly a rebrand for existing tenants but legacy DEAR-only workflows still trip people up. What to clean up before you switch the signage.
MYOB → Cin7 Core
For MYOB customers ready to leave MYOB entirely. Stock, sales, and purchasing move into Cin7 Core; accounting moves to Xero (Cin7 Core’s native partner). Clean cutover, no parallel systems.
Cin7 Omni → Cin7 Core
Different product, same vendor. Most Omni features have a Core equivalent but some don’t — and pricing usually drops. Honest assessment of when this move makes sense and when it doesn’t.
Unleashed → Cin7 Core
Same category, similar pricing — but different strengths. Common move for businesses adding a Shopify channel or wanting native Xero integration. Data structures are close enough to migrate cleanly.
What every migration includes
- Data audit on the source system before we touch anything
- Mapping document — every field, every workflow, signed off before migration
- Test load into a Cin7 Core sandbox tenant first
- Reconciliation report comparing source vs destination after every load
- Cutover plan with rollback steps documented
- Parallel run option for high-risk migrations
What rarely migrates cleanly
- Custom fields created in the source system — destination structures differ
- Document templates (invoices, POs) — almost always rebuilt in Cin7 Core
- Historical transactions — usually frozen in the source system rather than carried across
- Attachments — sometimes possible, sometimes a manual lift
- Custom reports — rebuilt in Cin7 Core or in your BI tool
- User permissions — re-set in Cin7 Core, never copied verbatim
Not sure which path applies?
If you’re running something else (Xero alone, spreadsheets, an old Sage install, an in-house system), we still handle the migration. Book a call and we’ll scope the right approach.