How migration works#
- It is scoped and priced separately from implementation, and starts at $1,500 (one-time).
- "No surprises at kick-off."
- How much history you carry across is your decision, not ours.
- Every load is reconciled against the old system before go-live.
- Open invoices and opening balances are always part of it.
- It is optional. "No migration needed" is a valid choice and costs $0.
Starting price by scope, as shown in the cost calculator:
| Scope | Starting at |
|---|---|
| Master data only (customers, suppliers, items) | $1,500 |
| Master data + opening balances (plus trial balance and stock counts) | $2,400 |
| Full transaction history (several years of records) | $3,900 |
The five-step switch#
| Step | What happens |
|---|---|
| 1. Assess | What you run today, what has to move, and what can be left behind |
| 2. Map | Your accounts, master data and processes mapped onto ERP36T |
| 3. Migrate | A test load first, reconciled against the old system before anything is signed off |
| 4. Parallel run | Both systems run briefly side by side, so you prove the numbers agree |
| 5. Go live | Switch over with our team in the room, then support under one contract |
Switching pages#
| From | Page | Page headline |
|---|---|---|
| QuickBooks | /quickbooks-alternative/ | "Outgrowing QuickBooks?" |
| Excel and spreadsheets | /excel-to-erp/ | "Still running the business on Excel?" |
| Odoo | /odoo-alternative/ | "Looking for an alternative to Odoo?" |
| SAP Business One | /sap-business-one-alternative/ | "A more flexible ERP for a growing business." |
| NetSuite | /netsuite-alternative/ | "Enterprise ERP capability without enterprise complexity." |
Each page has a lead form to book a free demo or a free assessment of what moving would take. We come back with a migration scope, a realistic timeline and an honest view of what it will take, at no cost.
From QuickBooks#
QuickBooks is a good accounting package. It was never meant to run a warehouse, a production line or a sales pipeline, which is why those ended up in spreadsheets.
What we hear from QuickBooks users:
- inventory tracked in a spreadsheet beside the accounts
- no purchase order approval or three-way match
- landed cost worked out by hand, so margin is an estimate
- no CRM, so the pipeline lives in someone's inbox
- multi-location or multi-company handled by separate files
- month-end assembled manually every single month
What changes on ERP36T:
- inventory, purchasing and sales on the same ledger
- purchase orders, receipts and invoice matching built in
- landed cost applied automatically to every receipt
- CRM, quotations and sales orders in the same system
- multi-company and multi-location as standard from Professional
- financial statements available the moment a transaction posts
Note: most QuickBooks migrations are straightforward. The chart of accounts and master data map cleanly; the decision that matters is how much transaction history you carry across.
What moves across:
- chart of accounts
- customers and suppliers
- items and price lists
- open invoices and bills
- opening balances and trial balance
- historical transactions, if you want them
From Excel and spreadsheets#
Spreadsheets got you here. They stop working at the point where two people need the same number at the same time, and nobody can say which file is current.
What we hear from Excel users:
- several versions of the same file, none of them definitive
- numbers re-typed between sheets, and sometimes wrong
- no record of who changed what, or when
- stock figures that are only right on the day they're counted
- reporting rebuilt by hand every month
- the whole operation depending on one person's workbook
What changes on ERP36T:
- one record and one version, visible to everyone who should see it
- a transaction entered once and reflected everywhere
- a full audit trail on every field, with previous values
- live stock that updates as goods move
- reports and dashboards that build themselves
- role-based access instead of a shared file
Note: coming from spreadsheets is usually the fastest migration, because there is no legacy system to decommission. It needs the most attention to process design, because the spreadsheet rules are in people's heads.
What moves across:
- customer and supplier lists
- item master and pricing
- current stock counts
- open orders
- opening balances
- historical data worth keeping
From Odoo#
Odoo is capable software. The complaints we hear are rarely about features; they're about app-by-app pricing, version upgrades that break customisations, and a partner who has moved on.
What we hear from Odoo users:
- cost that climbs every time you switch on another app
- customisations that break at the next version upgrade
- a partner who implemented and then disappeared
- hosting, support and development split across vendors
- modules that overlap but don't quite join up
- upgrade paths that turn into re-implementations
What changes on ERP36T:
- one plan, with the modules your industry needs already on
- customisation done in a way that stays upgradeable
- the team that builds it also hosts and supports it
- hosting, updates, backups and helpdesk in the subscription
- one database, so modules genuinely share data
- a named owner after go-live, not a ticket queue
Note: Odoo migrations are technically comfortable, because both platforms model the same business objects. The effort goes into reproducing your customisations properly rather than into moving the data.
What moves across:
- chart of accounts and fiscal setup
- customers, suppliers and contacts
- products, variants and price lists
- open orders and documents
- stock positions and valuations
- transaction history as required
From SAP Business One#
SAP Business One is a serious product. It also tends to arrive with per-seat licensing, a stack of third-party add-ons, and changes that take a quarter to get approved.
What we hear from SAP Business One users:
- per-seat licensing that punishes headcount growth
- essential capability sold as third-party add-ons
- a change request queue measured in months
- annual maintenance on top of the licence
- reporting that needs another tool to be usable
- upgrades that become projects in their own right
What changes on ERP36T:
- plan-based pricing, where users are the secondary dimension
- portals, BI and workflow included rather than bolted on, with AI as an optional add-on
- configuration changes made by your team, not a developer
- hosting, support and updates in the subscription
- reporting and dashboards in the platform
- an upgrade path that doesn't invalidate your customisations
Note: SAP B1 migrations need proper scoping, because there is usually real customisation and several add-ons to account for. We map the add-ons to standard capability first, and only then quote.
What moves across:
- chart of accounts and cost centres
- business partners
- item master and BOMs
- open documents and balances
- warehouse and stock positions
- historical transactions as required
From NetSuite#
NetSuite does almost everything. The question is whether you are paying for almost everything, and whether the renewal is the conversation you want to have every year.
What we hear from NetSuite users:
- renewal pricing that moves in one direction
- modules licensed separately for capability you assumed was included
- customisation that requires a certified specialist
- implementation partners charging for every adjustment
- a platform far larger than the business actually needs
- data that is difficult to get back out
What changes on ERP36T:
- transparent plan pricing, with the capability listed up front
- multi-company, multi-currency and multi-location in the platform
- an open-source foundation, so your data stays yours and exportable
- the implementer, the host and the support desk are the same team
- right-sized for a growing business rather than an enterprise
- customisation as a normal activity, not an exception
Note: NetSuite exports cleanly, so the data side is manageable. What needs care is reproducing saved searches, workflows and scripts; we scope those explicitly rather than discovering them at go-live.
What moves across:
- the full chart of accounts and subsidiaries
- customers, vendors and contacts
- items, assemblies and price levels
- open transactions and balances
- inventory positions across locations
- historical data as required
Industry-specific switching notes (from the landing pages)#
| Industry | Typical starting point | What is carried across |
|---|---|---|
| Distribution | QuickBooks, Sage or spreadsheets | Customers, suppliers, items, price lists, opening balances |
| Wholesale | Spreadsheet price lists and a separate accounting package | Customers, price lists, items, opening balances |
| 3PL & Logistics | A WMS that doesn't bill, or spreadsheet rate cards | Client records, rate cards, stock, opening balances |
| Manufacturing | Spreadsheet BOMs, a standalone MRP, or QuickBooks | Items, bills of materials, open orders, opening balances |
| Retail | A standalone POS plus QuickBooks or spreadsheets | Items, price lists, customers, opening stock |
| Professional services | Projects in spreadsheets, billing in QuickBooks | Clients, projects, rates, opening balances |
| Healthcare | Separate patient, pharmacy and accounting systems | Master data and opening balances |
| Construction | Estimating in spreadsheets, job costing in QuickBooks | Customers, suppliers, items, open jobs, opening balances |
| Immigration | Cases in spreadsheets, billing in QuickBooks | Clients, open cases, opening balances |
In the cost calculator, the system you use today is "the single biggest factor in migration cost". Where the data comes from matters.
ERP savings calculator (/erp-savings-calculator/)#
"What is your current stack actually costing you?" Licences are the visible half. The other half is the time your team spends moving numbers between systems that don't talk to each other.
Inputs: everything recalculates as you type. The defaults are typical for a 40-person distribution business.
- Employees
- People who would use the ERP
- Accounting software, per month
- Inventory / warehouse software, per month
- CRM software, per month
- Payroll software, per month
- Other tools, add-ons and integrations, per month
- External IT support and consultants, per month
- Hours a week spent re-keying and reconciling, across the team
- Blended hourly cost of that time, fully loaded
How it works:
- Current cost: the monthly total of the software and IT support you entered.
- ERP36T cost: the published plan price for your number of users, plus additional users.
- Up to 5 users: Starter.
- Up to 15 users: Business.
- More than 15 users: Professional.
- The one-time implementation is spread monthly over three years.
- Time: counted separately from cash, so the same hours are never counted twice. The calculator deliberately assumes that only half the reconciliation time is recovered: one system removes the re-keying, not the judgement.
- Result: an "indicative monthly benefit", with the cash difference and the recovered time shown separately.
- The calculator assumes the listed tools are replaced rather than kept alongside ERP36T.
Indicative only. A free 30-minute assessment uses your actual systems, volumes and processes, and produces the real number.