Moving from NetSuite¶
The Migration Kit is a service: our team moves your company from NetSuite to Consoletium with you, and finance signs off a reconciliation before NetSuite is switched to read-only. Consoletium was designed alongside NetSuite's own record structure, so documents keep their numbers, their links to each other and their history.
What comes across¶
| From NetSuite | Into Consoletium |
|---|---|
| Chart of accounts, subsidiaries, currencies and exchange rates, period translation rates | The ledger, under its own numbering, with each NetSuite account mapped |
| Customers, vendors, addresses, payment terms, sales team, price levels and rules | Lists, with addresses and terms as they were |
| Items, classes, item–vendor and item–location settings, reorder points | Items, with stock settings |
| Stock on hand by item, location, bin and lot | Opening stock, tied to the opening journal |
| Sales orders, invoices, cash sales, credit memos, returns, estimates and opportunities | Documents, with their NetSuite numbers and links |
| Purchase orders, bills, vendor credits and returns, vendor payments | Documents, with what is still open left open |
| Customer payments, deposits, bank transfers, cheques, bank statements and reconciliation | Banking, with reconciled items still reconciled |
| Due dates, notes and the audit history | As recorded in NetSuite |
You choose how much history comes across. Most companies bring everything since a chosen year and summarise the years before.
How it runs¶
- Connect. You create an integration record and an access token in NetSuite for a role we specify (read-only). Nothing is installed in NetSuite.
- Export and load. We pull each record type, load it into your Consoletium company, and report what loaded and what did not. Every load can be repeated safely: it is keyed on the NetSuite internal id, so a second run updates rather than duplicates.
- Reconcile. Control totals are compared side by side: document counts by type and year, the trial balance at month-ends, receivables and payables against their ageing, stock value against the ledger. Every difference is explained or fixed.
- Run in parallel. For a few weeks NetSuite stays your system of record and a daily sync brings across everything created or changed the previous day, so your team can learn Consoletium on live data.
- Cut over. A pre-flight check the week before confirms backups, jobs, the sync and the open items. On the cut-over date finance signs the reconciliation pack: counts, a balanced trial balance that matches NetSuite's, receivables and payables tying to their control accounts. NetSuite goes read-only and Consoletium becomes the system of record.
How long it takes depends mostly on how much history comes across; we agree the plan and the cut-over date with you before starting. Pricing is on consoletium.com/migrate/netsuite.
What you need to provide¶
- A NetSuite administrator for about a day at the start, to create the integration and token.
- A finance contact who can answer questions about old adjustments and sign the reconciliation.
- The cut-over date, chosen at a month-end.
From another system¶
The same five steps work from any system; only the first one changes.
| Your system | How we read it |
|---|---|
| Xero, QuickBooks Online | A read-only connection you approve in your browser; nothing is installed. |
| AutoCount, SQL Account | A read-only login to its database on your server, or its standard exports if that is not possible. |
| SAP Business One, Odoo, Microsoft Dynamics, Sage, MYOB, any other | Its standard exports to Excel or CSV, mapped once for that system. |
| Spreadsheets | Our templates, which you can also load yourself with the import centre. |
Every route ends with the same reconciliation against your old system's own trial balance, ageing and stock valuation, and the same sign-off. Orders from CSV are built in for day-to-day use.