NetSuite to Campfire
Leaving NetSuite for Campfire, with the audit trail intact
A ledger migration is not a data export. It is a series of decisions about what your numbers mean, made once, under time pressure, with an auditor reading the result next year. We have spent twenty years on the NetSuite side of that work.
Scope
What has to move, and what has to be decided
Each of these is a decision with an audit consequence. None of them is a file export.
01
Chart of accounts
Mapped, not copied. A NetSuite chart carries accounts created for a process nobody runs any more, and they do not need a second life.
02
Opening balances
Reconciled to NetSuite before anyone reports from the new ledger, with the differences explained rather than absorbed.
03
Transaction history
How many years, at what granularity, and what your auditor expects to be able to test. Decided deliberately, not by default.
04
Revenue contracts
Recognition schedules in flight have to keep recognising on the same basis after the move, or the comparatives stop meaning anything.
05
Subsidiaries and consolidation
Entity structure, intercompany and currency handling rebuilt to produce the consolidated view your board already reads.
06
The systems either side
Banking, AP, payroll, billing and tax connections all point at NetSuite today. Every one of them needs a new destination and a cutover order.
Honest answer first
Whether you should move at all
Worth moving
Fits when
NetSuite is doing the work of a general ledger for you, and the close is the pain you actually feel.
Watch for
The things you would lose are things you do not use: inventory, order management, manufacturing, field service.
Think harder
Fits when
You use NetSuite for items, orders, receiving or warehouse work as well as the books.
Watch for
Those capabilities have to go somewhere. Moving the ledger without deciding where they land is how a migration turns into a rebuild.
Stay
Fits when
Manufacturing, BOMs, production or field service run in NetSuite.
Watch for
There is no version of this move that ends well, and we will tell you that before you spend anything on it.
We implement both platforms, so we have no stake in the answer. The longer comparison → · How we handle migration data →
Process
How the project runs
1
Inventory what NetSuite actually does
Not what it was bought for. Which modules carry real transactions, which customisations matter, and who depends on them.
2
Decide the destination for each
The ledger goes to Campfire. Everything else needs a named home, including the work Campfire does not do.
3
Map and stage
Accounts, entities, revenue contracts and balances mapped, then loaded into a trial tenant and reconciled against NetSuite.
4
Cut over in one close
A cutover that spans two closes doubles the reconciliation. We plan for a single boundary and a parallel close around it.
5
Prove it to the auditor
Documentation of what moved, at what granularity, and how balances tie back — produced during the migration, not reconstructed a year later.
FAQ
Questions about leaving NetSuite
Can we keep NetSuite for inventory and run Campfire for accounting?
Some businesses do, and it can work when the boundary is clean and the posting rules are written down. It is also the most expensive answer, because you keep paying for NetSuite. We would rather show you the arithmetic than assume it.
What happens to our NetSuite customisations?
Most do not transfer, because they exist to make NetSuite do something Campfire either does natively or does not do at all. We sort them into replace, retire and rebuild elsewhere, and price the third group honestly.
How much history can Campfire take?
Campfire migrates from NetSuite and QuickBooks and states that entries arrive at transaction-level detail. How much you should bring is a different question from how much is possible, and the audit answer usually decides it.
Will our auditors accept the move?
They will ask what moved, how it reconciles, and where the detail behind each balance now lives. Those answers are produced during the migration. Retrofitting them afterwards is the part that goes badly.
Who does the data work?
We do. Extraction and mapping on the NetSuite side is our twenty-year side of the fence, and it is the half of a migration that most Campfire partners have never done.
Weighing up a move off NetSuite?
Tell us which NetSuite modules carry real transactions today. That answer decides whether this is a migration or a rebuild, and we will say which one you are looking at.