SAP Business One Support and AMC in India: Your Options

I lead ERPNext and Frappe programmes at MithTech, a small senior AI-assisted team of Frappe specialists in Bengaluru. We support businesses on SAP Business One with the work around it, and we move the ones for whom B1 itself has become the problem. We are not an SAP partner and we sell no SAP licence. Most B1 support complaints we hear are about the work around B1, not about SAP.

How does SAP Business One support work?

Through your partner. SAP's support page says Business One is sold, implemented and supported through SAP's partner network, and customers raise support with their partner through the Launchpad. The partner works the case first; when it needs SAP, the partner takes it to SAP. You rarely talk to SAP directly.

What SAP lists for customers with a valid maintenance contract:

• Help around the clock for critical issues.
• One access point (the Launchpad) for cases, SAP Notes, knowledge base articles, licence keys and users.
• Proactive tools such as the Remote Support Platform, which watches database health.
• New versions and updates at no extra licence charge.
• At least five years of mainstream maintenance for each release family.

That is a solid base. What it is not is a team that writes your next report, fixes your print layout or connects B1 to your online store. That work sits with whoever you hire for it, often the same partner, on a separate bill or inside an AMC that mixes both.

What does the maintenance fee cover, and what doesn't it?

It covers the right to new versions and updates, SAP's support behind your partner, and the tools above. It does not cover the custom work your business added: queries, user-defined fields, layouts, add-ons from other vendors and integrations. SAP does not publish the maintenance percentage on its support pages, so we don't print one.

Before a renewal, ask your partner three things in writing:

1. What the maintenance fee is, as a percentage and an amount, and when it renews.
2. What else the AMC includes beyond SAP maintenance: hours, response times, which add-ons, which integrations.
3. What is billed on top: new reports, layout changes, upgrade work, user training.

Most AMC arguments come from point 2 being unwritten. A clear split turns "you said this was covered" into a list both sides can read.

One practical rule for custom work: change B1 through its supported tools, such as user-defined fields, the Query Generator, layout tools, the SDK and the Service Layer, not by writing to B1's database tables directly. Ask your partner what a direct database change would do to your support before anyone tries it.

Which SAP Business One versions are still maintained?

Only 10.0. SAP's maintenance page lists 10.0 in mainstream maintenance until 31 December 2028, marked "subject to change", with Version 11 to follow. Releases 8.8 to 9.3 are out of mainstream maintenance, and SAP says extended maintenance is not offered for Business One. So 9.3 users have an upgrade to plan.

Since 10.0, SAP ships updates as feature packs within the release. SAP's upgrade strategy document covers which older releases can upgrade straight to 10.0. Community threads from people who did it show the practical side: some went through an intermediate 10.0 feature pack first, and add-ons and changed database indexes were what slowed them down. Treat an old-release upgrade as a small project with a test copy, not a weekend job.

What is the work around B1, and who can do it?

The work around B1 is everything your business added on top of standard SAP: saved queries and reports, user-defined fields and tables, print layouts, approval procedures, third-party add-ons, and integrations with a store, a CRM, WhatsApp or a bank. It can be done by your partner or by an independent team that knows B1's tools.

The tools are SAP's own:

• Queries and reports. B1's Query Generator and Query Manager, plus SAP's reporting and layout tools.
• Fields and tables. User-defined fields and tables, added through B1, not in the database.
• Integrations. The Service Layer, a web API (REST and OData) available for both SAP HANA and Microsoft SQL Server from 10.0, or the older DI API in SAP's SDK.

Whoever does it, ask for the same habits: changes tested on a copy of your company first, each change written down, and nothing that touches B1's own tables directly.

That split is how we work on B1: the work around it and help for your users, while the licence, SAP support and upgrades stay with your reseller. We don't set up new B1 systems.

How do you change who supports your SAP Business One?

Customers can and do move to a new partner. We could not find a published customer step-by-step from SAP, so work from your own list: what you run, what you pay, and when it renews. Then ask the new partner and SAP how the transfer works for your contract.

A safe order:

1. List what you run: the B1 release and feature pack, add-ons and their vendors, integrations, saved queries and layouts.
2. Get your licence and maintenance status in writing, with the renewal date.
3. Talk to the new partner before that date, and confirm with SAP how your contract moves.
4. Collect the work around B1, such as query texts, layout files, add-on licences and integration settings, from the old partner.
5. Run both for a short handover, then switch the support line.

People on the SAP Community describe the usual trigger: licences and downloads sit under partner control, so when the partner stops responding, the customer is stuck. The common advice there is to try to sort it with the current partner first, then move.

When is moving off B1 the cheaper answer?

Only when B1 itself is the problem, not the support around it. If the system fits and the pain is slow reports or a missing integration, better support fixes it. If several companies or plants need one view, the renewal and the upgrade both fall due, and the work around B1 keeps growing, a move is worth costing.

The renewal and an old-release upgrade are the natural times to review. For an honest side-by-side, read ERPNext vs SAP Business One; for bigger groups, ERPNext for large enterprises. SAP Business One to ERPNext shows what moves, and the nine-plant case shows a group that went live on ERPNext in 11 weeks. The SAP to ERPNext guide walks the steps, and the ERP roundup covers the wider field. If you stay, what ERPNext support costs is a useful comparison for any AMC quote.

Skimmable summary: fix support problems with better support; only cost a move when B1 itself no longer fits and the renewal and upgrade both fall due.

Frequently asked questions