A practical framework for CPA, CAS, and bookkeeping firms advising clients on the move beyond QuickBooks.
Most CPAs and advisors have the same conversation at least a few times a year. A client’s books are clean. The controller is competent. The team has built workarounds for every soft spot in their accounting system. And the business is still being held back by the software.
The client asks the CPA what to do. They expect a real recommendation, in plain language, from someone they trust. Most firms either hedge, because they don’t want to be wrong, or refer to an implementation partner they don’t fully trust. Both moves cost the firm reputational capital.
After enough QuickBooks-graduation stories across manufacturing, distribution, professional services, and nonprofits, the pattern is clear. The graduation moment is the highest-stakes referral a CPA makes. Most firms don’t have a system for it. They should.
Here’s the short version of the framework we use.
The three signs that matter most
QuickBooks complaints don’t always mean a client is ready for an ERP (Enterprise Resource Planning system). Plenty of “we’re outgrowing QuickBooks” conversations turn out to be a reporting workflow problem rather than a platform problem. The signals below sort the real graduation candidates from the ones who only need a fix.
1. Month-end is taking a week, and the controller is the bottleneck
When the close process consistently runs past five business days because one or two people are doing manual rollups, reconciling spreadsheets, and reformatting reports, the software is the gating factor. The controller can’t add capacity. The team can’t help. Software change is on the table.
2. Multi-entity rollups happen in Excel
Two or more legal entities, a parent company, an acquisition, even a sister company doing its own books, all consolidated through a tab-laden spreadsheet. This is the most common QuickBooks workaround we see, and the most consequential one to get past. Real multi-entity consolidation, with eliminations and currency translation handled by the system, is one of the strongest single arguments for moving to a real ERP.
3. More than one full-time person is “QuickBooks ops”
If the business has built itself a hidden FTE whose job is mostly making the accounting software work, the software is costing more than it saves. Move that person’s hours to higher-value work and the business case writes itself.
One signal means ask follow-up questions. Two means the conversation is real. Three plus a growth trajectory means the client is ready.
Where the Microsoft suite fits
When a client outgrows QuickBooks, the better question is usually not “Which ERP?” The better question is, “Where is the process breaking down?” Different Microsoft pieces fit different breaks.
Business Central fits clients who need real financial structure, inventory, multi-entity consolidation, project accounting, or approval workflows. Microsoft’s cloud ERP step up from QuickBooks. Strong integration with Outlook, Teams, and Power BI.
Power Platform fits when the pain is workflow, reporting, approvals, or repetitive manual work that does not need a new ERP yet. Power BI for dashboards. Power Apps for custom workflows. Power Automate for cross-system automation.
Dynamics 365 Sales fits when the front office is disconnected from finance and operations, and leadership cannot see pipeline or customer activity clearly.
Microsoft 365 and Teams form the collaboration layer around all of it.
Look at where the operational complexity sits. Size matters less than where the complexity lives.
For smaller clients headed to Business Central, our TruNova Launchpad offers a fixed-scope, fixed-fee, fixed-timeframe path with two delivery options: consultant-led or self-led. Same framework, different driver. See launchpad.trunova.ai for additional information.
The partner matters more than the platform
This is the lesson most CPAs learn after being burned once. A solid implementation on a “good enough” platform almost always beats a poor implementation on the “best” platform. Most of the ERP horror stories you’ve heard came from the partner. The product was usually fine.
When you’re vetting an implementation partner for a client, watch for these patterns:
- Salespeople you never see again after the contract is signed.
- “Customization” that turns out to be a workaround for a product gap.
- Implementation teams swapped out mid-project, often quietly.
- A “done” handoff where nothing actually works in production yet.
Before you make any referral, ask five questions. The answers should be specific and confident. Hesitation on any of them is a signal.
- Who specifically will do the work, and can I talk to them before signing?
- What is your methodology, and what happens at each phase gate?
- Show me three references in businesses that look like ours.
- What does post-go-live support look like, and what does it cost?
- What does “done” mean, and how do we know we got there?
If any answer is vague, keep looking.
Get the full framework
We packaged the longer version of this framework, including the full operational signals checklist, a side-by-side platform comparison, the partner-vetting patterns, and a one-page decision framework you can hand directly to a client, in a free guide for CPA firm leaders.
Download the CPA’s Guide to Recommending an ERP
27 pages. Free, no sales call required. Includes the readiness signals checklist, platform fit framework, partner-vetting questions, and a one-page decision framework you can hand a client.
If you have a client conversation coming up and want to compare notes before you make the referral, reach out at SalesTeam@TruNorthDynamics.com. We’ve been the partner in enough QuickBooks-graduation stories to have an opinion.
Michelle Serna
SVP Revenue, TruNorth Dynamics · Microsoft MVP for Business Central