Most companies don't outgrow QuickBooks in a single dramatic moment. There's no error message, no crash, no vendor letter. Instead, the system quietly stops covering the whole job, and your team fills the gap the way capable teams always do: with a spreadsheet. Then another one. Then a shared folder of them, each maintained by a different person, each holding a piece of the truth that your accounting system can't.
If you want an honest read on whether it's time to move to a real ERP, don't start with a vendor demo. Start with a census of your spreadsheets.
Run the census
Block an hour. Ask every department lead for a list of every recurring spreadsheet they maintain — anything updated weekly or monthly that someone else depends on. For each one, capture four things: who owns it, where the data comes from, what decision or document it produces, and what breaks if that person is out for two weeks.
You are not auditing anyone. Make that clear, or you'll get a sanitized list. These files exist because smart people solved a real problem with the tools they had. The goal is to see the shape of the gap they were filling.
Three kinds of spreadsheets
Once the list is in front of you, sort each file into one of three buckets:
- Analysis. Someone pulled clean data out of a system to model, forecast, or explore. This is healthy. Spreadsheets are excellent thinking tools and always will be.
- Bridge. Data is exported from one system, reshaped by hand, and imported or re-keyed into another. This is a warning. It means two systems that should talk don't, and a human is the integration layer.
- System of record. The spreadsheet holds information that exists nowhere else. Job costs, commission calculations, inventory counts, contract terms, project margins. This is the alarm.
The ratio tells you most of what you need to know. A handful of analysis files and one or two bridges is normal for a growing company. A folder full of systems of record means your financial system stopped being the source of truth a while ago, and nobody announced it.
The patterns that point to ERP, not a better report
Some gaps close with a well-built report or a single integration. Others don't, because they're structural. Four patterns tend to signal that you've genuinely outgrown a small-business accounting package:
Inventory and cost of goods gymnastics. If landed costs, work in process, assemblies, or multi-location stock live in spreadsheets, you're doing manufacturing or distribution accounting outside your accounting system. Your margins are estimates.
Project and job-level profitability. If you can tell me what the company earned last month but need a day to tell me which jobs made money, the structure for tracking revenue and cost against a project doesn't exist in your books.
Multi-entity and consolidation. Separate files per entity, manual intercompany eliminations, and a consolidation workbook that only one person understands is a well-known breaking point.
Order-to-cash handoffs. If a sale is entered in a CRM, re-entered into a fulfillment sheet, then re-entered again as an invoice, you're paying for the same data three times and inviting three chances to get it wrong.
What QuickBooks is still fine at
Be honest in the other direction too. Plenty of companies with real complexity run fine on QuickBooks because their volume is manageable and their processes are clean. If your census turns up two bridge spreadsheets and no systems of record, you may need an integration, a reporting layer, or a disciplined chart of accounts — not a year-long migration.
Replacing a working accounting system is expensive in money, attention, and organizational patience. The trigger shouldn't be revenue or headcount. It should be evidence that the work no longer fits the container.
Turn the census into a requirements list
Here's the part most companies skip. Every system-of-record spreadsheet is a completed requirements document that your team wrote for you, for free, over several years. It shows the exact fields they need, the calculations they actually use, the exceptions they handle, and the reports leadership asks for.
Rank those files by how much of the business depends on them and how fragile they are. The top three or four define phase one of an ERP rollout. The rest can wait, and some should never move — a good forecasting model belongs in a spreadsheet.
This also gives you the argument for the investment. Not "we need modern software," but "eleven critical processes run on files one person maintains, and here's what happens when they leave."
Where to go from here
If your census turns up more alarm bells than you expected, the next question is sequencing: what moves first, what gets integrated instead of replaced, and how you migrate without stalling the business for a quarter.
That's the work we do at Infraxio — Odoo and ERP implementations, systems integration, and the process design around them, led by people who have run operations, not just configured software. Send us your spreadsheet list and we'll tell you honestly whether you need a new system or a better connection between the ones you have.