Payroll Cutover from QuickBooks Desktop to Online Without Breaking the Tax Year

A mid-year payroll move from QuickBooks Desktop to Online can split wage bases and orphan in-flight deposits; this playbook keeps the tax year whole.

A standard conversion from QuickBooks Desktop to QuickBooks Online carries your lists and your books, but it does not carry your payroll history. Wage bases, tax withholdings, and pending agency payments stay behind, and a careless cutover splits the tax year across two products. This playbook is how our engineers sequence that move so the year stays whole.

The right time to run this playbook

Start once the move itself is decided and payroll is the only remaining risk. The window opens after the last payroll of a quarter has been paid, transmitted, and reconciled. It closes on the date of the first payroll you plan to run in Online. A mid-quarter cut is possible, but it leaves one quarter's wages in two products, and every form covering that quarter then gets assembled by hand.

Do not begin while a direct deposit batch is in transmission. If the export fails repeatedly and ends without an error, more retries rarely tell you anything. At that point, a service-side QuickBooks data migration can convert the file away from the broken export path.

Phase 1: fix the boundary before you fix a date

List every scheduled check date through the end of the year. Mark the last one you will run in Desktop and the first you will run in Online. The year-to-date date for the whole migration is that last Desktop check date; every number that follows is stated as of it. Leave one full pay cycle between the conversion and the first live run. That gap is where you verify.

Phase 2: snapshot the Desktop side

Take a full backup in .qbb format and store it away from the working folder. This is rollback point one; anything that later goes wrong restores here. Then export, all as of the year-to-date date:

  • the payroll summary
  • the employee state taxes detail
  • the payroll item list, with rates and limits
  • the payroll liability balances
  • the direct deposit register

Note which transmitted deposits have not yet debited the bank. Keep the Desktop payroll subscription active through year end, because amending or late filing from the old side still needs it.

Phase 3: convert, then load the wage bases

Run the conversion normally. Employees arrive as records, but their wage history does not; the import has no payroll detail to draw from. Activate payroll in Online and set its year-to-date as-of date to the last Desktop check date. Enter each employee's totals from the snapshot: gross wages, federal tax withheld, social insurance wages and tax, state and local tax. Add each deduction as well, including retirement deferrals and pre-tax premiums.

Desktop payroll items do not convert. Recreate additions, deductions, and employer contributions in Online before the first run, so the first paycheck finds its pieces. Confirm any wage-base ceiling carried at the right figure instead of resetting to zero.

Phase 4: verify every employee, one by one

Set the Desktop payroll summary beside the Online employee list and tie each employee line by line: gross, each tax, each deduction. Then tie the company totals per quarter to the forms already filed; the two products combined must equal what was reported. We treat this tie-out as the gate for the whole migration. If a figure is wrong, edit the year-to-date entry itself. A journal entry fixes the ledger, not the wage record, and the year-end statement prints from the wage record.

Everything here stays editable until the first live payroll is submitted. That is rollback point two: corrections at this stage are cheap, and corrections after filing are not.

Phase 5: settle the payments still in flight

Finish the final Desktop direct deposit cycle completely before the switch: checks dated, transmitted, and debited. A batch still pending at cutover debits after the switch, so match that debit in Online against the liability that created it. Never void a transmitted deposit after the fact; a plain void erases wages that were actually paid.

Taxes accrued on the last Desktop payrolls but not yet due are the other trap. Pay them from Desktop where you reasonably can. If you must pay from the Online side, record the payment as a prior-period liability payment coded to the same liability account. Do not pay old taxes through Online's tax payment module; it applies the money to current Online liabilities and marks the wrong debt paid.

Phase 6: prove it with the first live run

Preview the first Online payroll before submitting anything. Inspect two employees closely: a long-tenured one near a wage-base ceiling, and a new hire with no year-to-date at all. The first should show the cap continuing from the carried figure. The second should show nothing inherited. Submit the run, then set one real stub beside that employee's last Desktop stub. If anything mismatches, stop before transmitting deposits.

How do you know the cutover worked?

  • Every employee's Online year-to-date equals the Desktop summary as of the chosen date.
  • Each quarter's wages sit entirely in one product, so no quarterly form needs hand assembly.
  • The first live run respected wage-base ceilings rather than resetting them.
  • Every in-flight deposit and tax payment matched to exactly one bank debit, with no duplicate or orphaned liability.
  • Each year-end wage statement shows one combined figure across both products.

Keep the retired Desktop file readable regardless; a later question about the year is best answered by a file that still opens, next to the backup and the printed reports.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.