Migrating from Cin7 to a Full ERP: When and How to Make the Jump

Cin7 to Full ERP Is a Common ANZ Mid-Market Step#

For ANZ businesses outgrowing Cin7 Core (formerly DEAR Systems) or Cin7 Omni, the question is which full ERP to migrate to and how to manage the migration. This article covers when migration is justified, target ERP selection, and the realistic playbook.

When Cin7 Migration Is Justified#

Common triggers:

• Multi-entity expansion. Cin7 organisations are single-entity; multi-entity businesses need ERP with multi-entity capability (NetSuite OneWorld, MYOB Acumatica, etc.).
• CRM and sales pipeline depth. Cin7's customer records don't include sales pipeline, opportunity tracking, or activity logs. Businesses with sales-team-led operations outgrow this.
• Financial reporting depth. Cin7 + Xero handles accounting; complex financial reporting (multi-dimensional, real-time consolidated) requires full ERP.
• Manufacturing complexity. Cin7 Core handles light to mid-market manufacturing; deeper requirements (full MRP, finite-capacity scheduling) need full ERP.
• B2B/wholesale complexity. Pricing rules beyond Cin7's basic structure, credit management depth, EDI integration with chain retailers.
• Compliance. ISO 27001, SOC 2, or industry-specific compliance requirements may exceed Cin7's capability.

When NOT to Migrate#

Many ANZ businesses stay on Cin7 indefinitely. Cin7 is the right home when:

• Operations remain single-entity and focused on inventory/orders
• Xero handles all accounting needs
• Manufacturing remains light (single-level BOMs or simple multi-level)
• Total operational complexity stays within Cin7's scope
• Business growth doesn't introduce new compliance or reporting requirements

Target ERP Selection#

The most common ANZ Cin7 migration destinations:

For multi-entity, global expansion: - NetSuite OneWorld (most common) - Microsoft Dynamics 365 Finance and Operations

For ANZ mid-market with manufacturing: - MYOB Acumatica - Sage X3 (industry edition)

For Microsoft-aligned businesses: - Microsoft Dynamics 365 Business Central - Microsoft Dynamics 365 Supply Chain Management (for deeper manufacturing)

For modular ERP path: - OpsUI (per-module pricing, no implementation partner overhead) - Odoo Enterprise (open-source flexibility)

Cin7 Core to NetSuite/Acumatica/D365 BC#

Most common migration. Realistic ANZ timeline: 6-12 months.

Cost Comparison#

Source	Target	All-in cost
Cin7 Core	NetSuite	NZ$300,000–600,000
Cin7 Core	MYOB Acumatica	NZ$280,000–500,000
Cin7 Core	Dynamics 365 BC	NZ$200,000–450,000
Cin7 Core	Sage X3	NZ$280,000–550,000
Cin7 Core	OpsUI (modular)	NZ$150,000–350,000

OpsUI's modular pricing typically results in lower migration cost because there's no large implementation partner overhead.

Cin7 Omni to Full ERP#

Less common but real. Cin7 Omni already has multi-channel and retail POS depth that ERP migrations need to match.

Migration considerations#

• POS hardware integration must be maintained or replaced
• Multi-channel sales integrations must be rebuilt against new ERP
• Retail-specific workflows (returns, exchanges, loyalty) need ERP equivalents
• Often takes longer than Cin7 Core migrations (12-18 months)

The Migration Playbook#

Phase 1: Discovery and Mapping (4-6 weeks)#

Activities: - Document current Cin7 configuration - Document Xero integration and decide future state - Map Cin7 data structures to target ERP - Identify operational processes to redesign vs replicate - Define data retention policy - Plan target ERP architecture

Key insight: Cin7's data model is modern and well-documented. This makes mapping straightforward compared to Sage or QuickBooks migrations.

Phase 2: Configure Target ERP (10-20 weeks)#

Activities: - Implement target ERP's chart of accounts (often redesigned) - Configure modules for required business processes - Build integrations (sales channels, Xero or new financial system) - Build custom workflows where standard doesn't fit - Configure multi-entity (if applicable)

Phase 3: Data Migration and Testing (4-8 weeks)#

Activities: - Extract data from Cin7 (typically via API or CSV export) - Transform and load to target ERP - Validate data integrity - UAT with key business users - Performance testing

Phase 4: Parallel Validation (4-8 weeks)#

Activities: - Cin7 remains production - Mirror critical transactions in target ERP - Reconcile reports between systems - Train users on target ERP - Identify and fix discrepancies

Phase 5: Cutover and Hypercare (4-8 weeks)#

Activities: - Final data migration - Cutover to target ERP production - Cin7 becomes read-only - Hypercare period - Handoff to internal team

What Migrates Well#

• Customer/vendor master records
• Item master records (with restructured attributes)
• Open transactions (AR, AP, inventory)
• Recent transaction history
• Sales channel mappings (with rebuild)
• Xero integration approach (often continues with new ERP)

What Requires Rebuild#

• Sales channel integrations (Shopify, Amazon, etc.) — rebuilt against new ERP's APIs
• Custom report templates from Cin7
• Workflow automations specific to Cin7's structure
• POS hardware integration (if migrating from Cin7 Omni)
• Custom fields from Cin7 may need restructuring

Common Migration Failure Patterns#

1. Underestimating sales channel integration rebuild. Cin7's connectors don't port; each channel needs rebuild against new ERP.
2. Skipping parallel run. Even though Cin7 is modern and migration is technically clean, business processes need validation.
3. Trying to recreate Cin7 exactly. Migration is an upgrade opportunity; new ERP capability should be embraced, not constrained to Cin7's scope.
4. Wrong target ERP selection. Migrating to enterprise ERP when modular alternative would fit better; or modular when enterprise would have been appropriate.
5. Inadequate change management for power users. Cin7 power users find new ERPs less intuitive; need investment in training.

Xero Continuation Strategy#

Most Cin7 migrations keep Xero alongside the new ERP for accounting. Specific architecture decisions:

• Cin7 + Xero (current). Cin7 owns operations; Xero owns accounting. Sync between them.
• New ERP + Xero (post-migration option A). Same architecture but with broader ERP capability. Xero continues for accounting.
• New ERP (replaces Xero) (post-migration option B). New ERP's built-in accounting replaces Xero. Larger migration scope.

For most ANZ Cin7 migrations, keeping Xero is the lower-risk, lower-cost option. The new ERP brings operational capability without replacing accounting.

Decision Framework#

Use this framework to evaluate target ERP:

Need	Likely target ERP
Multi-entity, multi-country expansion	NetSuite OneWorld
Strong ANZ tax + manufacturing	MYOB Acumatica
Microsoft 365 integration	Dynamics 365 BC
Process manufacturing depth	Sage X3 Process
Modular pricing, lower cost	OpsUI
Open-source flexibility	Odoo Enterprise
Single platform with retail POS	Cin7 Omni (stay) or NetSuite SuiteCommerce

See Also#

For broader context, see Cin7 vs Unleashed Comparison, Inventory Management Module Architecture, NetSuite vs MYOB Acumatica Comparison, What is a WMS?, and Data Migration Disasters Case Studies.