QuickBooks to NetSuite or Business Central: when to move
Signs you've outgrown QuickBooks or Xero, how NetSuite and Business Central compare, and what ERP migration involves, from chart of accounts to controls.
By the Ceety Systems teamUpdated 6 min read
Key takeaways
- Move when the workarounds cost more than the system: month-end in spreadsheets, multiple entities, inventory or revenue rules QuickBooks cannot model.
- NetSuite is cloud-only and strong for multi-entity, multi-currency companies. Business Central runs online or on-premises and fits teams built on Microsoft 365.
- The migration is mostly design work: a new chart of accounts and dimensions, a decision on how much history to bring, and rebuilt integrations.
- Set up approvals, roles and period locks at go-live. Add SOX-style controls only when an IPO is on the horizon.
It is time to move from QuickBooks or Xero to an ERP such as NetSuite or Microsoft Dynamics 365 Business Central when the business has outgrown what the ledger can model. The usual triggers are several legal entities, inventory, or revenue rules that live in spreadsheets, and a month-end close that depends on a few people and manual journals. Choose between NetSuite and Business Central based on entity structure, the tools your team already uses, and how you want to customize.
Signs you've outgrown QuickBooks or Xero
No single metric decides it. Look for several of these at once:
- Multiple entities or currencies. You consolidate subsidiaries in Excel, and intercompany balances rarely tie out first time.
- Month-end runs on spreadsheets. Accruals, deferred revenue, allocations and reconciliations happen outside the system and are pasted back as journals.
- Inventory has outgrown the add-ons. Several warehouses, landed costs, assemblies or lot tracking are handled by a patchwork of apps.
- Reporting needs more dimensions. You need profit by product line, department, location and customer segment together.
- Plan limits bite. QuickBooks Online publishes its usage limits: Plus allows 5 billable users, 250 accounts and 40 combined classes and locations; Advanced allows 25 users. Hitting these is a symptom, not the reason to move.
- Approvals happen in email. Purchase approvals, vendor changes and journal reviews have no record in the system.
- An investor, lender or buyer is asking questions. Due diligence, an audit or a bank covenant exposes how much depends on manual work.
If only one of these applies, a better-configured QuickBooks or Xero plus one or two integrations may be enough. ERP is a bigger commitment in cost, process and people.
NetSuite vs Business Central
Both are mid-market ERPs with general ledger, payables, receivables, cash management, inventory and reporting. They differ more in shape than in features.
| Oracle NetSuite | Microsoft Dynamics 365 Business Central | |
|---|---|---|
| Deployment | Cloud only (software as a service) | Online in Microsoft's cloud or on-premises |
| Multiple entities | OneWorld manages many subsidiaries, tax jurisdictions and currencies in one account, with consolidated reporting | Separate companies in one environment, with intercompany postings and consolidation |
| Reporting segments | Departments, classes and locations, plus custom segments | Dimensions on every entry |
| Customization | SuiteCloud: SuiteScript (JavaScript), workflows, custom records | Extensions written in AL in Visual Studio Code; apps from Microsoft's marketplace |
| Ecosystem | SuiteApps and a large partner network | Partner network; close ties to Microsoft 365, Power BI and Power Automate |
| Typical fit | Multi-entity, multi-currency or fast-growing companies that want one cloud system across finance and operations | Companies already standardized on Microsoft, or that need on-premises or partner-built industry solutions |
Neither is right for everyone. A single-entity distributor on Microsoft 365 may find Business Central the simpler fit. A software company opening subsidiaries in three countries may find NetSuite OneWorld fits the structure better. We have not included prices; both are quoted by the vendor or partner based on users, modules and edition, so get current quotes for your case.
What does migrating from QuickBooks involve?
1. Chart of accounts and dimensions
This is the most important design decision. QuickBooks charts often carry hundreds of accounts because they encode department or product in the account itself. In an ERP, keep the chart lean and move that detail into segments (NetSuite) or dimensions (Business Central). Map every old account to a new account plus dimension values, and have the controller sign off the mapping.
2. Historical data
Decide how much history moves. Common options:
- Opening balances only, with QuickBooks kept read-only for detail.
- Monthly trial balances for one or two prior years, so comparative reports work in the new system.
- Open transactions in detail: open invoices, open bills, open purchase and sales orders, and inventory on hand with costs.
Bringing every historical transaction across is rarely worth the effort and risk. Keep an archived copy of the old file and confirm your retention obligations.
3. Master data
Customers, vendors, items, employees and fixed assets need clean-up before they move: duplicates merged, inactive records dropped, payment terms and tax settings checked. Bad master data is a frequent source of problems after go-live.
4. Integrations
List every system that touches finance: CRM (HubSpot or Salesforce), billing and payments (Stripe, for example), payroll (Rippling, Gusto or ADP), expenses, banking, e-commerce and your data warehouse. For each, decide whether to use a vendor connector, an integration platform or a custom API integration. Test with real volumes.
5. Controls
Build these in from day one, not after the first audit:
- Roles with least privilege, and no shared logins.
- Approval workflows for purchases, bills, vendor bank detail changes and manual journals.
- Segregation of duties: the person who creates a vendor does not pay it.
- Period close and locking, so posted months cannot change silently.
- An audit trail kept on, and reviewed.
How to prepare for an ERP move
- Write down the pain. List the manual processes, reports and workarounds that prompted the move. They become the requirements and the test cases.
- Clean the books first. Reconcile every balance sheet account in QuickBooks before migration. Moving unreconciled balances moves the problem.
- Pick a go-live date at a period boundary. Month-end, or ideally quarter- or year-end, keeps reporting clean.
- Name an owner in finance. The implementation partner configures; your team decides and signs off.
- Plan a parallel close. Run at least one month in both systems, or rehearse the close in a sandbox, before switching off QuickBooks.
- Train by role. Accounts payable, sales operations and approvers need different training.
Our model is a 1–2 week discovery, then a phased build; a full platform go-live is typically about 90 days, depending on entities, integrations and data.
SOX-style controls: only when heading toward an IPO
The Sarbanes-Oxley Act (SOX) Section 404 requires public companies to report on internal control over financial reporting, and many also need their auditor's report on those controls. SEC rules give newly public companies a transition period, so the first management report is generally due with the second annual report (SEC Release 33-8760).
A private company with no IPO plans does not need full SOX documentation. The controls listed above are a sound base. When an IPO is a real plan, start well ahead of it: document processes, risks and key controls in the ERP so there is time to test them before the first report.
How this differs by company stage
- Startups: QuickBooks or Xero is usually right. Keep the chart clean and use classes or tracking categories so a later move is straightforward.
- Growing businesses: the move to NetSuite or Business Central usually happens here, when entities, inventory or investors arrive.
- Enterprises: a subsidiary may run NetSuite or Business Central while the group runs SAP or Oracle. Integration and consolidation become the main work.
See our platform implementation and modernization practice for how we run these projects.
Frequently asked questions
How long does a move from QuickBooks to NetSuite or Business Central take?
It depends on entities, integrations and data quality. A single-entity move with few integrations is quicker than a multi-entity one with inventory; a full go-live is typically about 90 days in our model.
Should we move from QuickBooks Desktop or Online first?
Move directly to the ERP. An intermediate step to QuickBooks Online adds a second migration without solving the underlying limits.
Can we keep QuickBooks for one subsidiary?
Yes, if you accept manual or integrated consolidation for that entity. It works for a small or dormant entity, but many companies bring all entities across once the ERP is stable.
Is NetSuite or Business Central better for SOX?
Both support roles, approvals, audit trails and period locks. SOX readiness depends on how you configure and document controls, not on the product.
Do we need an implementation partner?
Many companies do, because configuration choices made at the start are costly to change. Keep the design decisions, especially the chart of accounts and controls, with your finance team.