Pricing
Log inBook a demo

Migration · NetSuite

Most companies should not leave NetSuite

We sell against NetSuite and we still start this page there, because leaving a mature ERP is a materially bigger decision than leaving QuickBooks and the reasons people give for wanting to are frequently not the real problem. Here is how we test it, and the three cases where we will tell you to stay.

Get an honest readerp.io vs NetSuite

Should you actually leave?

Your size, entity structure, and what is driving the question. We come back with a straight answer, including 'stay'.

1 / 3
Three closed months must tie firstRead-only throughoutWe also rescue NetSuite deployments
Stay ifReal reasonsHow it worksQuestions

Stay if

Three cases where we will tell you not to move.

These are not hedges. Each describes a situation where leaving NetSuite for us would be a mistake you would discover in month four.

You file statutory returns abroad

Local compliance across multiple jurisdictions is two decades of accumulated work. We have not built it and will not pretend otherwise.

You manufacture or run a warehouse

BOMs, routings, work orders, MRP, bin-level control. We build none of it, and no amount of integration substitutes for it.

A sponsor or acquirer expects it

Diligence teams know NetSuite and assess a standard instance faster. That is worth real money at a transaction and it is a rational reason to stay.

Real reasons

Three that hold up under examination.

Seat cost has outrun the value

The most common genuine reason. Headcount grew, the licence grew with it, and most of those seats do three things a month.

The implementation never landed

A configuration nobody owns, customisations nobody documented, and a close that still runs on spreadsheets. Sometimes the fix is a rescue, not a migration — we will say which.

You are simpler than you were

A divestiture, a wind-down of an international arm, or an exit from inventory can leave a services business paying for machinery it no longer uses.

The reason that does not hold up

"We hate the interface." It is a real complaint and it is almost never worth a ledger migration. If the UX is the binding problem, an integration layer that puts reporting and AP automation on top of NetSuite solves it for a fraction of the cost and risk — and that is an engagement we sell, so we are not steering you away from spending money.

Extractread source, no writesMapaccounts, customers, vendorsLoadinto a staged tenantReconciletrial balance, per periodgate · must tieReviewyour controller signsCut oversource goes read-onlygate · must tievariance → back to mapping, never waivednothing advances past a gate until the trial balance agrees to the penny

How a NetSuite exit actually works

Nothing about the mechanics is exotic. NetSuite has a good API and SuiteAnalytics exports, so extraction is straightforward. The difficulty is that a NetSuite instance which has been live for six years encodes a great deal of business logic in places a migration has to find: saved searches, workflows, SuiteScript, custom records, and custom fields that somebody added in 2021 and that a monthly report silently depends on.

So the first phase is inventory rather than extraction — cataloguing what has been built on top of the platform and deciding, item by item, what is still needed. In our experience roughly a third of custom objects in a mature instance are no longer used by anyone, and finding that out is valuable whether or not you migrate.

The hard part of leaving NetSuite is not the data. It is the six years of logic built on top of it, some of which nobody remembers building.

The gate is the same, and it is stricter here

We will not sell a NetSuite cutover until a shadow ledger has reconciled against your NetSuite trial balance for at least three consecutive closed months at zero variance. With NetSuite that means running longer than we would ask for a QuickBooks customer, because the switching risk is higher and the multi-entity structures are more intricate.

The practical consequence is that you can begin this process without committing to anything. A read-only connection and a shadow ledger cost you nothing but a configuration, and if the reconciliation reveals that your NetSuite instance is doing more than you thought, that is a finding and a reason to stay.

Timeline and price

Single-entity NetSuite exits run eight to twelve weeks and start at $32,000. Multi-entity with intercompany history is quoted after a diagnostic and typically lands between $60,000 and $120,000 depending on entity count, currencies, and how much SuiteScript is in play.

We quote after inventorying the instance rather than before, because the range within NetSuite is enormous. A clean single-subsidiary instance with light customisation is a different engagement from a six-subsidiary structure with forty custom records and a revenue recognition configuration nobody has touched since implementation.

We would rather rescue it

About half the NetSuite conversations we have end in a rescue or an integration engagement instead of a migration — fixing the configuration, rebuilding the close, or adding the reporting layer the instance never produced. Those are cheaper for you and perfectly good business for us.

Questions

What NetSuite customers ask.

Can we run both during the transition?
That is the design. The shadow ledger reconciles against NetSuite daily while NetSuite remains authoritative, and cutover only happens after three consecutive closed months have tied at zero variance.
What happens to our SuiteScript customisations?
They are inventoried and triaged. Some are no longer used, some become configuration, and some become custom modules we host. The inventory itself is usually the most useful deliverable of the diagnostic, migration or not.
Will our renewal timing matter?
Yes. NetSuite renewals are annual and auto-renew with notice periods, so start the diagnostic at least two quarters before your renewal date. Beginning the process also gives you a genuine alternative at the negotiation, which several customers have used to stay on better terms.
Do you migrate our history?
Opening balances plus one to two years of detail as standard, with NetSuite kept read-only for prior years. Full-history migrations are quoted separately and we usually advise against them.
What if the diagnostic says we should stay?
Then it says so in writing, and roughly half of them do. We would rather sell you a rescue or an integration engagement that works than a migration that should not have happened.

Test the decision before you make it.

A read-only connection and a shadow ledger cost you nothing and answer the question with evidence.

Book a diagnosticCompare us to NetSuite