Moving Clients Off QuickBooks Desktop: A 2026 Migration Playbook for Bookkeepers and Firms

A solo business owner on QuickBooks Desktop has one file, one deadline, and one decision to make. A bookkeeping firm has eight clients on Desktop. Or fifteen. Or forty. Each one runs a different version and sits on a different support clock. Each has its own reason for never switching.

That's the real problem here. It isn't "how do I migrate a company file." It's "how do I run this migration eight, fifteen, or forty times without burning a quarter of billable hours." And it's how to do that without breaking something for a client who trusts your firm to handle it.

This is a playbook for that second problem. It's not a walkthrough for one file. It's a decision framework for a portfolio: which clients move now, which can wait, and which destination fits which client. It also covers how to build one repeatable process, instead of solving the same problem forty separate times. Most of what's published about "QuickBooks Desktop discontinued" is written for the business owner staring at one file. That content answers a real question, just not this one. A firm needs something different. It needs a way to sort a whole client list by urgency and complexity. Then it needs to pick the right destination for each segment, and run the process the same way every time. That way, quality doesn't depend on which bookkeeper happens to draw the file.

Is QuickBooks Desktop being discontinued, and what does it mean for a bookkeeping firm?

Not all at once, but yes for most versions. Intuit stopped selling new QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus, and Enhanced Payroll subscriptions in September 2024. Existing subscribers can keep renewing. QuickBooks Desktop 2022 already lost support on May 31, 2025. Desktop 2023 already lost support too, on May 31, 2026. Desktop 2024 is the last non-Enterprise version Intuit will ever release. Its support ends September 30, 2027. QuickBooks Desktop Enterprise is the one edition Intuit still sells, with no end date announced. For a firm, this means any client still on 2022 or 2023 is already running unsupported software. Clients on 2024 have more runway, but it's still a migration you'll manage on someone else's schedule.

Key Takeaways

• Desktop 2023 already lost support - May 31, 2026 has passed, so any client still on it is running unsupported software now and should move first.
• Desktop 2024 is the last version that will ever exist - support ends September 30, 2027, with no 2025, 2026, or 2027 edition coming.
• Enterprise didn't get the memo - it's the one Desktop edition Intuit still sells and supports, with prices up about 10% since February 2026.
• QBO isn't automatically right for every client - defaulting 20 clients onto the same plan can mean $27,600 a year in software spend your firm is implicitly recommending.
• Intuit's migration tool has real limits - it skips budgets, memorized reports, and full payroll history, and caps out around a 750,000-target company file within a 60-day window.
• The real risk isn't the software - it's running this migration forty times with no standard process, which is why a repeatable checklist beats any single tool choice.

What's Actually Ending (and What Isn't)

Intuit made three separate moves here. Clients and some bookkeepers mix them up. It's worth keeping them straight.

First, in September 2024, Intuit stopped selling new subscriptions of QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus, and Enhanced Payroll in the US. If a client already had one of these subscriptions, they could keep renewing it. This wasn't a shutdown. It was Intuit closing the front door to new buyers. The back door stayed open for people already inside. Intuit's own stop-sell FAQ covers the details if a client wants it in writing.

Renewing isn't the same as standing still on cost, either. Desktop renewal pricing has climbed alongside QBO pricing in recent years. A client who assumes "we can just keep paying for what we have" is often surprised by the actual invoice. That's a useful data point to bring into the conversation early. It removes the "why should we bother moving if we can just keep renewing" objection before it slows down your migration schedule.

It also helps to say plainly why Intuit is doing this. The company has been moving its accounting product line toward a cloud, subscription-first model for years. QuickBooks Desktop is the last major piece still running on the old install-it-locally model. Slowing new sales and letting each version age out on a fixed clock is how a vendor sunsets a legacy product line. It does that without pulling the plug on existing customers overnight. None of that changes what a firm needs to do. It just explains why the deadlines exist instead of getting extended again.

Second, each version has its own support sunset. They don't all land on the same day. Here's where each one stands:

"Support ends" doesn't mean the software stops opening. A client can still launch a Desktop file after its support date, enter transactions, and run reports. What actually stops: payroll tax tables freeze at whatever rates were current, bank feeds disconnect, and payment processing through QuickBooks (cards, ACH) stops working. Security patches stop shipping too, and Intuit tech support ends. For a client who runs payroll or takes card payments through QuickBooks, that's enough to force a move. The file technically still opens, but that's not enough. For a client who only uses Desktop to enter journal entries and print a P&L, it's a slower burn.

That distinction matters for how you sequence a firm-wide plan. Two clients can both be on Desktop 2023. Both are already past that May 2026 support date. But they still need completely different urgency. One runs payroll and card payments through QuickBooks. That client needs to move now, not on some future deadline, to stop the scramble that's already started. The other only uses it for internal reporting. That client could, in theory, limp along unsupported a while longer. Even so, that's not a position to leave a client in without a documented conversation about the risk.

Third, and this is the detail that surprises a lot of firm owners: 2024 is it. There will be no QuickBooks Desktop 2025, 2026, or 2027 (outside Enterprise). Intuit has stopped the annual release cycle for the standard product line entirely. Any client on 2024 today is running the final version that will ever exist for their edition.

The one exception across all of this is Enterprise. Intuit kept selling and supporting it with no announced end date. That makes it the one legitimate "stay put" option for clients with real reasons to avoid a migration. Enterprise isn't cheap, though, and it got more expensive: prices rose about 10% in February 2026. A 1-user Silver plan runs around $1,873 a year. Larger White or Gold tiers run up to roughly $6,598 a year. The Gold and Platinum tiers also add per-employee monthly fees on top. For a client with heavy inventory or job-costing needs, that cost can still be the cheaper option next to a messy migration. For a simple service business, it's a hard number to justify.

Losing support isn't only a security or payroll story either. Add-on integrations, expense-management tools, point-of-sale systems, and third-party payroll processors gradually stop maintaining compatibility with an unsupported Desktop version too. That failure is slower and quieter than a bank feed cutting off overnight. But it adds up to the same outcome: software fewer other tools want to talk to with each year that passes. For a firm, that shows up as a steady trickle of small breakages. A receipt-capture app stops syncing. A payroll integration throws errors nobody investigates until it's been broken for weeks.

If your firm also manages clients inside QuickBooks Online Accountant, that's a related but separate shift worth reading on its own: what's changing with QuickBooks Online Accountant.

Why "Just Move Everyone to QBO" Is the Wrong Default for a Firm

Intuit built one very good on-ramp: the Desktop-to-QBO export tool sits right inside the software, a few clicks from the Company menu. That convenience creates a default path. Convenient isn't the same as correct for every client on your book.

Here's the thing worth slowing down for: a forced migration is a rare, natural checkpoint. Most of these clients haven't reevaluated their accounting stack in years, maybe ever. They're on Desktop because that's what they started with. Or what a prior bookkeeper set up. Or what came bundled with an old computer purchase. The migration deadline gives you a legitimate reason to ask "does this client actually belong here." That beats just moving them to wherever the export button points.

Some clients genuinely fit QBO well: straightforward service businesses, single entity, a handful of bank accounts, nothing exotic in the chart of accounts. Others don't. A client with real inventory complexity might be better on Enterprise or a specialist stack built for their industry. A client who's growing fast and outgrowing rules-based categorization might fit better with an AI-native general ledger. That's often a better fit than another rules engine with a new interface. Weighing the full landscape of options, not just QBO versus Desktop? Our SaaS accounting software comparison breaks down the destinations by category.

The decision framework that actually holds up: match the destination to the client's complexity, growth trajectory, and how your firm wants to staff the work. Don't match it to whichever button Intuit put in front of the client first. For a firm managing many clients at once, that framework matters more than it does for a single business owner. You're making this call dozens of times, and a wrong default compounds across your whole book. Our guide to choosing bookkeeping software across multiple clients walks through that framework in more depth.

Run the cost math before you default anyone anywhere. QBO Plus at around $115 a month is roughly $1,380 a year, per client. Multiply that by twenty clients defaulted onto Plus because it's the "safe" choice. You're looking at $27,600 a year in client software spend your firm is implicitly recommending. That's on top of the migration hours themselves. Some of those clients need Plus. Others would do fine on Simple Start at $38 a month, or Essentials at $75. A few might be better served long-term by a tool that isn't billed by the seat and feature tier at all. The point isn't that QBO is overpriced. It's that "just put everyone on Plus" is an expensive default to get wrong twenty times over.

Think in archetypes instead of one blanket rule. A solo bookkeeper at their client ceiling, clicking through the same categorization work every morning, has a different problem. A five-partner CPA firm trying to scale advisory services without hiring more bookkeeping staff has a different one too. A brand-new business owner setting up their first set of books has a different problem than either of them. The migration deadline is the same for all three. The right destination usually isn't.

How you bring this up with a client matters as much as which tool you pick. Framing it as "Intuit is forcing us to move you" puts the client on the defensive. It makes every option feel like a downgrade. Framing it as "your support window is closing, and it's a good time to check whether your current setup still fits your business" opens a real conversation instead. Most clients don't have strong opinions about accounting software. They have opinions about surprises, unexpected costs, and being told what to do without being asked. Bring two options, not one. Explain the tradeoff in plain terms. Let the client make the call with you, not for them.

Triage Your Book: Which Clients Go Where

Before you touch a single company file, sort your book. Not every client needs the same destination. Sorting first saves you from migrating a client twice.

Sorting doesn't require a deep audit of every file up front. A few quick signals tell you most of what you need: does the client's file use the inventory module at all, and how heavily? How many months since the last full reconciliation? Is the client on one entity or several? Is the business under a year old, or does it have years of transaction history baked into ingrained habits? Ten minutes per client answering those questions is usually enough to place them in one of these buckets.

Use this as a starting sort, not a final answer for every client. A retail client with light inventory might still fit QBO Plus fine. A "simple" service business with three partners and messy draws might need cleanup before anything else. The point of the table is to stop treating "move everyone to QBO" as the default. Start asking the question client by client instead, with a short list of real options, not just one.

A practical way to spot the "messy books" row without opening every file: pull a quick trial balance. Scan for negative accounts receivable or payable. Look for credit card accounts that haven't been reconciled in six months or more. Check for an equity section that doesn't roll forward the way it should year over year. Any one of those is a flag. The client needs a cleanup engagement before a migration date gets scheduled, not after. Trying to migrate a file with those problems just carries them into the new system with a fresh coat of paint on top.

Client profiles shift, too. A simple service business today might add real inventory next year. A client who looked like an AI-native GL fit at signup might grow into job-costing complexity that argues for Enterprise later. Treat this table as something to revisit at each annual engagement renewal. Don't treat it as a one-time sort you run once during the migration push and never touch again.

Destination pricing (Intuit's published 2026 SMB pricing, hedged because it changes): QBO runs around $38 a month for Simple Start, $75 for Essentials, $115 for Plus, and $275 for Advanced. Xero runs roughly $29 to $80 a month depending on plan. FreshBooks runs about $22 to $68. Wave is free. Sage pricing varies by product line. None of these numbers should be the only factor in the decision. But they matter when you're pricing the client conversation.

What a Clean Per-Client Migration Involves

Once you know where a client is headed, the migration itself has a repeatable shape. Firms that treat each one as a one-off waste hours reinventing steps that should already be standard.

Start with cleanup, before you export anything. Duplicate vendors, uncategorized transactions, and unreconciled accounts don't get better in a new system. They just move. Clean the file first. Reconcile every bank and credit card account through the most recent statement. Resolve undeposited funds, and clear out any vendor or customer duplicates you can find. Check the aging reports too. Old, uncollected receivables and payables that should have been written off years ago will follow the client into the new system. They'll distort the first set of reports there too. A clean source file is the single biggest factor in whether a migration goes smoothly. It's also the step that's easiest to shortcut under deadline pressure, and the hardest to fix after the fact.

Know the constraints before you commit to a date. Intuit's built-in migration path runs from the Company menu: Export Company File to QuickBooks Online. Two constraints matter for planning. First, the company file's Total Target must be under 750,000 (press Ctrl+1 in Desktop to check). A file over that limit either has data problems on import, particularly with inventory, or can't convert at all. Second, you only have 60 days from the date you create the QBO account to complete the import. Miss that window and you're starting over.

Understand what the tool actually moves. It transfers the chart of accounts, customer and vendor lists, products and services, and up to two years of transaction history. It does not transfer budgets, memorized reports, some custom fields, journal-entry attachments, or complete payroll history. Inventory valuation methods can also shift during the move. None of this is a reason to avoid the tool. It's a reason to tell the client, in writing, exactly what won't carry over before they notice something's missing three weeks later. Build a short migration letter template once. List the items that don't transfer, and send it to every client before their cutover date. That single document heads off most of the "where did my old reports go" calls.

Document the chart-of-accounts mapping as you go, even when the export handles it automatically. Standardizing account structures across clients during this move is worth doing (see the mistakes section below). If you do, write down old account name to new account name for each client. Six months from now, a partner might ask why a number looks different than it used to. That mapping is the fastest way to answer without reopening the old file.

Validate before you call it done. After the import, don't just check that the software opened. Pull a trial balance in both systems and compare them. Check accounts receivable and accounts payable totals against the old file. Confirm every bank and credit card balance matches to the penny. Check that 1099 vendor flags carried over correctly and that sales tax settings match what the client actually charges. Both are easy to miss on import day and expensive to discover at year-end. This step catches the errors that Intuit's own migration disclaimers warn about. It's the difference between a migration that holds up and one that generates a cleanup project six months later.

Reconnect everything that lived on top of the old file. Bank feeds, payroll, and any connected apps (payment processors, expense tools, point-of-sale) need to be reestablished in the new system. Payroll re-setup in particular can take several business days if the client is moving payroll providers as part of this. Start that conversation early. Don't assume it happens automatically at cutover. This is the step firms forget most often. The file itself looks fine, and nobody checks whether the feeds are actually pulling data again. A bank transaction from two weeks ago can sit unnoticed for weeks.

Consider a parallel run for anything complex. For a client with real inventory, multi-entity structure, or payroll complexity, running both systems side by side for one full close cycle is worth the extra week. It catches discrepancies before the client's next tax return or lender report depends on the new numbers being right.

Check in again after the first full close in the new system. The real test isn't the day of import, it's the first month-end close afterward. Schedule a specific follow-up, thirty days out. Confirm the close went cleanly, and confirm nothing that passed initial validation quietly broke once a full month of real transactions ran through the new system.

Decide how you're billing this work before you start, too. Some firms fold migration into existing monthly fees as a value-add for long-term clients. Others price it as a fixed-fee project, separate from ongoing bookkeeping, scaled by file complexity instead of by the hour. A fixed quote is easier for a client to say yes to than an open-ended hourly estimate for work they don't fully understand. It also protects your firm's margin if a "simple" file turns out to need more cleanup than expected.

For a firm, the value here isn't any one of these steps. It's turning them into a checklist your whole team runs the same way every time. The alternative is a senior bookkeeper solving it fresh for each client while everyone else waits and asks questions. A written, repeatable migration checklist is worth building once and running forty times. For more on the broader automation side of running QuickBooks workflows day to day, see our QuickBooks automation hub.

The Migration Mistakes That Bite Firms Specifically

Some mistakes matter more at portfolio scale than they do for a single business owner migrating one file. These are the ones that show up again and again once a firm is running this across a real book of clients.

Dirty data, multiplied. One messy file is a cleanup project. Fifteen messy files, migrated on the same rushed timeline, is fifteen cleanup projects your firm didn't budget hours for. Say a firm schedules eight clients for the same migration week because their support dates all fall in the same window. Three of them turn out to have six months of unreconciled bank accounts. The whole batch slips, and the clean five clients end up waiting behind the messy three. Sort your book by data quality before you commit to dates. Push the messiest files to the back of the line, or handle cleanup as its own billed engagement first.

Chart of accounts drift across files. Different clients, especially ones set up years apart or by different bookkeepers, end up with inconsistent chart of accounts structures. One client might track "Office Supplies" and "Software Subscriptions" separately; another lumps everything into "Miscellaneous Expense." Migrating each one without a standard mapping means your reporting and staff training stay fragmented in the new system too. Any bookkeeper covering for a sick colleague has to relearn each client's quirks from scratch. Decide on a standard COA template before you start migrating. Map each client's old accounts to it during the move, not after.

Payroll history that quietly disappears. Complete payroll history doesn't transfer with Intuit's export tool. If your firm handles payroll for clients, export payroll reports separately and archive them before the cutover. Discovering this gap after year-end is a much worse conversation than catching it up front and having the archive ready. That's especially true when a client needs prior-year payroll detail for a loan application, a workers' comp audit, or a bank's due diligence request.

Cutover timing that ignores the client's calendar. Migrating a client mid-quarter, right before a loan renewal, or during their busiest sales season creates unnecessary risk. A retail client shouldn't get migrated the week before their holiday season starts. A client refinancing a loan shouldn't get migrated the month their lender is reviewing financials. Batch your migrations around each client's actual calendar, not just your firm's internal capacity to schedule the work.

Staff retraining treated as one-and-done. If your team has run QuickBooks Desktop for years, moving the whole book to a new system means retraining everyone, not just the person handling one client's file. It might mean several systems, not one, if you're using the triage table above. A junior bookkeeper who learns the new system on client twelve has absorbed eleven clients' worth of avoidable mistakes. Those mistakes come from struggling through clients one through eleven without guidance. Build the training into your rollout plan instead of discovering the gaps client by client.

Missing the 60-day window on a batch. This one is specific to firms managing volume. If you create QBO accounts for several clients at once to get ahead of a deadline, watch the clock. Cleanup or scheduling delays can push the actual import past 60 days. If that happens, you're starting over on all of them. That means re-exporting the Desktop file and redoing any prep work already done. Don't create the QBO account until you're genuinely ready to import within the window. Track each client's 60-day clock separately once you do.

None of these mistakes are exotic. They're the ordinary failure modes of running the same process many times without writing it down first. Naming them up front, before the first client gets scheduled, is cheaper than discovering each one live on somebody's actual books.

Where an AI-Native Layer Fits (and Where It Doesn't)

Here's where Growthy fits into this playbook, and where it honestly doesn't.

Growthy works in two modes. A migrating firm can use either one depending on the client. In the first mode, Growthy sits on top of a client's new QBO or Xero books as a workflow layer. There's no second migration. You connect the client's new QBO or Xero account, import bank statements, or upload a CSV. Growthy picks up the routine categorization work from there. Your team reviews and approves instead of clicking through every transaction by hand. This is the fit for clients who just landed on QBO or Xero through the Desktop migration and don't need to move again. It's also the lower-friction starting point for a firm that wants to pilot the tool on a handful of already-migrated clients. That pilot helps you decide whether standalone Mode 2 makes sense for anyone else on the book.

In the second mode, Growthy is the standalone book of record instead of QBO or Xero. This fits differently: a new client with no existing Desktop habits to unwind, or a firm deliberately building a modern stack. That firm doesn't want to migrate into another rules-based ledger it'll want to leave again in a few years. If a client is starting fresh anyway, it's worth asking whether QBO or Xero is really the destination, or just the default. We wrote more about that decision in why to start on an AI-native GL instead of QuickBooks. Firms rebuilding the whole practice around AI, not just the books, can look at TracePrep, an AI-first operating system built inside a working CPA firm.

The honest number: Growthy is about 85% accurate on first import. You review the rest. That's not a claim of finished work. It's a starting point. The transactions it's least sure about get flagged for your team instead of guessed at. In practice that looks like a triage list, not a blank inbox. Out of, say, 247 transactions in a month, maybe 13 need a human look. The rest are already sorted and waiting for approval. On returning clients, after 30 days of learning that client's specific patterns, accuracy climbs toward 90%-plus. Both numbers matter for a different reason. 85% tells you what to expect on day one with a new client's file. The returning-client number tells you why sticking with one system pays off, instead of migrating again in two years. Every correction your team makes on a client's file gets remembered for that client specifically. The same vendor doesn't get miscategorized twice.

The categories that trip up every categorization tool, not just Growthy, are worth naming plainly. Net-versus-gross deposits: a Stripe or PayPal payout posts as one lump sum. The fee needs to land in the right account instead of getting buried in revenue. Transfers: loans, owner draws, and account-to-account transfers all look similar on a bank feed. A wrong guess here misstates the balance sheet even when the P&L looks fine. No-description transactions: an ACH line that just reads a reference number with no vendor name attached. Growthy's approach on all three is the same: flag it for a human instead of guessing wrong with confidence. That's a deliberate tradeoff, not a limitation we're hiding.

For firm work specifically, the architecture matters as much as the accuracy number. A tool that's built to be the book of record, instead of a categorization layer sitting on top of one, is a different kind of system. It applies consistent categorization logic the same way every time, and it keeps a clear trail of what changed and when. That matters for anything that eventually gets audited, whether that's a lender review, a tax return, or a client asking "why does this number look different than last month." The double-work problem is real, but it's specific. A tool that sits on top of QBO or Xero and keeps its work in a separate system, or in a spreadsheet, is doing double work by design. A workflow layer that syncs its categorization directly into the client's QBO or Xero books, the way Growthy's first mode does, doesn't have that problem. There's no second system to keep aligned. A tool built as the standalone book of record from the start doesn't have that second system either.

Where Growthy isn't the fit: clients with heavy manufacturing operations, complex job-costing, or serious inventory valuation needs. Those clients are better served by QuickBooks Enterprise or an industry-specific stack built for that complexity. We're not the right tool for every client on your book. Pretending otherwise would just create a different migration problem down the line. If you're comparing Growthy against fully-managed bookkeeping services like Bench or Pilot, instead of against QuickBooks itself, that's a different comparison. It's worth reading separately: AI bookkeeping versus Bench and Pilot.

There's a firm-level reason this matters beyond any single client's file, too. A firm that standardizes on one modern system gets easier to staff and easier to hand off between bookkeepers. That beats forty different one-off tool choices made client by client over the years. A new hire learns one process instead of relearning quirks per client. And a client's books don't live in a system only one person on the team actually understands.

Your Next 12 Months: A Firm Migration Timeline

Given where the deadlines actually stand right now, the sequence for a firm looks like this over the rest of 2026 and into 2027.

Now (mid-2026): audit the book, and move the overdue clients first. List every client on QuickBooks Desktop, which version they're running, and what they actually use it for (payroll, card payments, bank feeds, or just data entry). This single list tells you which clients are on a real clock and which have more room. Desktop 2023's May 31, 2026 support date has already passed. Any client still on that version is running unsupported software right now. Put those clients at the front of the line, not the back.

Second half of 2026: triage, clean up, pilot, and migrate the overdue clients. Sort the rest of your book against the table above. This is a planning exercise, not a migration, and it's the step that prevents the "move everyone to QBO" default from taking over by inertia. Flag the messy files that need cleanup as their own line item, separate from the migration itself. Pilot the full process, cleanup through validation, on one or two of your simplest clients first. Use that pilot to fix the steps that don't work in practice before you run them under deadline pressure on forty files. Then run the overdue Desktop 2023 migrations through that same checklist. They shouldn't wait for a slower quarter.

2027: work through Desktop 2024 on a calendar spread. Desktop 2024 support ends September 30, 2027. Spread those migrations across the year instead of cramming them into the weeks right before the deadline. Build the schedule around each client's fiscal calendar, not just your firm's capacity.

Ongoing: train staff once, on the standard path. Once your checklist and destination framework are set, train your whole team on it together. Don't let each bookkeeper improvise their own process client by client. This is the step that turns a one-time migration project into a repeatable skill your firm keeps. That skill stays useful the next time a vendor sunsets a product your book depends on.

If your firm is managing this across a real book of QBO or Xero clients once the migrations land, see how Growthy fits firms specifically at Growthy for bookkeepers.

Frequently Asked Questions

Is QuickBooks Desktop going away in 2026?

Not entirely. Pro Plus, Premier Plus, Mac Plus, and Enhanced Payroll stopped taking new subscribers in September 2024. Desktop 2023 already lost support, on May 31, 2026. Existing renewals continue for now, and Desktop 2024 stays supported through September 2027. Enterprise keeps going with no announced end date. For most firms, 2026 was the year Desktop 2023 clients needed a plan. Desktop itself didn't disappear entirely, but that plan is now overdue for anyone who hasn't moved yet. The version number determines a client's actual deadline. The first step for any firm is confirming which version each client is actually running, instead of assuming they're all in the same boat.

When does QuickBooks Desktop support end?

It depends on the version. Desktop 2022 already lost support on May 31, 2025. Desktop 2023 already lost support too, on May 31, 2026. Desktop 2024, the last version Intuit will ever release outside Enterprise, loses support September 30, 2027. Enterprise has no announced end date.

Will QuickBooks Desktop stop working after support ends?

The software still opens. A client can still enter transactions and run reports locally after the support date passes. What actually stops: payroll tax tables freeze, bank feeds disconnect, payment processing through QuickBooks stops working, security patches stop shipping, and Intuit's tech support ends. For most active businesses, that combination is enough to force a move even though the file technically still opens. Third-party add-ons and integrations also tend to drop compatibility with an unsupported version over time. That's a slower failure than a bank feed cutting off. But it adds up the same way.

Should a bookkeeping firm move every client to QuickBooks Online?

No. QBO is the destination Intuit's built-in migration tool defaults to. That makes it the easiest path, not automatically the right one for every client. Some clients fit QBO well. Others are better served by Xero, an AI-native GL, or Enterprise if inventory and job-costing get complex. Treat the forced migration as a chance to match each client to the right tool instead of the default one. Run the cost math per client before assuming the higher-tier plan is the safe choice.

What's the best QuickBooks Desktop alternative for a firm managing multiple clients?

There isn't a single answer, because a portfolio of clients rarely fits one tool. QBO and Xero work well for straightforward service businesses. Enterprise or a specialist industry stack fits inventory-heavy or job-costing clients. An AI-native GL fits new clients starting fresh. It also fits clients where the firm wants a modern book of record, instead of another layer sitting on top of an old one. Ask what the client will actually do with the software day to day before picking a destination. A tool chosen for its feature list instead of the client's actual workflow tends to become another migration project in a couple of years.

How long does it take to migrate a whole book of clients?

It depends heavily on client count and data cleanliness, but batching helps a lot. One clean file might migrate in an afternoon. A firm with twenty clients, some clean and some messy, is realistically looking at a few months. That's the timeline if each one is handled one-off with no standard process. A repeatable checklist cuts that time significantly, because you stop reinventing the steps for every single client. Piloting the process on one or two clients before batching the rest also shortens the total timeline. It catches process problems before they repeat across the whole book.

Can we keep some clients on Desktop (or Enterprise)?

Yes. Enterprise stays supported with no announced end date. Clients with heavy inventory, manufacturing, or job-costing needs can reasonably stay there. Clients on 2023 or 2024 can also keep running past their support date, since the software still opens; it just becomes unsupported. Whether that's acceptable depends on the client's reliance on payroll, bank feeds, or payment processing through QuickBooks. It also depends on their tolerance for running unpatched software. Keep in mind that "unsupported" isn't a fixed risk level. Fewer workarounds exist the longer a client stays on an unsupported version. And Intuit's support team won't help troubleshoot problems on it. Build that into the conversation with any client who wants to stay put. Don't treat it as a one-time decision.

Does Intuit's free migration tool transfer everything?

No. It moves the chart of accounts, customer and vendor lists, products and services, and up to two years of transaction history. It does not move budgets, memorized reports, some custom fields, journal-entry attachments, or complete payroll history. Inventory valuation methods can also change during the move. That's worth checking closely on any client carrying inventory. Two other constraints matter for planning. The company file has to stay under a 750,000 Total Target to convert cleanly. And the import has to happen within 60 days of creating the QuickBooks Online account.

What happens to payroll history during migration?

Complete payroll history doesn't come across with Intuit's export tool. Firms that handle payroll for clients typically need to export payroll reports separately before migrating. Keep them as a standalone reference. QuickBooks Online won't display the client's full payroll history from before the cutover.

Do we need a CPA to manage client migrations?

Not for most straightforward migrations. A bookkeeper or firm can run the process directly: cleanup, export, validate, reconnect. Where a CPA tends to get pulled in is compliance-sensitive cleanup, multi-year reconciliation gaps, or clients who specifically want a fully managed migration. That means end to end, instead of run by their bookkeeping team. That's a client-preference question as much as a technical one; plenty of straightforward files never need CPA involvement at all. SDO CPA's walkthrough for a single business's managed migration is a useful reference if a client asks for that kind of service instead of a firm-run one.

Once your clients land on their new destination, whether that's QBO, Xero, or a standalone AI-native GL, the daily categorization work doesn't disappear. That's where a workflow layer earns its keep.

Growthy is in open alpha: AI bookkeeping built for firms managing a book of clients. It categorizes the routine work automatically so your team reviews and approves instead of clicking through every transaction. Get Early Access.