Why businesses are moving now
As of 2026, Intuit has been steadily narrowing its QuickBooks Desktop line, ending new sales of several editions in some markets, moving remaining customers to subscriptions and retiring older versions on a regular schedule. Once a version is retired, add-on services such as payroll and bank feeds stop working with it. For many businesses the question is no longer whether to move, but when and where.
The usual destinations are QuickBooks Online, another cloud accounting product, or a system built for businesses that relied on Desktop’s depth: inventory, multiple users with different permissions, job costing and a menu-driven workflow. Make the list of features you actually use in Desktop before you shop. Inventory assemblies, sales orders, progress invoicing, multiple currencies and custom reports are the features most likely to be missing or different elsewhere.
Pick a cutover date
The cleanest cutover is the first day of a new fiscal year. Your old file holds every completed year, the new system starts with opening balances, and year-end reporting never straddles two systems. If that is too far away, the start of a quarter is the next best option, especially for GST/HST quarterly filers, because each return will come entirely from one system.
Avoid switching in the middle of a month or close to a busy season. Leave a buffer: plan the migration a few weeks before the cutover date so you can run a test migration, check it and fix problems while the old system is still your system of record.
Payroll needs special attention. If you switch payroll systems mid-year, you must bring each employee’s year-to-date earnings, deductions and remittances into the new system, or T4 slips will be wrong. Switching payroll on January 1 avoids that.
Clean up the QuickBooks file first
A migration copies what is in your file, including its mistakes. Spend time cleaning up before you move. Reconcile every bank and credit card account up to the cutover date. Clear out the undeposited funds account, which often holds old payments that were never matched to a deposit. Review open invoices and bills, and write off or void items that will never be paid.
Make inactive any customers, suppliers, items and accounts you no longer use, and merge duplicates. Run Verify Data and Rebuild Data in QuickBooks Desktop to repair internal inconsistencies. Then print or save the reports you will use to check the migration: trial balance, balance sheet, profit and loss, A/R and A/P aging, and inventory valuation, all as of the cutover date.
- Reconcile all bank and card accounts to the cutover date
- Empty undeposited funds
- Clean up stale open invoices and bills
- Inactivate unused lists and merge duplicates
- Run Verify and Rebuild Data
- Save trial balance, aging and inventory reports as of cutover
Decide what to bring across
You do not have to move everything. The minimum is your lists (chart of accounts, customers, suppliers, items with costs and prices), opening balances for every balance sheet account, open invoices and bills so you can collect and pay them, and inventory quantities and values. Many businesses also bring a year or two of transaction history so they can compare periods without opening the old file.
Keep the old QuickBooks file. Make a final backup, keep a licensed copy available for reference for as long as you need it, and remember that the CRA expects you to keep records for six years. Export key reports to PDF in case the software ever becomes unavailable.
Run a dry run, then prove it to the penny
Do a test migration first. Import into a trial or sandbox company, then compare the new system’s trial balance, aging reports and inventory valuation with the reports you saved from Desktop. Every account should match to the cent. If one is off, find out why before the real migration. Common causes are tax codes that map differently, items with negative quantities, and transactions dated after the cutover that slipped in.
SeroBooks includes a QuickBooks Desktop migration with a dry run, so you can see what will come across and check the results before you commit. Its export is penny-verified against the source file. In one migration of a live seller’s QuickBooks Desktop file, the comparison showed $0.00 variance. Accountants can be invited at no charge with practice seats to review the result.
Train the team on the new workflow
Change is hardest for the people who enter transactions every day. Walk each person through their daily tasks in the new system: entering bills, receiving payments, creating invoices, receiving inventory. Write a one-page cheat sheet that maps the old menu path to the new one for the ten things they do most.
Familiarity helps. SeroBooks offers a desktop-style workspace with menus that will feel familiar to QuickBooks Desktop users, plus native apps for Windows, macOS and Android and a web app, so staff who are used to a desktop program are not forced into a browser tab. Set roles and permissions before go-live so each person sees only what they should.
Bringing payroll and sales tax across
If you run payroll in QuickBooks Desktop, decide whether payroll moves at the same time as accounting. Moving both on January 1 is simplest. If you move accounting mid-year but payroll later, keep payroll running in the old system until year-end, file T4s from it, and post payroll journals into the new system each pay period in the meantime.
If payroll must move mid-year, load each employee’s year-to-date gross pay, CPP, CPP2, EI, income tax, vacation accrued and taxable benefits into the new system as of the cutover date. Check those totals against the old payroll reports and against remittances on your CRA account, because errors here appear on the T4 in February. SeroBooks Pro includes Canadian and US payroll in the same ledger, and SeroPayroll is available on its own if you prefer to keep payroll separate.
For sales tax, make sure the GST/HST, PST or QST payable and receivable balances come across as opening balances, and that any return for a period before cutover is filed from QuickBooks. The first return from the new system should cover only periods that started after cutover.
Go live and run the first close
On cutover day, do a final migration of open items and balances, lock the old file against new entries, and start recording everything in the new system. For the first month, close the books carefully: reconcile the bank, compare sales tax figures and review the P&L line by line against the same month last year. Small mapping issues usually show up in the first close and are easy to correct then.
After one clean month-end, the migration is done. Our month-end close checklist is a good guide for that first close in the new system.