QuickBooks Desktop End of Support 2026: What NNN Landlords Need to Know
If you've been running your NNN properties on QuickBooks Desktop, you already know the setup: QBD handles the general ledger, a spreadsheet handles the CAM reconciliation and recovery billing, and the combination more or less works. Until the accounting layer starts to erode.
Intuit ended service for QuickBooks Desktop 2023 in May 2026. That means no payroll updates, no bank feeds, no live technical support. Your software won't disappear from your hard drive — but the infrastructure that makes it functional has been going dark.
If you're still on QBD 2023, here's what NNN landlords specifically need to understand about what that means, and what to do about it.
---
What Changed with QuickBooks Desktop
Intuit has been moving customers off QBD for several years on a consistent sunset cycle: QBD 2021 services ended May 2024, QBD 2022 ended May 2025, and QBD 2023 followed the same pattern in May 2026.
"End of support" is not a forced uninstall. It means:
- Bank feeds stop working. Intuit no longer maintains the connections between QBD and financial institutions. You'll need to import transactions manually via CSV.
- Payroll updates require a subscription upgrade. Tax table updates won't come through for end-of-life versions.
- No security patches. Vulnerabilities discovered after the cutoff date won't be fixed.
- No live Intuit support for QBD 2023 issues after the service end date.
For a CPA managing general bookkeeping, this may be workable. For someone managing NNN properties — where bank feeds, recurring charges, and year-end CAM reconciliation all depend on the accounting layer being accurate and current — the erosion becomes a more material operational risk.
---
What NNN Landlords Have Been Doing with QBD
The typical NNN landlord accounting setup has been QBD as the general ledger, with a spreadsheet doing everything else: CAM tracking, tenant rent rolls, reconciliation calculations, recovery billing.
QBD works well enough as a general ledger. The problem is the gap between what QBD records and what NNN accounting actually requires. That gap is where most landlords spend their time — manually:
- Tracking which operating expenses are CAM-includable versus excluded under each lease
- Calculating each tenant's pro-rata share by square footage
- Reconciling estimated CAM payments against actual year-end costs
- Generating billing statements that document the calculation clearly enough to survive a tenant audit
QBD records the transactions. Your spreadsheet does the NNN accounting on top. That arrangement worked when QBD was stable and supported. When the bank feeds stop and security patches end, the entire stack becomes harder to maintain.
---
QuickBooks Online as the Migration Path — and Its Limits for NNN
Intuit's intended migration path from QBD is QuickBooks Online. For most property accounting uses, the migration is straightforward: QuickBooks Online maintains bank feeds, updates automatically, runs from any browser, and handles the GL functions QBD was handling.
For NNN workflows, the picture is more nuanced.
What QuickBooks Online handles well for NNN landlords:
- General ledger and expense categorization
- Bank feed reconciliation (this part works reliably in QuickBooks Online, unlike end-of-life QBD)
- Accounts receivable for base rent and CAM estimates
- Class and location tracking for multi-property portfolios
What QuickBooks Online doesn't solve on its own:
- CAM recovery calculation — pro-rata share by lease, not by accounting class
- Year-end reconciliation statements in a format tenants can actually audit
- CAM inclusion and exclusion logic based on individual lease definitions
- Gross-up provisions, CAM caps, and management fee exclusions
- A record of which tenants disputed a reconciliation and how it was resolved
QuickBooks Online is a general accounting platform. NNN property management lives one layer above the accounting platform — and that layer is where the complexity is.
---
Why the Migration Window Is Worth Acting On Now
Most NNN landlords on QBD 2023 didn't hit an immediate crisis at the May 31, 2026 cutoff. The service end is gradual, and you can keep using QBD after the end date — you just lose bank feeds and support. Some landlords will run on unsupported QBD for months.
But the migration forces a decision either way: whether to move the accounting layer alone (QBD to QuickBooks Online, same spreadsheet workflow above it), or whether to also evaluate the layer that handles NNN-specific work — the spreadsheet, the recovery billing, the lease tracking.
For landlords managing two to fifteen NNN properties, the spreadsheet layer is usually where the real friction lives. Year-end CAM reconciliation takes days. Tenant disputes are worked out through email threads with no centralized record. CAM inclusions get re-researched every cycle because lease exclusions were never documented when the lease was signed.
The QBD sunset is not a crisis — it's a natural evaluation point. If you're migrating your accounting layer anyway, the migration cost is already being paid. The question is just what you land on.
---
A Note on the Property Management Layer
When I moved from QBD to QuickBooks Online, I also looked at whether to keep the spreadsheet layer or replace it. That's actually what led me to build PigJet (pigjet.com) — a tool that runs on top of QuickBooks Online specifically for NNN and retail leases. The CAM reconciliation, recovery billing, and lease obligation tracking sit in PigJet; QuickBooks Online handles the accounting. The two stay in sync.
That's not the right call for every landlord. Some portfolios are simple enough that a well-built spreadsheet is fine. The point is: if you're migrating the accounting layer regardless, it costs nothing extra to evaluate whether your NNN tracking layer is also worth replacing. The migration overhead is the same either way.
---
Practical Steps If You're Still on QBD 2023
1. Check your version. Open QBD, go to Help → About QuickBooks. If you're on 2023, service ended in May 2026 — you're already running unsupported. If you're on 2021 or 2022, you've been unsupported since 2024 or 2025.
2. Take a full backup before migration. QBD stores data in .QBB files. Export a clean backup before any conversion — the QuickBooks Online migration tool is reliable, but you want the original file before any conversion runs.
3. Run the QuickBooks Online migration wizard. Intuit provides a direct migration pathway. Most NNN general ledger data transfers cleanly: chart of accounts, vendor history, customer records. Some payroll and class setup requires manual cleanup post-migration.
4. Verify bank feeds immediately after migration. Reconnect and confirm that your bank and credit card connections are active in QuickBooks Online. This is the main operational dependency that breaks in end-of-life QBD.
5. Decide on the NNN layer separately. Once QuickBooks Online is stable, evaluate whether your spreadsheet workflow is what you want to carry forward. That decision is separate from the accounting migration — but this is the moment to make it.
---
If you're still on QBD 2023, the May 2026 cutoff has already passed. The landlords who end up in trouble are the ones who keep delaying until bank feeds stop mid-cycle or until a year-end reconciliation deadline arrives while they're still mid-migration.
The accounting migration is largely mechanical. The more interesting question for 2026 is what you build on top of it.