ERP replacement. Acumatica
Leaving Acumatica for a system your business owns
In short
- Black Badger Software Solutions is a custom software company in Clearwater, Florida that replaces Acumatica, ledger included where the accounting is ordinary, with a cloud system your business owns outright, running on hosting and database accounts in your name.
- We were never an Acumatica partner and we have no Acumatica engagement on record, so nothing rides for us on which way you go, and we do not configure, patch or administer Acumatica for anyone.
- Leaving means customers, vendors, stock items, orders and transactions come out through the contract-based REST API and generic inquiry exports with their keys intact, customization projects are read for the rules they hold and rebuilt as code, and Acumatica 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.
Acumatica is a real ERP. Financials, distribution, inventory, project accounting and industry editions for construction, distribution and manufacturing, built for the cloud from the start. It's priced by the applications you license and the resource level you run at, not per named user, and it's sold and implemented through independent firms in the vendor's channel. We sell none of it, so nothing rides for us on which way you go.
The pricing model is the thing people like, and it's real. Adding a person doesn't add a license. But a mid-sized company with real volume still ends up paying for the edition, the modules and the resource tier, plus the firm that implemented it, and the work that actually runs the business often sits in spreadsheets and add-ons beside it. That gap is where we come in.
Where we stand
Do you implement or support Acumatica?
No. We were never an Acumatica partner, we have no Acumatica 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 straight answer on whether the ledger should move with them.
We were partners of other platforms, monday.com, Smartsheet, Wrike and Zoho among them, and we ended those partnerships to build replacements. So the Acumatica work we take is replacing it, the whole system when the accounting is ordinary, on cloud accounts in your name. We do not configure Acumatica, maintain customization projects or take an admin retainer. Where the ledger should stay, the section below says so.
Where it fits
Where does Acumatica fit?
We sell no Acumatica 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.
Multi-company and multi-branch operations with intercompany transactions and a consolidated close on a statutory calendar. That's genuinely hard software to write, and Acumatica does it.
Companies whose auditors, lenders or investors expect a recognized ERP as the book of record. The name on the platform is part of the answer there.
A business whose operation matches one of the industry editions closely. A distributor or a contractor that works the way the edition assumes gets a lot of capability without writing any of it.
A company already live whose finance team is happy with it and whose people need broad access without per-user cost. If the ledger is doing its job, keep it and fix what sits around it. That's a smaller project than a replacement, and it's often the honest advice.
Where it breaks
Where does Acumatica break down?
The failure modes below are the ones that show up again and again as a company grows.
The cost tracks volume. Licensing follows the applications you add and the resource level your transaction volume needs, so a growing company moves up a tier on the vendor's terms. No per-user fee doesn't mean the bill stays still.
Everything runs through the firm that sold it. Implementation, support, upgrades and most customization come from the same outside firm, billed in service hours. Changing firms means someone new reading code they didn't write, so most companies don't, and that's a commercial position you feel at renewal.
Customization is a software project. Real changes live in customization projects written in C# against the vendor's framework, and the platform ships two major releases a year. Each upgrade means revalidating and republishing that code on the vendor's calendar, not yours.
Reporting is a generic inquiry, and writing a good one is a skill. The questions a manager asks every day (what's late, which job is losing money, who is overloaded) end up exported to a spreadsheet. That's how a company ends up running an ERP and a shadow system at once.
The edition decides the shape. Industry editions assume an industry's typical process. Where your operation differs (field work, quoting with real pricing rules, a customer-facing view of jobs and orders), the answer is another add-on, another integration or another sheet.
The replacement
What does replacing Acumatica look like?
The lead option is a full replacement, ledger included. If the accounting is ordinary (one entity or a few, a clean chart of accounts, a close your team runs without heroics), the whole system moves, and finance gets a ledger built around how the business actually posts. If multi-company consolidation, a statutory close or an auditor's expectations genuinely justify keeping Acumatica's ledger, it stays, and the operational layer gets replaced around it, posting back through the API. We tell you which one applies before anything is scoped.
Either way, the system takes the shape of your operation. The records are your jobs, sites, orders, items, crews and customers, with real relationships between them, and the pricing and approval rules live in tested, versioned code. Reporting reads live data, so a manager's daily question is a screen. No generic inquiry, no export.
Migration reads Acumatica through its contract-based REST API and generic inquiry exports. Customers, vendors, stock items, orders, transactions and history get mapped into the new structure in a document you approve before anyone writes a row. Both systems run in parallel until the numbers reconcile line for line, and nothing gets switched off until finance has signed off on a closed period that matches on both sides.
You own the result. It runs in the cloud, with code in a repository in your name and database and hosting on accounts in your name. Unlimited users including people outside your company, no edition or resource tier to renegotiate, and no outside firm standing between you and a change. 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.
The general ledger is derived. You can't copy it out of a table. Transactions post by company, branch, financial period and ledger, so an extract taken without deciding those produces figures that won't tie to a closed period, and finance signs nothing off.
Records connect through keys and the names on screen are only labels. Pull orders without the customer, item, branch and warehouse keys resolved, and attribute values without the records they belong to, and you've got a warehouse of rows nobody can reconcile against what Acumatica reported last quarter.
The operational half is where the working day happens. Replace the finance side, leave scheduling, quoting and job tracking in spreadsheets, and the shadow system survives the whole project. That shadow system is what the ERP was bought to kill in the first place.
The order of work
What happens, in what order, when you leave Acumatica?
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
Edition, module and customization audit
We check which licensed applications carry real activity and which were bought for a plan that changed, then list every published customization project, generic inquiry, import scenario, business event and automation still firing. Roles and row-level restrictions by branch get mapped too. Companies routinely find capability they're paying for and quietly working around.
- 02
Extraction with keys resolved
Acumatica comes out through its contract-based REST API, generic inquiries exposed for export, and import and export scenarios where they already exist. Customers, vendors, stock items, orders and transaction lines get pulled with their keys so the relationships survive, and company, branch, period and currency ride along on every transaction. We don't copy the generic inquiries. They're configuration, so what gets recorded is the question each one answers.
- 03
The ledger decision
This one decision shapes everything after it. Where the accounting is ordinary, the ledger moves with everything else and the whole of Acumatica goes. Where multi-company consolidation, a statutory close or an auditor genuinely needs it, the ledger stays and the operational layer moves around it, posting back through the API. We take a position on which one applies before we scope anything.
- 04
Build against a live ERP
The new system gets built in the cloud while Acumatica keeps running, importing on a schedule and posting into it wherever the ledger is staying. The operational areas that live in spreadsheets today come first, along with the customer-facing view, because that's where a manager's daily question currently needs an export.
- 05
Reconcile a closed period
Nothing gets switched off until finance has a closed period that matches line for line on both sides, including intercompany balances and any consolidation. Operational counts get checked at the same time. Open orders, stock on hand, scheduled work. Then the cutover happens, and the subscription comes off at renewal.
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 pretend every ledger should move. Full replacement is what we lead with, but multi-company consolidation and a statutory close are serious software, and if that's why you bought Acumatica we'll build around it and say so plainly.
- 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 install anything on your servers or build an on-premise system. What we build runs in the cloud on accounts in your name, and an on-premise Acumatica gets replaced by moving the business onto that cloud system, never by standing up another server.
Questions
What do people ask before leaving Acumatica?
Can you really replace an ERP, ledger and all?
Yes, and for a company whose accounting is ordinary that's what we recommend. Receivables, payables, the general ledger and the operational layer move into one system built around how you work. The exception is real and we'll name it. When multi-company consolidation, a statutory close or an auditor's expectations justify keeping Acumatica's ledger, it stays, and everything around it gets replaced and posts back through the API.
Do you work with on-premise or privately hosted Acumatica?
Yes, as a starting point, never as a destination. Acumatica can run on your own servers or with a hosting firm, and either way we read the data out through the same API and inquiry exports. The replacement always runs in the cloud on hosting and database accounts in your name, so leaving a self-hosted install means moving to the cloud as part of the project. We don't install anything on-site, host anything on your servers or build on-premise systems.
Acumatica doesn't charge per user. Why would we leave?
Often you shouldn't, and the per-user point is a fair one. The bill still tracks the applications you license, the resource tier your volume needs and the hours the implementing firm bills, and none of that goes away by staying. The question is whether the system fits the operation. If your team runs the business in spreadsheets beside it, you're paying for an ERP and maintaining a shadow system at the same time.
We've got a lot of customization projects. Do they come with us?
The rules do. The code doesn't. We read each customization project, automation and business event for what it enforces, rebuild the rules that still matter as tested code, and let the code that existed only to bend Acumatica around your business go away with the model. You also stop revalidating it twice a year.
What does replacing Acumatica cost?
It depends on which applications are in real use, how many companies and branches are involved, whether the ledger moves, 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 renewal and the implementing firm's hours. 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. No fee, no handover charge, no license reverting to us. With an ERP that matters more than anywhere else, because what makes a renewal uncomfortable is having nowhere else to go.
What happens to our historical financial data?
It stays available and it stays reconcilable. Transactions, orders, customers, vendors and items migrate with their keys, company, branch, period and currency intact, so historical figures still tie to the periods Acumatica reported. Where the ledger is staying, none of your financial history moves and the new system posts into it. Where it's being replaced, you keep the raw exports as an archive your auditor can read without an Acumatica login, and closed periods reconcile line for line before anything gets switched off.
Can we leave one piece at a time?
Yes, and that's usually how it goes, even when the end state is a full replacement. We build the area that hurts most first and connect it to Acumatica through the API, so nothing gets re-keyed while the rest stays put. The ledger is usually the last thing to move, once the operational side has run cleanly for a period.
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 Acumatica stop fitting?
Book a strategy call, or send a short note about the workarounds your team runs today. If keeping Acumatica is the right answer, you will hear that first.