Switching Your SAP Business One Partner the Right Way
Switching your SAP Business One partner without downtime: contracts, notice periods, handover list, a four-week process and typical pitfalls.


Tickets stay open for days, small customizations take months, and with every problem you explain from scratch how your system is set up. At that point, the idea of a new SAP partner is obvious. Before you switch, raise the problems openly with your current partner. Many conflicts can be resolved once expectations and response times are put in writing.
If that does not help, a switch is not a big risk. Your database and your licenses belong to you, SAP does not have to approve, and the technical takeover usually takes two to four weeks. What matters are contract deadlines, a complete handover list and the discipline not to mix the switch with a redesign.
Who has which contract with whom
SAP Business One is sold exclusively through partners, and maintenance also always runs through a partner. This results in three contracts that you have to keep apart when switching.
| Contract | Contracting party | What happens when you switch |
|---|---|---|
| License, purchased | your company receives a perpetual right of use | remains in place, nothing to buy again |
| License, rented | subscription via partner or hoster | check term and notice period in the rental agreement |
| Maintenance | with the partner who manages it with SAP on your behalf | moves to the new partner, usually at the turn of the year |
| Consulting and support | with the partner, often as a framework or support contract | own notice period, often independent of maintenance |
| Hosting | with the hoster or partner | can stay if the new partner can work with the hoster |
| Third-party add-ons | depending on the vendor, directly or via the partner | clarify the license and maintenance path for each add-on |
There is one fixed point for maintenance: between SAP and the partner, the maintenance contract runs per calendar year and can be terminated with three months’ notice to the end of the year. SAP recommends that partners adopt this rule in their customer contracts. So check your contract by September at the latest. Important: a gap in maintenance saves nothing. If you rejoin later, SAP charges the fees retroactively.
Support and maintenance do not have to move on the same day. Many companies let the new partner take over support during the year and switch maintenance at the turn of the year.
The handover list
The new partner can find out a lot on their own if they have administrator access. It becomes faster and safer if you gather these items beforehand.
| Area | What you need | Why it matters |
|---|---|---|
| License | installation number, current license key, license overview | without a valid key, no update and no new users |
| Server and database | administrator access to server, database and SLD, version and Feature Package | the basis for every analysis and every emergency |
| Backup | where, how often, who tests the restore | the first question in case of a failure |
| Add-ons | list with vendor, version, license and maintenance path | add-ons are the most frequent blockers of upgrades |
| Custom developments | source code, documentation, rights to the code | without source code, no bug fixing and no upgrade |
| Validation rules | content of the Transaction Notification and other database procedures | they often contain business rules nobody remembers anymore |
| Data structure | user-defined fields, tables and objects with their purpose | the basis for reports and interfaces |
| Documents and reports | print layouts, Crystal Reports, saved queries | invoices and delivery notes must be right on day one |
| Interfaces | shop, shipping, bank, DATEV, EDI, with credentials and contact persons | errors show up here first |
| Open topics | ticket list, known bugs, planned projects | so that nothing happens twice or not at all |
When it comes to source code, it is worth looking at the old contract. If the partner developed extensions for you, the rights to them do not automatically pass to your company. How far your rights of use extend depends on the agreement and its purpose. If there is no clear rule, ask for the source code early and, if in doubt, have a lawyer check what you are entitled to. In a new contract, the handover of the source code should be explicitly included.
A four-week process
| When | What happens | Who acts |
|---|---|---|
| beforehand | talk with the current partner, check contracts and deadlines, decision | you |
| Week 1 | inventory: version, add-ons, custom developments, interfaces, backup | new partner with your key user |
| Week 2 | securing: confirm access, test critical processes, define the emergency path | new partner |
| Week 3 | handover of open tickets, familiarization with special cases, fixing the first errors | new partner, old partner where available |
| Week 4 | regular operation with committed response times, plan for the next improvements | new partner |
| at the turn of the year | maintenance with SAP moves, the license key comes from the new partner from then on | new partner |
The most important question in the first week is: what has to work reliably on the first day after the takeover? Usually that is document creation and printing, posting logic, payment transactions, interfaces to the shop and shipping, and user permissions. Everything else is sorted after that.
The most common pitfalls
First, missing documentation. Many customizations were implemented directly over the years without anyone recording why. That is normal. An experienced partner reads validation rules, queries and fields from the system and uses them to build the documentation that was missing.
Second, switching and redesigning at the same time. Anyone who reorganizes permissions, rebuilds reports, replaces add-ons and migrates to HANA during the switch turns a handover into a major project. Operational stability first, then improvement. One exception is an outdated release: according to SAP, versions up to 9.3 are no longer maintained, and for version 10.0 SAP currently states the end of 2028. If your system is below that, the upgrade belongs in the first months after the takeover, not in the first week.
Third, the wrong timing. A switch in the middle of year-end closing or shortly before a go-live is possible, but requires more coordination. A quiet quarter is better, and maintenance follows at the turn of the year.
Fourth, no clear responsibility in your own company. The new partner needs a contact person on your side who bundles information, prioritizes questions and makes decisions. Without this role, even a well-prepared takeover drags on.
What a switch costs
The takeover itself depends on the state of your system: a documented standard system with two add-ons is taken over faster than an environment that has grown over time with ten interfaces and custom developments without source code. A fixed price is only serious if the scope has been assessed beforehand. With us, ongoing support is available on a time-and-materials basis or as a support package from 620 EUR per month, with included hours and a committed response time; details are on the support page.
Maintenance paid to SAP does not change as a result of the switch; it depends on your licenses. Letting things carry on is usually more expensive than switching: documents are corrected by hand, reports are created in Excel, and employees stop reporting errors because nothing happens anyway.
How to recognize a good new partner
In the first conversation, a good partner asks about your critical processes, add-ons, custom developments and your internal contact person before talking about expansion stages. They name a concrete process, say what is not possible right away, and do not badmouth their predecessor. Which other criteria matter when choosing is described in which SAP partner is right for SMEs.
How we approach a takeover in concrete terms is described on the page about the partner switch.
Frequently asked questions
Does a partner change require SAP's approval?
Do the licenses belong to me or to the old partner?
What notice period applies to SAP maintenance?
How long does a partner change take?
What happens if the old partner does not cooperate?
Updated on November 11, 2026

