Sage 300 and Accpac to QuickBooks
Your GL segment structure is your reporting model. Move it wrong and nothing reconciles.
Sage 300 is a capable ERP that a great many Canadian organizations outgrew in the wrong direction. The migration is not hard because of transaction volume. It is hard because segments, optional fields and the Tax Services module encode twenty years of reporting decisions that have to arrive intact. We have done this one before, including for a national organization off a corrupted Sage 300 environment in four weeks.
15,000+ migrations completed. 90+ source platforms. Client data processed in Canada.
Lineage
If your system says Accpac, this page is about your system
Few products have been renamed as often. The data structures underneath have been broadly stable throughout, which is why a file created under one name migrates the same way as a file created under another.
| Year | Name |
|---|---|
| 1976 | EasyBusiness Systems |
| 1987 | Accpac Plus, under Computer Associates |
| 2004 | Sage acquires the product line |
| 2006 | Sage Accpac ERP |
| 2009 | Sage ERP Accpac |
| 2012 | Sage 300 ERP |
| Later | Sage 300 and Sage 300cloud |
Resellers outside North America still market it as Accpac. If you are running Accpac Plus on a Pervasive or Btrieve database, say so on the first call. It changes the extraction sequence, not whether the project is possible.
The technical centrepiece
Segments are a structure, not a preference
This is the section worth reading twice. Everything else on this page is execution. This is the part that decides whether your reports still work.
What segments actually are
Sage 300 splits the account number into segments: account, department, division, region, cost centre, whatever your implementation chose in year one. Reports are built by rolling up and filtering on those segments. Your board pack, your divisional profit and loss, your funder reporting all sit on that structure.
Sage caps how many segments you get by edition, and changing the segment structure after implementation is effectively a re-implementation. That is why the structure you have is almost always the structure you were given, not the structure you would choose today.
Why that matters on the way out
QuickBooks does not have segments. It has accounts, classes, locations, projects, custom fields and tags. Moving a four-segment Sage 300 chart into that model is a design decision made once, and if it is made mechanically you get a chart of accounts with thousands of entries that nobody can report on.
We work backwards from your reports instead. Which segments appear in the pack that leaves the building, which are dead, and which are really doing the job of a location or a project. Then we design the destination to reproduce those reports, and we prove it by running both side by side before cutover.
Optional fields carry more than you think
Sage 300 optional fields get used for everything the core system did not anticipate: funder codes, contract references, asset tags, approval routing. They are frequently undocumented and frequently load bearing. We inventory them and map the live ones to custom fields, classes or projects rather than discovering them missing after go live.
The manufacturing question answers itself
Sage 300 has no first-party manufacturing module. If you are manufacturing today you are already running a third party application alongside it. That is genuinely useful information, because it means the manufacturing capability was never the reason you were on the ERP, and the destination question becomes much simpler.
Discovery
Which edition you are on changes the project
The three Sage 300 editions carry hard limits, and those limits tell us most of what we need before we open the file.
| Edition | Companies | Users | GL segments | What it changes for the migration |
|---|---|---|---|---|
| Standard | 5 | Up to 5 | 3 | Simplest segment model and the fastest migration we run on this platform |
| Advanced | Unlimited | Up to 10 | 4 | Multiple companies usually means a consolidation decision as much as a migration |
| Premium | Unlimited | Unlimited | 10 | Up to ten segments and unlimited account structures. The destination design work is the project |
If you are on Advanced or Premium with several company databases, the first question is whether you want one set of books at the end or several. That is a business decision, and it changes the scope more than anything technical.
Scope
What moves, module by module
Sage 300 is modular, and each module carries its own data model. The second half of this table is the part that decides whether the project goes well.
| Module or item | Outcome | How we handle it |
|---|---|---|
| General Ledger accounts and segments | Remodelled | Segment structure mapped to accounts, classes, locations and projects based on your live reports rather than mechanically flattened |
| GL transactions and batches | Moves | Full history at transaction level with original posting dates, batch references and source ledger codes preserved |
| Accounts Receivable | Moves | Customers, ship-to locations, invoices, receipts, adjustments and applied detail, with aged ageing reconciled to source |
| Accounts Payable | Moves | Vendors, remit-to locations, invoices, payments and applied detail, with aged ageing reconciled to source |
| Optional fields | Remodelled | Inventoried across every module, live ones mapped to custom fields, classes or projects, dead ones dropped with your sign-off |
| Multicurrency and rate history | Moves | Currencies enabled deliberately in the destination, with realised and unrealised exchange positions reconciled rather than flattened to domestic |
| Tax Services setup | Rebuilt | Tax authorities, tax classes and tax groups rebuilt as GST, HST, PST and QST codes against the correct Canadian agencies |
| Inventory Control | Moves, with a decision | Items, categories, quantities and cost. Destination costing method is fixed the first time inventory is enabled and cannot be changed after, so it is agreed in writing first |
| Order Entry and Purchase Orders | Partially | Open orders and POs converted. Sales orders have no destination equivalent and become estimates, with the fulfilment workflow redesigned with your team |
| Project and Job Costing | Remodelled | Contracts, projects and categories mapped to customers, sub-customers and classes, then reconciled on project profitability against the source |
| Bank Services | Partially | Bank accounts and reconciled status move. Historical reconciliation reports do not and are archived as PDFs |
| Intercompany Transactions | Redesigned | Intercompany routing has no direct equivalent. Modelled explicitly during destination design, and central to any consolidation decision |
| Canadian Payroll | Basic only | Basic payroll data migrated. Detailed pay type and year to date history archived from the source rather than partially rebuilt |
| Crystal Reports and Sage Intelligence | Does not move | The reports that leave the building are rebuilt and tested against the Sage 300 source. The rest are archived rather than recreated |
| Macros and customisations | Does not move | Inventoried, then each is replaced natively, replaced with a connected application, or explicitly dropped with your sign-off |
| Third party ISV modules | Assessed | Manufacturing, warehouse, EDI and similar bolt-ons are assessed for a destination equivalent, and the replacement is scoped and costed inside the same project |
| Attachments and documents | Does not move | Extracted into a structured archive keyed to the original records |
| Users and security groups | Does not move | Roles redesigned in the destination and users re-invited |
Canada
The Canadian details a generic Sage 300 plan misses
Tax Services is a three-part structure, not a rate
Sage 300 models tax through the Tax Services module: tax authorities, tax classes and tax groups combining to produce the rate applied to a transaction. Canadian implementations use that structure to represent GST, HST, PST and QST, and every implementation does it slightly differently.
Translating it means reading how yours was actually configured rather than assuming a standard. Get it wrong and historical transactions arrive under the wrong authority, which is precisely the detail that makes a filed return impossible to reproduce.
The rates are nine different answers
HST at 13 percent in Ontario. 14 percent in Nova Scotia. 15 percent in New Brunswick, Prince Edward Island and Newfoundland and Labrador. GST plus PST in British Columbia at 7 percent, Saskatchewan at 6 percent and Manitoba at 7 percent. GST plus QST in Quebec at 9.975 percent. GST only in Alberta, Yukon, the Northwest Territories and Nunavut. Every historical transaction keeps the code it was filed under.
Input tax credits have to be reproducible
A Sage 300 environment usually sits on many years of filed returns. Move summary balances and you can file going forward but cannot substantiate what was already filed. We migrate at transaction level specifically so the ITC position for every filed period can be rebuilt, and we reconcile a sales tax summary from both systems before go live.
Canadian Payroll is a separate module on its own cycle
Sage 300 Canadian Payroll is distinct from the US module and carries its own tax table updates, released around 1 January and 1 July. If you are running it, the annual update dependency is part of what you are paying for and part of what you are leaving. Our scope is basic payroll data migrated and detailed history archived.
Six years, at a Canadian place of business
The CRA requires records to be kept for six years from the end of the last tax year they relate to, and to be kept at your place of business in Canada unless you have written permission otherwise. A retired Sage 300 database that needs a Sage licence to open is not an archive. We deliver a structured, readable one.
Your data is processed in Canada
Extraction, staging, transformation and validation all happen in Canada. We do not move a Canadian client file offshore to be worked on, and it goes in the statement of work rather than being asserted on a web page.
Destination
QuickBooks Online Advanced, or QuickBooks Enterprise
Leaving Sage 300 is two decisions. The second one is where you land, and it gets made badly most often because it gets made by whoever is selling the migration.
QuickBooks Online Advanced fits most Sage 300 exits
Unlimited classes and locations, unlimited chart of accounts, 25 billable users plus 3 accountant users, custom fields and workflow automation. For a Standard or Advanced edition site running general ledger, receivables, payables, some inventory and a reporting pack, that is the workload, and you lose the server, the annual upgrade and the consultant dependency in one move.
This is the destination in the Dairy Farmers project below, and it is where most of these migrations land.
QuickBooks Enterprise fits some Premium sites
Heavy inventory with bin, lot or serial tracking, or job costing at construction depth, sometimes needs a desktop-grade destination. Enterprise carries up to 40 concurrent users and advanced inventory that browser accounting does not match natively.
It also carries a per seat licence and, if your team is not all on one network, a hosting bill. That is the same shape of cost you are leaving Sage 300 to escape, so it only makes sense when the capability is genuinely load bearing. We will look at your inventory and job cost reports and tell you which one you are.
We turn Sage 300 migrations down. If your segment model, intercompany routing or ISV stack genuinely needs an ERP, staying is the right answer and you will hear it on the first call rather than in month three.
Process
How a Sage 300 migration runs
Assessment
We take a copy of the database and profile it: edition and version, modules carrying live transactions, segment structure, optional fields, currencies, Tax Services configuration, ISV modules and the reports that leave the building. Output is a written scope with the exclusions named and signed.
Destination design
The segment to class, location and project model. Chart of accounts, tax codes and agencies, item structure, custom fields, user roles. Designed against your reporting rather than mirroring Sage 300.
Extraction and remediation
Data extracted and audited across every module. Long-lived Sage 300 databases carry retired segment values, repurposed accounts and cross-module inconsistencies, and those are resolved inside the migration where they can be reconciled.
Test migration
Full conversion into a sandbox. Trial balance, balance sheet, profit and loss, AR and AP ageing, sales tax summary, project profitability and inventory valuation reconciled line by line against Sage 300. You receive the comparison and sign off.
Cutover
Final delta migration in a quiet window. Your team keeps working in Sage 300 until we switch. Reconciliation repeats against the final numbers before anyone is asked to use the new system.
Hypercare and archive
Thirty days of support after go live, role training and your first month end with us on the line. The Sage 300 database is archived in a structured, readable form to meet the six year requirement.
Timeline
How long it takes
Timelines reflect the segment model, the module count and the consolidation decision rather than transaction volume.
| Profile | Timeline |
|---|---|
| Standard edition, single company, three segments, financials only | 1 to 2 weeks |
| Advanced edition, multicurrency, inventory and order entry, project costing in use | 2 to 5 weeks |
| Premium edition, multiple companies consolidating, deep segment model, ISV modules to replace | 4 to 8 weeks |
Those windows run from kickoff to go live and include the test migration and the reconciliation cycle. They exclude the thirty days of hypercare that follow every project. Software subscriptions are paid to Intuit directly and are never marked up by us.
Proof
We have run this exact migration for a national organization
Most proof points on migration pages are adjacent. This one is not. Same source platform, same destination, and the source environment was in worse shape than yours.
Dairy Farmers of Canada
The national organization representing more than 9,000 dairy farms across every province moved from an on-premise Sage 300 environment to QuickBooks Online Advanced. Zero days of downtime, complete data integrity, four weeks to go live.
The Sage 300 environment had developed data corruption across General Ledger, Accounts Payable and Accounts Receivable, each with its own database structure and cross-references. We provided a production file so the organization kept operating while the corruption was identified and resolved, restructured the chart of accounts to use class and location tracking properly, and reconciled every balance against the source before anything entered production.
“The major risk was dealing with data corruption in our Sage 300 system. SaaS Direct was flexible in providing a production file so our business could continue operating while they resolved the data issues. The team has really improved the service.”
Abdou Doumbia, Financial Controller, Dairy Farmers of Canada
Questions Canadian finance teams ask
Before you book
Is Accpac the same product as Sage 300?
Yes. The line ran from EasyBusiness Systems in 1976 to Accpac Plus in 1987, then through Sage Accpac ERP and Sage ERP Accpac before becoming Sage 300 ERP in 2012. Same lineage and broadly the same data structures, so everything here applies to an Accpac file.
What happens to our GL segments?
They are remodelled, not flattened. We work backwards from the reports you actually distribute to identify which segments are live, then map those to accounts, classes, locations or projects in the destination. A mechanical conversion produces a chart of accounts nobody can report on, which is the most common way these projects fail.
We have several company databases. Can you consolidate them?
Yes, and that is usually the more valuable half of the project. Whether you end with one set of books or several is a business decision we make with you in discovery, and it affects scope more than any technical factor.
Will our GST, HST, PST and QST history survive?
Yes, when the conversion runs at transaction level. Sage 300 Tax Services authorities, classes and groups are translated into Canadian tax codes against the correct agencies, and we reconcile a sales tax summary from both systems before go live so you can see the position.
What about our optional fields?
Inventoried across every module. Canadian sites commonly use them for funder codes, contract references and asset tags, and they are usually undocumented. Live ones are mapped to custom fields, classes or projects. Dead ones are dropped with your sign-off rather than silently.
Do you migrate Sage 300 Canadian Payroll?
We migrate basic payroll data. Detailed pay type history and year to date figures are archived from the source rather than partially rebuilt in the destination, because a half populated payroll history inside a live file causes more problems than it solves.
Our Crystal Reports are business critical. What happens to them?
They do not convert. We inventory the report library before cutover, rebuild the ones that leave the building and test them against the Sage 300 source, and archive the rest. On most Sage 300 sites the archive is the larger half, and not rebuilding it is a real part of the saving.
What happens to the Sage 300 database afterwards?
It is archived in a structured, readable form and handed to you, built to meet the CRA requirement to keep records for six years at a place of business in Canada unless you have written permission otherwise. A backup that needs a live Sage licence to open does not satisfy that.
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.
Seven things to export before you cancel Sage Intacct
Dimensions, allocation logic, statistical accounts and attached documents do not come out in a CSV, and the API dies with the contract.
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.
Discovery Call
Book a Sage 300 migration assessment
Ninety minutes on your edition, your segment structure, your modules in use and your Tax Services setup. A fixed-scope quote after, or an honest recommendation to stay on the ERP.
