SAP Business One Version 11: 7 Readiness Checks
Key takeaways
- SAP has announced an initial partner preview of Version 11 for 2027, not a confirmed customer release date.
- SMEs should assess add-ons, integrations, data and recovery arrangements now.
- Web Client and infrastructure improvements do not need to wait for Version 11.
- A SAP Business One agency should provide evidence before recommending an upgrade, cloud migration or new add-on.
What Has SAP Actually Announced About Version 11?
SAP plans to open the first partner preview of SAP Business One Version 11 in 2027. The features announced so far include new cloud management tools for partners, containerised lifecycle management, native deployment on AWS, Microsoft Azure and Google Cloud, and storage integration with Google Drive and OneDrive. SAP also plans to keep developing the Web Client and to make more room for AI-based extensions. All of this comes from SAP’s current product announcement, though, and it isn’t a final specification. Several things are still missing: a confirmed general availability date, full system requirements, licensing terms and a compatibility list for third-party add-ons. That gap matters more than it might seem. Take a manufacturer with 40 SAP users, three production extensions and a custom warehouse interface. It can start documenting those dependencies today. What it can’t know yet is what a Version 11 upgrade will cost, or when its extensions will be certified. Booking a go-live weekend because “Version 11 is coming in 2027” gets things backwards. The smarter move is to gather the evidence now, so that once SAP and the add-on suppliers publish firm technical details, the decision almost makes itself.Can You Document Your Current SAP B1 Environment?
Start with a system inventory. It should record:- SAP Business One version and feature-package level
- Microsoft SQL or SAP HANA database
- Hosting model and server configuration
- Company databases and localisations
- Add-ons, custom code and user-defined objects
- Scheduled jobs, reports and integrations
- User numbers, roles and authentication methods
- Backup, recovery and support ownership
Are Your Add-Ons and Integrations Documented?
SAP Business One upgrades rarely go wrong because someone forgot about the standard sales order screen. The risk sits in everything connected to the ERP: banking, e-commerce, EDI, warehouse scanning, document management, production planning and custom reports. Build a compatibility register with these fields:- Add-on or interface name
- Current version
- Supplier and support contact
- Technical owner and business owner
- Database and Service Layer dependencies
- Renewal or maintenance status
- Business processes affected
- Supplier’s statement on Version 11
- Regression tests needed
Is Your Data Ready to Move?
A new version of SAP Business One won’t clean up your data. Duplicate customers, items nobody has sold in years and tax codes that don’t match all carry straight over. Migrate a mess and you get the same mess, just on newer software. Start with the basics: business partners, items, units of measure, warehouses, price lists, user-defined fields and inactive users. Before anyone deletes or archives old records, finance needs to confirm how long each type has to be kept. Imagine a company with 50,000 item records. Over the last three years, only 12,000 of them saw any activity. Deleting the remaining 38,000 might look like an easy win. Hold off. Some of those items could still be needed for a warranty claim, a tax audit, a service job or a year-end report. Before anything is removed, agree on the rules, get someone to approve the list and keep a note of what was taken out and why. Data cleanup deserves its own owner and its own timeline instead of being squeezed in alongside other work. And there’s no reason to wait for Version 11. Once the data improves, the reports you’re running today improve with it.Which Processes Should Move to the Web Client First?
SAP launched the Web Client in 2020 and has been adding to it ever since. Version 11 is expected to keep going in that direction. That still doesn’t mean everyone in your company should switch on day one. It’s safer to move one process at a time. A sales manager who mostly looks up customers, checks quotations and reviews dashboards is a good first candidate. A warehouse worker whose day depends on a specialist scanner workflow is a different case. They may still need an add-on or the desktop client for a while. Pick one role and one process that happens again and again. Write down what that person has to create, approve, change, print and report on. Then run the process with real transactions from your own business and note every step that’s missing or awkward. Ingold’s SAP Business One Web Client service covers consulting, setup, training and adjustments after go-live. If screen layouts, validation rules or automations need fine-tuning, Ingold also works with Boyum’s B1 Usability Package to close those gaps.Is Your Hosting and Recovery Model Ready?
SAP’s announcement includes cloud-management changes and support for major hyperscaler platforms. It does not establish that every Version 11 customer must move to the cloud. The current assessment should compare on-premise and managed-cloud operation against actual requirements:- Recovery time and acceptable data loss
- Security and authentication
- Internal administration capacity
- Remote access
- Performance at each location
- Maintenance responsibilities
- Predictability of operating costs
- Data-location and contractual requirements
Can You Test Without Putting Production at Risk?
A Version 11 plan will eventually require a representative test environment. A fresh but empty demonstration database is not enough. The test copy should contain realistic configuration, anonymised data where required, add-ons and connections to suitable non-production endpoints. The business then needs regression tests covering:- Order to cash
- Purchase to pay
- Inventory movements
- Production or warehouse processes
- Payments and financial posting
- Tax and compliance outputs
- Reports and document layouts
- E-commerce and other interfaces
- Roles, permissions and approvals
Who Owns the Decision?
ERP upgrades fail organisationally when every technical task has an assignee but nobody owns business acceptance. Assign an executive sponsor, project manager, technical lead, data owner and process owners for finance, sales, purchasing, inventory and any industry-specific workflows. Each owner should approve defined results rather than merely attend meetings. Use decision gates:- Current environment documented.
- Add-on suppliers contacted.
- Data issues assessed.
- Test and recovery arrangements agreed.
- Costs and dependencies recorded.
- Business tests completed.
- Rollback and go-live approved.
What Should a 90-Day Readiness Plan Include?
Days 1 to 30: Find out where you stand
List what’s in your system, keep a record of the faults that keep coming back and flag any components that are no longer supported. At the end of this stage you should have a clear report on how things stand today. Don’t let anyone turn it into a Version 11 sales proposal.Days 31 to 60: Test and clean up
Contact your add-on providers and ask about their plans. Run a database restore so you know your backups work. Check who owns each integration, and pilot one Web Client process that suits it. Pick a contained data set, such as duplicate supplier records, and clean it using rules everyone has agreed on.Days 61 to 90: Plan the next steps
Write down your upgrade options, give each task an owner and estimate the work you can already justify spending on. Keep confirmed requirements separate from assumptions that depend on SAP’s final release information. This plan doesn’t push you into an upgrade. It gives management the facts to wait, prepare or go ahead, with reasons that hold up when someone asks why.How Can Ingold Solutions Support Version 11 Readiness?
Ingold Solutions can assess the current SAP Business One environment, add-ons, interfaces, hosting and support arrangements. Its service coverage includes implementation, system health checks, upgrades, Web Client work, cloud hosting and partner change. For companies whose existing support arrangement has become part of the risk, Ingold also offers inventory analysis and system re-engineering as part of its partner-change service. A partner change should still be treated as a separate management decision, not presented as a prerequisite for Version 11 preparation. The immediate deliverable should be a short readiness report: findings, business impact, recommended actions, owners, dependencies and unresolved questions. That is more useful than a sales proposal built around an unconfirmed release date.A Version 11 readiness review should take the guesswork out of planning, not create a sense of panic. Ingold Solutions offers a free initial consultation to look at your current SAP Business One setup and scope a system health check. You’ll come away knowing what’s worth fixing now and what can wait until SAP confirms the release details.
Frequently Asked Questions
SAP has announced a first partner preview for 2027. It hasn’t given a date for general customer availability yet. You can start getting your current system in shape now, but treat any budget or go-live date as provisional until SAP publishes the final release, support and upgrade details.
No. There’s no generally available Version 11 to upgrade to yet. The better use of your time is to write down what you’re running today: your current version, add-ons, integrations, the state of your data and your backup and recovery setup. That cuts down the guesswork without locking you into a migration that starts too early.
That depends on the add-on, its version and the company that makes it. List every add-on in a compatibility register. Once suppliers have their Version 11 plans, ask each one to confirm in writing where they stand. Anything your business can’t run without should also be regression-tested in an environment that mirrors your real setup.
Not necessarily. SAP has announced new cloud management features and support for AWS, Microsoft Azure and Google Cloud, but nothing so far says every customer has to move to the cloud. Compare your options on security, recovery, performance, cost and how much administration your team can realistically handle.
It should cover your SAP version, database, infrastructure, company databases, localisations, users, add-ons, integrations, reports, data quality, security, backups and recovery. Every area needs an owner on the business side. The assessment should also separate the work you can start today from the decisions that have to wait for final Version 11 information.
Yes. Pick one role and test a clearly defined process in the current Web Client. Include the everyday work, plus the exceptions, approvals, reporting and printing. When something doesn’t work, write it down. Don’t assume every desktop workflow already has a Web Client equivalent.
Applicable for Package
Optional