Entity count
QuickBooks handles one company file well. Consolidation happens in a spreadsheet that is fine at two entities, fragile at four, and a genuine reporting risk at eight — unversioned, unaudited, and understood by one person.
By situation
Nobody wakes up unable to use QuickBooks. It degrades — the close adds a day a quarter, the consolidation spreadsheet gets one more tab, another person starts keying bills. By the time it is obviously a problem it has been one for eighteen months, and the fix is more urgent and more expensive than it needed to be.
What is your annual revenue?
The situation
Not revenue. These three compound, each gets worse on its own as you grow, and each is expensive to fix late.
QuickBooks handles one company file well. Consolidation happens in a spreadsheet that is fine at two entities, fragile at four, and a genuine reporting risk at eight — unversioned, unaudited, and understood by one person.
Five days is functioning. Fifteen means finance spends three quarters of the month reporting on the last one. It also degrades quietly, because nobody notices the month it went from eight to eleven.
It scales linearly with growth in a way almost nothing else in finance does. At 200 bills a month you are spending a full-time week on keying; at 600 you are hiring, and that hire gets booked as a growth cost rather than a systems cost.
Department or location P&L reconstructed in Excel every month means the dimensions were never captured. That is fixable at the point of entry and not fixable in the report.
For software and services companies this is usually the forcing event, and it arrives on somebody else’s deadline — a raise, an audit, or a sale.
The clearest test: could anyone other than your controller produce the consolidated statements if they were away for a fortnight? If not, the system is a person.
This is the part most vendors skip, and it resolves a meaningful share of cases. When we assess companies that believe they have outgrown QuickBooks, roughly half have a problem that does not require replacing the ledger at all.
Both are reversible, both are live in weeks, and both cost a fraction of a migration. If they resolve the pain, the ledger conversation postpones for a year or two, which is a better outcome than an unnecessary implementation.
Multi-entity consolidation with real intercompany elimination, ASC 606 revenue recognition with multiple performance obligations, and a fixed-asset subledger are the three things QuickBooks does not do and cannot be made to do from outside. If any of those is your binding constraint, the ledger has to change.
When it does, the shadow ledger means it is not a leap. A parallel ledger reconciles against your QuickBooks daily for months, so the cutover happens on a system that has already demonstrated it agrees with the books your CPA signed.
If you are on Desktop rather than Online, factor in that a conversion is roughly three times the elapsed work — no modern API, data in a file on a machine, and a decade of workarounds usually encoded in the class list. Start two quarters earlier than feels necessary, particularly if your version has an announced end-of-support date.
Where to start
A free assessment separates a workflow problem from a reporting problem from a genuine ledger constraint. About a third of these conclude you should change nothing structural.
AP automation or the reporting layer on top of QuickBooks. Reversible, no migration, and it resolves the pain outright for a large share of companies.
Costs a read-only connection. It accumulates proof while you decide, and turns any eventual migration into a switch rather than a leap.
We will not sell a cutover until three consecutive closed months have tied at zero variance. Plenty of customers never take that step and are well served anyway.
Questions
Three questions and a written answer, including the answer that says keep what you have.