ERP guide
Should you stay on NetSuite or move to a custom ERP?
Stay on NetSuite when it runs your process with little scripting and the renewal still fits your budget, because a working system costs less to keep than to replace. Move to a custom ERP when each renewal rises, modules and subsidiaries keep adding fees, and consultants spend more time bending NetSuite to your process than your team spends using it.
| What you are comparing | Staying on NetSuite | A custom build |
|---|---|---|
| Renewal and price changes | NetSuite publishes no price list, and customers on its forums report renewal increases of 40% to 150% and uncapped yearly uplifts. Oracle sets the price again at each renewal. | No license to renew. After the build you pay for hosting, database and email on accounts in your own name, and each change is scoped and priced before work starts. |
| Per-user and module charges | NetSuite licenses by modules and users, and each added module, extra subsidiary and sandbox carries its own fee. | No fee per user, module or entity. A new warehouse lead, a read-only executive or a second company adds no license. |
| Fit to your process | NetSuite comes with its own processes, and what they miss is built in SuiteScript by a consultant. Customers retest those scripts at each of the two releases a year. | Built from your own process, including the pricing rules, approvals and handoffs that set you apart. Updates arrive when you ask for them. |
| Getting your data out | Customers who left report that the full CSV export misses data, that custom scripts cannot move, and that read-only access after the contract ends carries its own fee. | The database sits in an account you own, so every table can be exported in standard formats whenever you choose, with no vendor to ask. |
| Who runs it | An internal administrator plus a NetSuite consultant for scripts and changes. Oracle runs the platform and sets the release schedule. | A named owner on your side, with Black Badger or any capable developer maintaining code written to be read and extended. |
| What changes as you grow | More users, modules, subsidiaries and transaction volume each raise the subscription, and passing service-tier limits moves the account to a pricier tier. | Growth adds hosting load and the features you choose to build. Headcount and new entities add no license. |
| Getting started | Staying needs no project, though each release still takes testing time from your team. | Starts with discovery and a written scope, then areas go live in stages on a schedule set in that scope. |
When staying on NetSuite is the right call
Stay when NetSuite runs your process with little scripting. A company whose orders, stock and accounting look like most companies' is the customer NetSuite was built for, and replacing a system that works costs more than keeping it.
Stay when the renewal you were offered is one you can live with and your team trusts the numbers NetSuite produces. Leaving is a project, and a modest increase is not reason enough to start one. Ask for a cap on future increases before you decide.
Stay for now if you are in the middle of an implementation or have just finished one. Judge NetSuite on a settled year of use, after the early problems of go-live have passed.
What leaving NetSuite involves, step by step
Start with the contract. Find the renewal date and the notice terms, and plan the move so the new system is live before NetSuite access ends, because customers report that read-only access after leaving carries its own fee.
Export everything while you still have full access. That means customers, vendors, items, open orders, open invoices and bills, the chart of accounts and its history, attachments, and every saved search your staff rely on. Customers report that the standard CSV export misses data, so check record counts against NetSuite before the contract ends.
Write down what your scripts and workflows do. SuiteScript cannot move to another system, but it is the most exact record you have of your business rules, and the replacement is built from that record.
Run the old and new systems side by side through a closing period, compare the results, and switch when they match.
How a custom cloud ERP replaces NetSuite
Black Badger builds custom cloud ERPs and replaces cloud ERPs such as NetSuite. A build starts with discovery and a written scope that maps orders, stock, purchasing, billing and reporting as your company runs them today.
The system runs on cloud hosting and a database in accounts you own, and the code is handed over. There is no fee per user, so access can go to everyone who needs it, read-only staff included.
A custom ERP does not have to replace everything at once. Where an accounting package works and your accountants trust it, the package can stay and the custom system connects to it. The build goes where NetSuite did not fit.
What a custom build involves, and how to ask about one
Questions buyers ask
What happens to our SuiteScript customizations if we leave NetSuite?
SuiteScript customizations stay behind, because the code runs only inside NetSuite. The logic they hold does not have to be lost. Export the scripts and workflow definitions before access ends, and use them as the specification for the same rules in the new system.
Can we keep NetSuite for accounting and build the rest?
Keeping NetSuite for accounting and building operations around it is possible, and some companies start there. The custom system reads and writes NetSuite through its API. The NetSuite license and its renewals stay, so the split pays off when operations is where most of the scripting and consultant time goes.
Is a custom ERP harder to run than NetSuite?
A custom ERP needs a named owner on your side and a developer to maintain it, and NetSuite needs the same in the form of an administrator and a consultant. The difference is who sets the schedule. NetSuite releases twice a year on Oracle's timetable, and a custom system changes only when you ask.
More from this guide
- Top picks
- After a renewal increase
- Multi-entity companies
- NetSuite alternatives
- Acumatica alternatives
- Sage Intacct alternatives
- Business Central alternatives
- Dynamics GP alternatives
- SAP Business One alternatives
- Epicor alternatives
- Odoo alternatives
- Salesforce alternatives
- HubSpot alternatives
- Leaving Acumatica?
- Leaving Sage Intacct?
- Leaving Business Central?
- Leaving Dynamics GP?
- Leaving SAP Business One?
- Leaving Epicor?
- Leaving Odoo?
- Leaving Salesforce?
- Leaving HubSpot?
- Custom option