NetSuite Migrations · Canada
NetSuite to QuickBooks migrations for Canadian organizations.
Paying enterprise prices for capacity you never use. We move Canadian companies off NetSuite and onto QuickBooks before renewal: full history, every entity, reconciled to the penny, with your data processed in Canada throughout. Fixed scope, fixed date.
Time the assessment to your renewal date. Leverage is worth more than urgency.
The Exit, Done Properly
Why Canadian companies leave NetSuite, and what moves with them
Annual costs climbing, modules unused, admin overhead owning your finance team. Right-sizing to QuickBooks is not a downgrade of your books, only of your licence.
Full History
Complete transactional history moves and is reconciled per entity against your NetSuite trial balance, AR aging and AP aging. Opening balances and a shrug is a shortcut we do not take, because it is the one your auditor will find.
Reports Rebuilt
Every saved search, custom report and scheduled email is inventoried during analysis and rebuilt in QuickBooks before cutover. Your controller signs off on the rebuilt pack, so nobody discovers a missing report at the first month end.
Entities and Currency
Multi-entity structures, intercompany balances between Canadian and US entities, and CAD and USD books handled natively, with GST/HST continuity written into scope rather than promised on the call.
The Renewal Maths
Where the money actually goes
Most finance teams underestimate their true NetSuite cost, because it does not arrive as one line.
What you are paying for now
A NetSuite renewal is rarely a single number. It is a base platform fee, plus a user count that only ever went up, plus module fees for the pieces that were switched on during implementation and never switched off, plus a partner or administrator retainer to keep configuration and saved searches working, plus the internal finance time that goes into feeding a system built for a larger company.
The renewal quote shows the first three. The last two rarely appear in the same conversation, which is why the total surprises people when it is finally added up.
What replaces it
On QuickBooks the licence is a fraction of the platform fee, and the administrator retainer usually disappears entirely because the system does not require one. What does not disappear is the work that genuinely earns its keep: consolidation, dimensional reporting, and whatever operational system your business actually runs on.
Right-sizing is not a downgrade of your books. It is a downgrade of your licence, and only where the capability was not being used.
We do not publish a savings percentage, because the honest answer depends on your user count, your module list and what your partner charges. Bring the renewal quote to the assessment and you will get a real comparison rather than a marketing number.
Scope, Stated Plainly
What moves, and what does not
Most migration disappointment comes from a scope nobody wrote down. Here is ours, before you book.
What moves
- Chart of accounts, mapped with your controller, not auto-matched
- Customers and vendors, including CAD and USD balances
- Full transactional history, reconciled per entity
- Open AR and AP with aging intact
- Inventory items and valuation, tied to your closing stock position
- GST/HST, PST and QST codes, filing history and input tax credit detail
- Saved searches and custom reports, rebuilt in the destination
- Basic payroll records, carried at summary level
What does not, and why
- SuiteScript customisations, which have no QuickBooks equivalent
- SuiteFlow workflows, replaced by native QuickBooks capability or an app
- Third-party SuiteApps, which are re-selected rather than converted
- NetSuite record types with no destination equivalent
- User roles and permission trees, rebuilt to your approval matrix
Each of these is inventoried in discovery and given an explicit decision: replace, rebuild, or retire. None are quietly dropped.
Risk Register
What discovery looks for, and what usually breaks
These are the eight things that turn a thirty-day migration into a three-month one. Every project starts by checking all of them.
Subsidiary and elimination structure
NetSuite OneWorld holds subsidiaries in a hierarchy with elimination rules attached. Which entities migrate, which consolidate, and how intercompany balances resolve is a design decision that has to be made before extraction, not discovered during it. Changing it afterwards means reposting history.
Saved search dependencies
Saved searches are frequently used as inputs to other saved searches, to scripts, to dashboards and to scheduled emails. Rebuilding the visible report is easy. Finding the four upstream searches it silently depends on is the part that takes time, so we inventory the whole dependency tree rather than the report list.
Custom records and custom segments
Custom record types and custom segments carry reporting meaning that has no automatic destination equivalent. Each one is mapped to a class, location, project or custom field, or explicitly retired. Left alone, they load as noise and your new reports look wrong for reasons nobody can trace.
Revenue recognition schedules
Open revenue arrangements and deferred revenue schedules do not migrate as transactions. They are recreated so the deferred balance and the future release schedule both tie. This is the single most common source of a post-cutover variance nobody can explain.
Inventory costing and open fulfilments
Item fulfilment and invoice timing can leave quantities and values out of step at a point in time. Valuation is reconciled from the costing detail rather than from a stock-on-hand report, and open sales and purchase orders are loaded in a dependency order that the destination will accept.
Integrations pointing at NetSuite
Ecommerce platforms, CRM, payroll providers, expense tools and third-party logistics all authenticate against NetSuite. Every one is inventoried, and each gets a decision: repoint, replace, or retire. An integration nobody remembered is the classic week-one-after-cutover emergency.
Bank feeds and reconciliations
Bank and credit card feeds are re-authorised on the destination side, and the last reconciled statement on each account becomes the anchor for the first reconciliation after cutover. If the source reconciliations were not clean, that surfaces in week one of discovery rather than at your first month end.
Source data that is already wrong
Unapplied credits, negative inventory, journal entries doing the work of transactions, and duplicate customer records all exist in real files. We surface them in the assessment and tell you which ones to fix before the move and which ones to leave. Migrating a problem faithfully is still migrating a problem.
Method
How a NetSuite migration runs
Listen
Entities, customisations, integrations, sales tax registrations and the renewal clock, mapped in one session.
Analyze
Data audit and fixed-scope quote. You know the cost and the go-live date before committing, not after.
Accelerate
Migration runs alongside live NetSuite. Your team keeps invoicing and keeps closing. Nothing pauses.
Review
Penny-level reconciliation, controller sign-off, training, then and only then, cutover at a period close.
Built for Canadian Books
The part a US migration plan does not account for
Four different sales tax regimes, sometimes at once
Canada is not one sales tax. Ontario, Nova Scotia, New Brunswick, Prince Edward Island and Newfoundland and Labrador use HST, administered federally. British Columbia, Saskatchewan and Manitoba charge GST plus a separately administered PST, with its own registration. Quebec charges GST plus QST. Alberta and the three territories are GST only.
An organization selling into several provinces is therefore carrying multiple registrations and multiple filing obligations in one set of books. Every tax code is mapped to the correct regime and registration, because a code that lands in the wrong bucket is not a display problem, it is a filing problem.
Input tax credit history has to survive
Your input tax credit position is built from transaction-level detail, not from a summary balance. If tax codes are rebuilt from scratch in the destination and history is loaded without them, the ITC trail behind your filed returns quietly disappears, and it is only missed when a prior period is reviewed.
Tax codes, their filing history and the underlying detail are migrated together so previously filed returns still reconcile against the new system.
Six years of records, and the CRA expects them in Canada
The CRA requires businesses to keep books and records for six years from the end of the last tax year they relate to. It also expects those records to be kept at your Canadian place of business unless you have permission to keep them somewhere else.
This is why we retain your NetSuite account read-only rather than decommissioning it at cutover, and why client data is processed in Canada for the duration of the engagement. It removes a question your auditor would otherwise have to ask.
Year end and corporate filing continuity
Comparative figures, fiscal period structure and the opening position for your next T2 all have to come out of the destination system rather than out of a spreadsheet reconstruction. Fiscal calendars are mapped explicitly, and the cutover is planned around your year end rather than against it.
Where payroll is in scope, basic payroll migration is included and carried at summary level so the general ledger stays correct, with detailed payroll history remaining in the source system.
Destination
QuickBooks Online Advanced, or QuickBooks Enterprise
Both are real destinations for a NetSuite exit. Which one fits is a discovery answer, not a preference, and it changes the scope and the price.
QuickBooks Online Advanced fits when
- Your finance team is distributed, or you want the on-premise server gone
- Entity count is modest and consolidation is periodic rather than continuous
- Inventory is straightforward, or already lives in a dedicated system
- You want custom roles, workflow approvals and dimensional reporting without an administrator
- Remote and multi-user access matters more than deep desktop-style inventory control
QuickBooks Enterprise fits when
- Inventory is genuinely complex: assemblies, multiple locations, lots or serials
- You need advanced pricing rules or heavier reporting against large transaction volumes
- Your team is largely in one place and comfortable with a desktop-style workflow
- Transaction volume is high enough that list and file size limits matter
If the honest answer is that neither destination fits what your business actually does, we will say so on the discovery call rather than three weeks into a project.
Timelines and Investment
What a NetSuite exit costs, and how long it takes
Scoped after discovery, quoted as a fixed price, agreed before you commit.
| Engagement | Timeline | Investment |
|---|---|---|
| Standard NetSuite to QuickBooks migration | 30 days | Starting at CAD $10k |
| Multi-entity or extended history migration | 4 to 8 weeks | CAD $15k to $25k |
| Heavy customisation rationalisation and migration | 8 to 12 weeks | Scoped to environment |
Figures in Canadian dollars. Final scope and price are confirmed after the data assessment, and the go-live date is agreed at the same time.
The Other Answer
When you should stay on NetSuite
We migrate in both directions and have no reason to sell you a move you will regret. These are the cases where staying is the better decision.
Genuine multi-book or statutory complexity
If you are running multi-book accounting, or producing statutory reporting in several jurisdictions with different bases, that requirement is real and QuickBooks does not replace it.
Deep operational dependence
Where NetSuite is running manufacturing, warehouse management or field service, and those modules are genuinely used, the financial move is only part of the project and the operational replacement has to be solved first.
Revenue recognition at real complexity
Multi-element arrangements with ongoing modification and reallocation are modelled properly in NetSuite. If that is your business, the cost is buying something you actually use.
Cost alone is not a reason to move. A licence that feels expensive but is doing work you depend on is cheaper than a migration that has to be reversed.
Canadian Proof
A national organization, off an on-premise ERP, in four weeks
Dairy Farmers of Canada, the national policy and promotional organization representing Canadian dairy producers, retired an on-premise Sage 300 environment for QuickBooks Online Advanced. Cloud access for a distributed finance team, and the on-premise server and its licensing overhead gone. Different source system to yours, same standard of execution.
Questions Canadian CFOs ask
Before you book
Do we lose our transactional history?
No. Full history moves and is reconciled per entity against your NetSuite trial balance and agings. Opening-balances-only is a shortcut we do not take. The depth of detailed history is agreed in writing during discovery rather than assumed.
What happens to saved searches and custom reports?
They are inventoried during analysis and rebuilt in the destination before cutover, then signed off by your controller. Nobody discovers a missing report at month end.
Can this be done before our renewal date?
Usually, if the assessment happens early enough. Bring your renewal date to the first call and we plan backwards from it. Thirty days is the standard timeline for a single-entity migration with clean data.
How is Canadian sales tax handled?
GST, HST, PST and QST codes are mapped into the destination platform with their filing history and input tax credit detail, as part of scope rather than as an afterthought. Prior period returns still reconcile after the move.
Where is our data during the migration?
In Canada. Client data is processed in Canada for the duration of the engagement, and your NetSuite account is retained read-only. Nothing on the source side is deleted by us.
Does payroll come across?
Basic payroll migration is included, carried at summary level so the general ledger stays correct. Detailed payroll history stays in the source system, which is what most Canadian year-end and audit processes expect.
QuickBooks Online or QuickBooks Enterprise?
That is a discovery decision, not a preference. Entity count, inventory complexity, user count and how you report determine which destination fits. If neither fits, we will say so on the call.
Is a NetSuite migration reversible if something goes wrong?
Your NetSuite account is retained read-only and nothing on the source side is deleted by us. Cutover happens only after your controller has signed off the reconciliation on a test conversion, so the decision point comes before the switch, not after it.
How much detailed history can we bring?
Standard scope is full open items plus two to three years of detailed transactional history, with earlier years carried as opening balances by period. Deeper history is possible and is priced during discovery rather than assumed, because volume drives the cost.
We run several provinces with different sales tax. Is that a problem?
No, but it has to be scoped. HST provinces, GST plus PST provinces with their own registrations, and Quebec with QST are mapped to separate tax codes tied to the correct registration and filing obligation.
What happens to our integrations?
Every system authenticating against NetSuite is inventoried in discovery, and each gets an explicit decision to repoint, replace or retire. Nothing is left to be discovered in the week after cutover.
Can our accounting firm run this and keep the client?
Yes. Refer, white-label or co-deliver. The terms are written down and the engagement routes back to the firm. We do not take your client.
Accounting firm with a client on this platform?
Refer, white-label, or co-deliver the migration with our team while you keep the client relationship.
Playbooks
Before you decide, read the mechanics
Short, checkable pieces on the contract clauses and system limits that usually decide this. Each one names a document or a report you already own.
The uplift clause costs more than the discount you win
A 6 percent discount erased by a 7 percent annual escalator. All three years priced out, and the four documents to pull before you respond to a renewal.
Your renewal did not go up, your discount ran out
Why a 20 percent introductory discount unwinds as a 25 percent increase, and where in the original order form that condition is written.
Discovery Call
Book a NetSuite discovery call
Bring your renewal date. We scope the move, quote a fixed price, and tell you plainly if staying put is the better deal.
