// article
QuickBooks rarely fails loudly. It fails quietly: in the spreadsheet someone built to consolidate two companies, in the "don't touch that item list" rule everyone learned the hard way, in a month-end close that takes nine days and one person's entire sanity. If you are reading this, something already feels tight. The useful question is whether you are looking at a preference problem (annoying, survivable) or a structural one (no add-on fixes it).
Here are the seven signs we treat as structural, plus an honest note on which ones, alone, do not justify an ERP project.
The moment a second legal entity appears, whether a new state, a holding company, or an acquisition, QuickBooks turns month-end into export-and-merge work. Intercompany balances are eliminated by hand, and every consolidated number exists only in a spreadsheet someone maintains. In an ERP like Dynamics 365 Business Central, companies live in one environment and consolidation is a posting routine, not a weekend.
QuickBooks tracks items. It does not run warehouses. If you need bins and zones, lot or serial tracking for recalls and warranties, real costing methods, or barcode-driven picking, you are past what item lists were built for, and the add-on stack you have likely bolted on is its own monthly bill and its own point of failure.
Approval workflows on purchases and payments. Role-based permissions that actually segregate duties. A change log that shows who touched what. These are the requirements that show up with your first audit, your first covenant-heavy loan, or your first fraud scare. They are also the place where growing companies discover QuickBooks was designed for trust, not control.
If profitability by location, project, or product line lives in Excel and is rebuilt monthly from exports, the ledger is no longer your reporting system; the spreadsheet is. ERPs tag every transaction with dimensions (department, project, location, anything you define), so those reports are queries, not projects. Power BI reads them natively.
Orders from e-commerce typed in by hand. EDI documents processed through email and CSV. Shipping confirmations that someone copies back into the system. Every manual hop is an error rate and a headcount cost, and the duct-tape connectors that promise to fix it tend to drop the orders you needed most. (We wrote about what designed-for-failure integrations look like on our integrations page.)
A close that runs past five business days is usually not a people problem. It is reconciliation across systems that do not talk, manual accruals, and the consolidation spreadsheet from sign #1. Companies that move to a mid-market ERP typically buy back most of that week, not because anyone works faster, but because the work disappears.
If you are on QuickBooks Desktop, the calendar is now part of the decision: Intuit stopped selling new Pro and Premier subscriptions to new US customers in September 2024, and the 2023 edition lost payroll, payments, bank feeds, and security updates on May 31, 2026 under Intuit's service-discontinuation policy. Running unsupported financial software is a risk decision, not a software preference. We covered the full timeline, and what a migration actually involves, in When to Switch from QuickBooks to Business Central.
If two or more signs describe your company, get a real answer instead of a sales pitch: our fixed-fee QuickBooks-to-Business-Central Migration Assessment reviews your current state, maps exactly which data would move, and ends with a fixed-price proposal in writing, with numbers you can take to your leadership team, from a pricing structure we publish openly. A senior team member replies within one business day.