Companies do not decide to leave QuickBooks because of a feature. They decide because of a feeling, and the feeling arrives with the same four complaints every time. Someone is typing the same order into three systems. Inventory is a spreadsheet. Month-end takes longer every month. Nobody can answer a margin question without a week's notice.
Every vendor who hears those four will tell you it is time to move up, and for two of the four they are right. For the other two they are selling you a bigger ledger to carry a problem that has nothing to do with the ledger. This post takes the four signals one at a time, says which two mean leaving and which two do not, and gives you the test for each so you can tell before you sign anything.
An order arrives in the shop or the CRM. Someone types it into QuickBooks as an invoice. Someone types it into the shipping tool. When it ships, someone types the tracking number back. Multiply by orders per day and you have a job title.
This is the most common signal and it is the one that does not mean leaving. Re-entry is the absence of a join between the systems that hold the order, the invoice and the shipment, and QuickBooks has an interface that can receive invoices from the CRM and the shop directly. We have written about the three ways to connect a CRM to QuickBooks, and the same shape applies to the shop and the shipping tool.
The test: count the systems the order touches and count the people who type it. If the answer is three systems and two people, the fix is two joins, and it costs a fraction of a migration. Moving to an ERP does not remove the joins; it moves them, because the shop and the shipping tool are still outside the ERP and still need connecting. You would arrive at the new ledger with the same re-entry and a larger bill.
QuickBooks holds inventory in the sense that it has a quantity on hand and a cost per item. What it does not hold, in the editions most small companies run, is assemblies that consume components, multiple locations, lot or serial numbers, or a reorder logic that knows about lead times. So a company that makes things or stocks in more than one place ends up with the real inventory in a spreadsheet and a QuickBooks figure that is corrected at month-end.
This one is a genuine limit of the ledger, and it can mean leaving, with a qualification. The qualification is that the answer is not necessarily an ERP. An inventory system alongside the ledger, holding quantity and feeding value to QuickBooks, solves the spreadsheet for many light manufacturers and distributors for years. The day it stops solving it is the day the company needs the system to plan purchases from demand and a bill of materials, which is a planning function rather than a counting one.
The test: write down what the spreadsheet does that QuickBooks cannot. If the list is assemblies, locations and reorder points, an inventory system beside the ledger covers it. If the list includes planning what to buy from what is forecast, the ledger is becoming one module of something larger, and that is the leaving case.
The close used to take three days. It takes eight. Next year it will take twelve. This signal can go either way, and the way it goes depends on why the close is long.
If the close is long because the accountant is reconciling numbers that came from re-entry, or building the inventory figure from the spreadsheet, or costing jobs by hand, then the length is signals one, two and four wearing a different coat, and it shrinks when they are fixed. If the close is long because the company now has two or three entities and the consolidation is a spreadsheet, or because the transaction volume has made the file slow and the lists have hit their limits, then the ledger itself is the constraint, and that is the leaving case.
The test: ask the accountant to split the close into the hours spent reconciling what other systems should have posted, and the hours spent on what the ledger itself does slowly. The first number is joins. The second is the ledger. Most companies find the first number is three quarters of the close.
What did that job cost? Which product line makes money? Which customer is the one we should be losing? The owner asks and the answer takes a week, because the cost by job, product or customer does not exist in the ledger. It exists as a lump.
This signal does not mean leaving, and it is the one where a migration disappoints most. Margin by job needs material consumption, labour hours and an overhead rule captured and fed to the ledger, which is work that happens outside any ledger, and a new ledger without the feeds shows one lump instead of another. We have a separate piece on why the costs go missing on QuickBooks and the two feeds that put them back, and an inventory system beside the ledger is where the material feed usually comes from; the point here is that the fix is the feeds, and the feeds carry into any future ledger unchanged.
The test: ask whether the missing number is one the ledger could compute if it were given the inputs. If yes, build the inputs. If the missing number needs the ledger to do something it cannot, such as consolidating entities or recognising revenue on a schedule, that is a ledger limit.
Two of the four, re-entry and the margin question, are joins and feeds. They are the cheaper fix, they pay back in months, and they carry across into any ledger you later choose. Two of the four, inventory and the close, can be ledger limits, and the tests above tell you whether they are yet.
The order matters. Fix the two joins problems first, because they are cheap, because they make the close shorter, and because doing so gives you clean numbers to make the second decision with. Then apply the two tests. If both say the ledger is at its limit, you are leaving, and you leave with your joins already built and your job costs already known, which makes the migration smaller and the destination decision better informed. If neither does, you have three years before you ask again.
When the tests do say to leave, the destination question opens, and for most companies at this size it is a comparison between staying in the QuickBooks family at a higher tier, moving to a set of connected applications, or moving to a suite. We wrote the Zoho Books against QuickBooks comparison for the middle path, and the ERP or integration decision for the general one.
We run a no-risk discovery, a few days long, that applies the four tests to your actual business: we count the re-entry, read the inventory spreadsheet against the ledger, split the close with your accountant, and cost three jobs by hand. You get a written recommendation, and it is one of three: connect and stay, connect now and plan to leave on a date, or leave now. When the recommendation involves building anything, it comes with a guaranteed estimate. We are accountable for the recommendation being the right one for the numbers, not for the numbers pointing where a vendor would like.
Outgrowing QuickBooks arrives as four complaints. Re-entry and the margin question are joins problems, and a bigger ledger carries them with it. Inventory and the close can be ledger limits, and there is a test for each. Fix the two joins problems first, because they are cheap and they travel, then run the two tests. Most companies find they have not outgrown the ledger. They have outgrown running it alone.
In a no-risk discovery we follow an order from sale to shipment to invoice across your systems and show where it breaks and what one connected system would change. You pay only if you proceed. Or see how we approach it.
More on the same problem:
Commission Reconstruction: Why a Brokerage Runs on Four Systems, and What the Fourth One Costs. (article)
Zoho CRM Sales Signals Explained: Catch Every Buyer Moment (article)
The same four complaints arrive every time: someone types the same order into three systems, inventory lives in a spreadsheet, month-end takes longer every month, and nobody can answer a margin question without a week's notice. Only two of those can be limits of the ledger. Re-entry and the margin question are missing joins and feeds, and a bigger ledger carries them along. Inventory and the close have tests that tell you whether the ledger is actually the constraint.
No. Re-entry is the absence of a join between the systems that hold the order, the invoice and the shipment, and QuickBooks can receive invoices from a CRM or a shop directly. Count the systems the order touches and the people who type it; if the answer is three systems and two people, the fix is two joins at a fraction of a migration's cost. Moving to an ERP moves the joins rather than removing them, because the shop and shipping tool stay outside it.
When the business needs assemblies that consume components, multiple locations, lot or serial tracking, or reorder logic that knows about lead times, which the editions most small companies run do not hold. Even then the answer is not necessarily an ERP: an inventory system beside the ledger, holding quantity and feeding value to QuickBooks, solves it for years. The leaving case arrives when the system must plan purchases from forecast demand and a bill of materials.
Usually because the accountant is reconciling numbers that other systems should have posted: re-entered orders, an inventory figure rebuilt from a spreadsheet, jobs costed by hand. That part shrinks when the joins and feeds are fixed, and in most companies it is three quarters of the close. The close is a ledger limit only when the company has several entities consolidated in a spreadsheet, or the file has grown slow and the lists have hit their limits.
Fix the two joins problems first, re-entry and the missing margin inputs, because they are cheap, they make the close shorter, and they travel into any ledger you later choose. Then apply the two tests to inventory and the close. If both say the ledger is at its limit, you leave with your joins built and your job costs known, which makes the migration smaller. If neither does, the question can wait three years.
Three, broadly. Stay in the QuickBooks family at a higher tier, which suits companies whose constraint is file size or user count. Move to a set of connected applications, with a ledger, an inventory system and a CRM each owning its part and joins between them. Or move to a suite. The right choice follows the tests on inventory and the close rather than a vendor's pitch, and a discovery that costs three jobs by hand usually settles it.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
