ERP replacement. SAP Business One
Leaving SAP Business One for a cloud system your company owns
In short
- Black Badger Software Solutions is a custom software company in Clearwater, Florida that replaces SAP Business One, ledger included when the accounting is ordinary, with a cloud system your company owns outright.
- We were never a SAP Business One partner and we have no SAP Business One engagement on record, so nothing rides for us on which way you go, and we do not configure, patch or administer SAP Business One for anyone.
- Leaving means master data and transactions come out of the company database through the Service Layer, the DI API or read-only queries, the user-defined fields, tables, formatted searches and stored-procedure checks get read for the rules they hold, and Business One stays live until a closed period reconciles on both sides.
- The two replacements we publish outcomes for went live in six weeks and in sixteen weeks, and the runway for yours goes in the written scope once we have seen your data.
- After launch the system costs roughly $100 to $200 a month to run for a smaller company, and $2,000 to $3,000 a month at enterprise scale. Those are hosting and service bills you pay the providers directly, with no license and no per-user fee.
SAP Business One is SAP's ERP for small and mid-sized companies. Accounting, sales, purchasing, inventory, production and service in one package, running on Microsoft SQL Server or SAP HANA, installed on a company's own servers or hosted by the firm that sold it. It's sold, implemented and upgraded through SAP's channel of independent firms, never by SAP directly to you. We were never a SAP Business One partner, so nothing rides for us on which way you go.
Plenty of companies outgrow it without ever deciding to. Volume rises, a second entity arrives, the warehouse gets more complicated, and the answer each time is another add-on, another user-defined table or another query somebody wrote years ago. The system still closes the books. The operation around it ends up living in add-ons, exports and spreadsheets, on servers someone has to keep patched.
Where we stand
Do you implement or support SAP Business One?
No. We were never a SAP Business One partner, we have no SAP Business One engagement on record, and we will not pretend otherwise. What we bring is the build side, the system your operations and finance would move into, and a plain read of what your Business One install actually does.
We were partners of other platforms, monday.com, Smartsheet, Wrike and Zoho among them, and we ended those partnerships to build replacements. So the SAP Business One work we take is replacing it, usually all of it, with a system on cloud hosting and database accounts in your name. We build in the cloud only. If your Business One runs on your own servers or in a hosted environment, the replacement is also the move to the cloud, and we never install or host anything on site. We do not run upgrades, write add-ons or take a support retainer for Business One.
Where it fits
Where does SAP Business One fit?
We sell no SAP Business One licenses and take no referral fees, so this is not a hit piece. These are the cases where keeping it is the honest advice, and if yours is one of them, we will say so on the call.
A single-entity company with ordinary accounting and a standard distribution or light manufacturing flow. Business One covers that without much bending, and the people who know it are easy to find.
A business whose lenders, auditors or parent company expect a recognized SAP product as the book of record. The name on the platform is part of the answer there.
A company already running it whose finance team is happy and whose operations fit the standard documents. If the ledger and the core flow are doing their job, fix what sits beside them. That's a smaller project than a replacement and often the honest advice.
A subsidiary whose group runs larger SAP systems and wants the reporting lines to match. Fitting into the group's standards can matter more than anything a custom system offers.
Where it breaks
Where does SAP Business One break down?
The failure modes below are the ones that show up again and again as a company grows.
Each company is its own database. A group with several entities consolidates outside Business One or adds an add-on to do it, and intercompany transactions get keyed twice or synced by something else. Growth by acquisition makes that worse every time.
Customization piles up in layers nobody documents. User-defined fields and tables, formatted searches, saved queries, approval procedures, and validation written into a SQL stored procedure that fires on every transaction. Each one made sense when it was added, and together they're a rulebook only the person who wrote them can read.
Anything past the standard documents means an add-on built on the SDK. Those come from separate vendors with their own licenses and their own release schedules, so a version upgrade waits until every add-on you run supports the new version, and the firm that sold it is usually the only one who knows how they fit together.
Licensing is named users by license type, with annual maintenance on top, bought through the firm that sold it. People outside the company, like customers checking an order or a subcontractor logging work, don't fit that model without a separate portal or another product.
Many installs run on the company's own Windows servers or in a hosted environment the company doesn't control. Someone has to patch the server, the database and the client, back it up and keep remote access working, and in a hosted setup the company often doesn't hold the database credentials for its own data.
Reporting outside the built-in documents and Crystal layouts means SQL. The questions an operations leader asks every day (what's late, which jobs are losing money, what's stuck in approval) get answered by a query someone wrote, exported to a spreadsheet. That's how a company ends up running an ERP and a shadow system at once.
The replacement
What does replacing SAP Business One look like?
For most Business One companies this is a full replacement, ledger included. The accounting is usually ordinary, one entity or a few, one currency or a handful, and a new system can carry the general ledger, receivables, payables, inventory and orders together. Where several entities have to consolidate on a statutory calendar, or an auditor expects the ledger to stay where it is, we say so, and the operational layer gets replaced around it, posting back through the Service Layer.
Either way the new system takes the shape of your operation. The records are your orders, items, jobs, sites and crews with real relationships between them, and the pricing, approval and validation rules that lived in user-defined fields, formatted searches and a stored procedure become tested, versioned code. Reporting reads live data, so a manager's daily question is a screen, not a query and an export.
It runs in the cloud, on hosting and database accounts in your company's name. No server room, no Windows patching, no remote desktop into a hosted box. If Business One sits on your own servers today, retiring them is part of the project, and we don't put anything back on site.
You own the result. Code in a repository in your name, unlimited users including customers and subcontractors, and no license types or add-on renewals. We're added as administrators so we can build it and support it, and you can remove us whenever you want.
The stakes
What does it cost to get this wrong?
More than the software. A replacement that goes badly costs you the one thing the old system was still doing, a single place your team agrees on. The failures below each turn a rebuild into a year of parallel systems, so they are the ones we plan around.
Journal entries are the record and the documents produce them. Pull invoices without the journal lines behind them, or skip the period, posting date and currency on each line, and the figures won't tie to a closed period. Finance won't sign anything off on numbers like that.
User-defined fields and tables hold business rules disguised as data. Migrate the standard tables, drop the U_ columns and the @ tables, and you've lost the approval flags, custom statuses and pricing exceptions the business has been running on, often without anyone noticing until a customer does.
The validation in the stored procedure stops bad transactions before they post. Leave it out of the new rules and the first month runs on data Business One would have rejected, and that data gets reconciled by hand afterward.
The order of work
What happens, in what order, when you leave SAP Business One?
Each step exists because skipping it is how the previous attempt failed. The sequence is fixed. The runway is not, and it goes in your written scope once we know the shape of your data rather than on this page as a calendar promise.
- 01
Inventory every customization
We list every user-defined field, table and object, every formatted search, saved query, alert and approval procedure, each add-on and what it touches, and every check written into the transaction-notification stored procedure. Crystal and Print Layout Designer templates go on the list too, because the documents customers receive are part of the spec. Most companies find rules nobody remembered adding, and add-ons nobody uses.
- 02
Extraction with keys resolved
Customers, vendors, items, price lists, open documents, journal entries and inventory history come out through the Service Layer or DI API, or through read-only queries where you hold database access. Card codes, item codes and document entries ride along so every relationship survives, and each company database is extracted separately with its own chart of accounts. In a hosted install, getting that access from the host is often the first real step.
- 03
Full replacement or ledger stays
This decision shapes everything after it. If the accounting is ordinary, the whole system goes, ledger included. If several entities consolidate on a statutory calendar or an auditor expects the ledger to stay put, it stays and the operational layer moves around it, posting back through the Service Layer. We take a position on which one applies before we scope anything.
- 04
Build in the cloud while Business One runs
The new system gets built on cloud accounts in your name while Business One keeps running, importing on a schedule so the two stay in step. The areas living in add-ons, queries and spreadsheets come first, because that's where the working day already happens outside the ERP.
- 05
Reconcile a closed period, then retire the servers
Nothing gets switched off until finance has a closed period that matches line for line on both sides, per company, including inventory valuation and open receivables and payables. Then the cutover happens, the add-on and maintenance renewals stop, and the on-site or hosted servers can be retired once the archive is in your hands.
Limits
Where do we draw the line?
Saying this out loud is cheaper for both of us than finding out in month two. If one of these is what you actually want, we are the wrong firm and we will say so on the first call.
- We won't install, host or build anything on your premises. What we build runs in the cloud on accounts in your name, and an on-site Business One gets replaced by moving it to the cloud, never by standing up new servers next to it.
- We won't switch anything off before finance signs off on a period that reconciles on both sides. A cutover taken on assurances, without matched numbers, is how an audit trail ends up with a hole in it.
- We won't carry every user-defined field and add-on across just because it exists. The customizations are a record of where the standard product didn't fit, and discovery decides which rules still matter before any of them become code.
Questions
What do people ask before leaving SAP Business One?
Do you work with on-premise SAP Business One?
Only to replace it, and only by moving you to the cloud. Plenty of Business One installs run on a company's own servers or in a hosted environment, and that's fine as a starting point. We read the data out of it, build the replacement on cloud hosting and database accounts in your name, and retire the servers after a reconciled cutover. We never install, host or maintain anything on site, and we don't build on-premise systems. SAP Business ByDesign, SAP's cloud ERP for mid-sized companies, is a separate product with its own data model, not a hosted Business One.
Can you really replace the whole ERP, ledger included?
For most Business One companies, yes. The general ledger, receivables, payables, inventory and orders move together into a system you own. The exception is real multi-entity consolidation on a statutory calendar, or an auditor who expects the ledger to stay. In that case the ledger stays and the operations around it get replaced, posting back through the Service Layer, and we tell you that before we scope.
We have a lot of user-defined fields and a big stored procedure. Does that come with us?
The rules do. The mechanics don't. We read every user-defined field, table, formatted search and check in the transaction-notification procedure for what it enforces, rebuild the rules that still matter as tested code, and drop the ones that existed only to bend Business One around your business.
What happens to our add-ons?
Each one gets read for what it does and who uses it. The useful behavior gets built into the new system, so it stops being a separate license with its own upgrade schedule. Add-ons that connect to outside services, like shipping, tax or banking, get replaced by a direct integration from the new system.
What does replacing SAP Business One cost?
It depends on how many companies and users are involved, how much lives in add-ons and user-defined tables, and what has to keep connecting, so we don't publish a figure for the build. After a strategy call you get a written scope naming every deliverable and what it costs, measured against your licenses, maintenance, add-ons and servers. What we do publish is the cost of running the result. After launch the system costs roughly $100 to $200 a month to run for a smaller company, and $2,000 to $3,000 a month at enterprise scale. Those are hosting and service bills you pay the providers directly, with no license and no per-user fee.
Who owns the system, the code and the accounts?
Your company does. The repository, the database, the cloud hosting and the sending domain all get created in your name at the start of the build, and we're invited in as administrators so we can work. You can remove us at any point, with no fee and no handover charge. That matters most for a company whose Business One sits on a host's servers today, because owning the accounts is what puts the data back in your hands.
What happens to our historical financial data?
It stays available and it stays reconcilable. Journal entries, documents, customers, vendors and items migrate with their codes, posting dates, periods and currencies intact, so historical figures still tie to the periods Business One reported. You also keep a full export of each company database as an archive your auditor can read without a Business One login, and closed periods reconcile line for line before anything gets switched off.
Can we leave one piece at a time?
Yes. We can build the area that hurts most first, often whatever lives in an add-on or a spreadsheet, and connect it to Business One through the Service Layer so nothing gets keyed twice. The full replacement, ledger included, then follows as its own decision, and Business One stays live until the closed period reconciles.
Related
Coming from a different tool?
The same exit treatment for the other platforms people leave, and the pages that explain the custom model itself.
Where did SAP Business One stop fitting?
Book a strategy call, or send a short note about the workarounds your team runs today. If keeping SAP Business One is the right answer, you will hear that first.