We get some version of this question constantly: at what revenue or headcount should a business move off QuickBooks and into a real ERP. There is no clean number, and any vendor who gives you one is selling something. What actually predicts the right time is a specific set of operational symptoms, and once a business is living with two or three of them simultaneously, the workarounds have usually become more expensive, in real staff hours, than the ERP implementation everyone is dreading.
The symptom, not the size
A ten million dollar services business with one location and a simple product can run comfortably on QuickBooks Online for years. A two million dollar distributor with three warehouses and real inventory complexity can outgrow it in eighteen months. Revenue alone tells you almost nothing about ERP readiness. What tells you something is whether these specific symptoms are showing up in your actual operations.
Symptom one: the spreadsheet between systems
If your team maintains a spreadsheet that exists purely to reconcile what QuickBooks says against what your inventory system, your CRM, or your project tracker actually shows, that spreadsheet is doing the job an ERP's single database is designed to do automatically. The tell is not that the spreadsheet exists. Every business has some manual reconciliation. The tell is that someone updates it multiple times a week, and that people quietly do not fully trust either source without checking the other.
Symptom two: month end takes longer than it used to, not shorter
A close process should get faster as a team gets more practiced at it, all else being equal. If your month end close has been getting longer even as your finance team has gained experience, that is a strong signal the underlying systems, not the people, are the bottleneck. This usually shows up specifically around consolidating multiple entities, locations or revenue streams into one set of numbers, which is exactly the job a dimensional general ledger is built to do and a small business accounting system is not.
Symptom three: inventory numbers in the software and inventory on the shelf disagree
QuickBooks Online's inventory functionality is adequate for simple retail and thin for anything involving assemblies, multiple warehouses, or serialized tracking. If your team has started keeping a shadow inventory count somewhere else, in a spreadsheet or in someone's memory, because the software's number is not trusted, that is not a training problem. It is a signal the software has hit its actual functional ceiling for your business.
Symptom four: a customer facing promise your system cannot keep
This is the sharpest signal of the four. If a customer asks whether an order can ship by a specific date, and answering that question honestly requires a phone call to the warehouse rather than a lookup in your system, your order management and inventory are not actually connected in the way your business now needs them to be. This gap tends to appear suddenly as a company scales past a handful of large accounts who expect real answers, not estimates.
Symptom five: multi entity consolidation has become a real project every month
If you operate a US entity and a Canadian entity, or multiple entities for any reason, and consolidating them into one set of financials is a manual, spreadsheet driven project every single month rather than a report you can run, this is one of the clearest and most common triggers we see. Small business accounting software, on both sides of the border, is simply not built for real multi entity consolidation, and no amount of process discipline fixes that. It is an architecture limitation, not a training gap.
What actually happens when you move, realistically
An ERP implementation is a real project, typically measured in months rather than weeks, and it involves data migration, process redesign and staff training that a simple accounting software switch never requires. Budget for this honestly. NetSuite implementations commonly run into six figures and take one or more quarters. Sage Intacct, positioned as the step between QuickBooks and a full ERP, is a smaller project but still a considered purchase measured in months, typically through a partner, with licensing that runs into five figures annually before implementation costs.
Acumatica and Microsoft Dynamics 365 Business Central follow a similar pattern: real implementation projects, delivered through a partner network rather than self serve, with outcomes that vary enormously based on which partner you choose rather than which product you choose. This is a genuinely underappreciated fact across this entire category. The partner relationship often determines the outcome more than the software does.
The step between QuickBooks and a full ERP
Not every business showing these symptoms needs a full ERP like NetSuite or Acumatica immediately. Sage Intacct exists specifically for the company that has outgrown small business accounting software but does not yet need inventory, order management and manufacturing modules bundled into one system. Its dimensional general ledger, tagging transactions with department, location, project, customer or fund rather than a rigid chart of accounts, solves the multi entity consolidation and reporting symptoms directly, without the full scope and cost of a complete ERP. Companies whose symptoms are primarily financial rather than operational, more about closing the books than about inventory or order flow, often find this is the right sized step rather than jumping straight to a full ERP.
A short checklist before you start shopping
- Count your symptoms honestly. One of the five above is worth watching. Two or more happening at the same time is a real signal, not a coincidence.
- Separate financial complexity from operational complexity. If your pain is mostly about closing the books across entities, look at Sage Intacct before a full ERP. If your pain is mostly about inventory, order flow and warehouse operations, you likely need the fuller platform.
- Budget the implementation, not just the license. Every credible vendor in this tier is sold and implemented through a partner, and the partner's quality will affect your outcome more than the platform choice does. Ask for references in your specific industry and actually call them.
- Pick a quiet season to migrate. An ERP implementation during your busiest quarter compounds every risk in the project. Plan the cutover for a genuinely slow period if your business has one.
What we would actually do
Do not move because a peer company moved, or because QuickBooks feels like something you should have outgrown by now. Move when the specific symptoms above are costing real staff hours every month, hours that a properly implemented system would eliminate. Get a partner reference check from a business genuinely similar to yours in industry and size before you sign anything, because the platform you choose matters less than who implements it.
Nobody regrets moving to an ERP when the symptoms were real. Plenty of people regret moving when the symptom was actually impatience with QuickBooks looking unglamorous next to a shinier sales deck.