SAP put a date on the future. Most B1 owners missed it.
Buried in SAP's public product roadmap (the March 2026 edition, the one marked PUBLIC in big letters) is a sentence that should be on every Business One owner's planning calendar: "Version 11 to follow version 10 in 2027."
Not "someday." Not "under consideration." 2027. With the release train spelled out to get there: SP 2605, FP 2608, SP 2611, FP 2702, SP 2705, FP 2708, SP 2711, and the web client getting "accelerated delivery" through 2026 and 2027. (SAP Business One Road Map, March 2026)
I've been selling and implementing SAP Business One for over a decade (Vision33, SEIDOR, now running my own shop), and I can tell you exactly how roadmaps work: they're promises, and promises slip. SAP's own document says the planning "may be changed at any time." Fair. But this isn't a vague direction slide. It's a dated release train, and every car on it is browser-first. Yesterday I wrote about FP 2608's AI features; today is about what the schedule means for your business.
What Version 11 actually is (and isn't)
Here's what partners heard at the April 2026 APAC Partner Summit: Version 11 brings cloud-native deployment on hyperscalers with native cloud storage, expanded AI extensibility, and streamlined deployment and upgrades. And I want to be precise about SAP's official line, because it matters: "continued support and innovation for both Desktop and Web Clients." (Be One Solutions, APAC Partner Summit 2026)
Analysts reading the same roadmap add hyperscaler-native architecture (AWS, Azure), deep AI integration, and full backward compatibility: an evolution, not a rip-and-replace. SAP's Chief Partner Officer publicly reaffirmed B1's strategic importance in December 2025. Nobody is sunsetting your ERP. (Carlsquare, SAP Market Update Q1 2026)
And here's the quote from the top that frames everything. Rainer Zinow, SAP's head of midmarket product management, said in his annual review that his hope was for partners to do all customer-facing presentations in the web client exclusively: "the customer fully operates Business One through the browser." He also confirmed SAP had started gathering feedback on what goes into Version 11. (SEIDOR)
Read that again. SAP's product chief wants the demo, the thing designed to make you fall in love with the software, to happen entirely in a browser. That's not a feature decision. That's a verdict.
The honest tension: "both clients" vs. the release notes
Now the part where I earn my keep, because two things are true at once and most coverage only picks one.
SAP's official position: both clients continue, both get innovation. A partner broadcast from earlier this year put the field read more bluntly: "All new SAP Business One innovation is going into the Web Client. The desktop client will stay compliant. It will not get new features." (B1X, Ep. 8)
Both can be true. "Compliant" means it keeps working: security patches, legal updates, tax compliance. It does not mean it gets the good stuff. The release notes are the tiebreaker, and they've been voting browser for two years: FP 2602's Excel imports and ATP in the web client, FP 2605's Crystal Reports in the browser, FP 2608's Ask AI and banking workspace, all web-client-first. The desktop client isn't dying. It's being maintained. There's a difference, and your 2027 budget should know it.
The proof the browser already won (the features nobody talks about)
Everyone's quoting the AI headlines. Fine. I covered those yesterday. Here are the unglamorous releases that actually ended the desktop-client era, most of which your team never noticed:
Crystal Reports run in the browser now. Every Crystal report your partner built for the desktop client (same parameters, same filters) runs in the web client and emails straight from there. For a lot of companies, "but our custom reports" was the last excuse. It's gone. (FP 2602/2605 era, via Inecom's 2605 demo)
Multi-factor authentication everywhere. OTP-based login with Google Authenticator or any standard authenticator app, across the web client and the desktop client. If your auditor has been side-eyeing your B1 security, this one's free. (FP 2605)
Master data imports without the desktop client. Bulk Excel/CSV import of items, business partners, and serial and batch numbers, with column mapping, directly in the web client. Data administration was a desktop stronghold. Not anymore. (FP 2602/2605, via Be One Solutions)
Available-to-Promise in the browser. Committed stock, ordered stock, real availability (the number your sales team begs for before promising a ship date) now in the web client. (FP 2602)
Sales documents export with embedded XML. PDFs with structured XML inside, built for e-invoicing mandates and ERP-to-ERP integration. Boring? Extremely. Valuable? Ask anyone doing business in a country with e-invoicing rules. (FP 2602)
That same 2605 walkthrough put web client transaction coverage at roughly 90–95% of the desktop client. Ninety-five percent is not "the light version." It's the product.
What to do before 2027: the five-move checklist
1. Re-run your "we can't use the browser because ___" list. Write down every reason your company stayed on the desktop client. Then check each one against FP 2602, 2605, and 2608. I'd bet real money most of your list expired in the last eighteen months. Excuses have a shelf life. Check the date.
2. Audit your add-ons for web-client readiness. This is the real gatekeeper. Back in 2024 SAP shipped the UI API framework for the web client specifically so partners could bring desktop add-ons into the browser (SEIDOR), but "could" isn't "did." Ask your partner, add-on by add-on: does it run in the web client today? Get it in writing.
3. Know your release family. Here's one most owners miss: SAP ties maintenance to the version, not your contract: "the end of mainstream maintenance refers to the version and not to the overall product." Translation: know which release family you're on and what its runway looks like before you sign anything. (ERP Information)
4. Budget the testing, not the licenses. Same advice I gave yesterday, because it's the advice that saves careers: the software is the cheap part. The week your team spends proving everything still works after the upgrade is the real cost. Start that conversation now and 2027 won't ambush you.
5. Make the partner put the Version 11 path in writing. If you're buying or upgrading in the next twelve months, your statement of work should name the Version 11 upgrade path: what carries over, what gets re-tested, and what it costs. A partner who can't describe it hasn't been reading the roadmap. Find one who has. (I know a guy. The meeting link is below.)
The bottom line
SAP didn't announce the end of the desktop client. They didn't have to. They announced Version 11 in 2027, accelerated the browser for two straight years, and let the release notes do the talking.
SAP isn't killing the desktop client. They're just starving it. Version 11 is when the rest of us notice.
Move on your schedule, while testing is cheap and nobody's panicking, or move on SAP's, in 2027, with everyone else. I've watched a decade of ERP migrations. The first group always spends less.
Frequently asked questions
Is SAP discontinuing the SAP Business One desktop client?
No. And be suspicious of anyone who tells you otherwise. SAP's official roadmap position is continued support and innovation for both Desktop and Web Clients, and Version 11 (expected 2027) is an evolution of the product, not a replacement. What's true is that new features are landing browser-first, so the desktop client is increasingly the maintenance-mode option rather than the innovation option.
What is SAP Business One Version 11?
Version 11 is the next major release family after version 10, expected in 2027 per SAP's public roadmap. Partners briefed at the 2026 APAC Partner Summit describe cloud-native deployment on hyperscalers with native cloud storage, expanded AI extensibility, and streamlined deployment and upgrades, with backward compatibility preserved.
Can the web client really replace the desktop client now?
For most daily users, yes. As of FP 2605 the web client covers roughly 90–95% of desktop transactions, runs Crystal Reports, supports MFA, handles Excel master-data imports, and hosts the AI features. The exceptions are usually specific add-ons and deep customizations, which is why step 2 of the checklist is auditing your add-ons, not assuming.
We're on an old feature package. Should we upgrade now or wait for Version 11?
Don't sit on an old release for eighteen months hoping V11 solves everything. That's how companies end up doing a painful double-jump. If an upgrade is on your horizon, target a current feature package (2608 or later) so your team starts learning the web client now; that work transfers directly to Version 11 later.
