Switching from ADP or Gusto: what QuickBooks asks for first

The payroll switchover is the step where many small businesses stall. The question that keeps appearing among owners leaving ADP or Gusto for QuickBooks is a practical one: what has to be handed over before the first paycheck can run? What resolves it, we found, is a short list of provider documents and an automated import, not a weekend of retyping.

The stall before the first check

Reluctance here is understandable. A payroll history carries months or years of sensitive employee data, and a single mistyped figure can resurface on a pay stub or a tax form. Manual re-entry is slow and error-prone, which is why the migration step is where enthusiasm for a new provider tends to cool.

Community threads about the move describe the same choke point. The new account exists, the old provider is still cutting checks, and the history sits in limbo between the two.

Documents to gather before you begin

Two items start the process: your business information and the first pay date you intend to run under the new service. You also need two reports from your outgoing provider. Switchers leaving ADP should pull their employee summary and an earnings record. Switchers leaving Gusto need an employee summary and a payroll journal.

One detail saves people time. Bank and tax details are not part of the initial handover; they are added later in setup. Digging out account numbers on day one is wasted effort.

File formats are fixed. An employee summary can arrive as a PDF or a CSV. Payroll history must be a PDF. Files go up exactly as the provider issued them, without cleanup on your end, and each one is capped at 20 MB.

Where does the switch actually begin?

Naming matters here, because the flow sits somewhere unexpected. The switch starts inside QuickBooks Workforce, the app employees otherwise use to view pay stubs and tax forms. It does not start in the settings of the payroll product itself. The paychecks will run through QuickBooks Online Payroll, and the imported history lands there once the move is finished. Keeping the two names straight prevents real confusion during setup.

The import and the human review

Once the files are uploaded, QuickBooks reads them and brings in employee records plus year-to-date history on its own. Most are ready to review in a few hours. Complicated histories can take longer.

Every migration then passes a human check. An Intuit payroll expert reviews the imported data before any of it reaches you, and that step runs on every migration, whatever plan you hold. The review happens upstream. What you open has already been looked at once.

The review grid respects your time. Only items needing attention are flagged, so you are not re-verifying fields that imported cleanly.

The fields that stay behind

One catch survives the automation. Outgoing providers blank out the most sensitive entries before export, so Social Security numbers and bank account details never arrive in usable form. Two routes close the gap. Employees can supply their own details after a secure invitation through Workforce, or you can type them into the review grid yourself.

The invitation route has a side benefit. Staff update their own banking information in a portal built for exactly that, and the sensitive numbers never pass through your keyboard.

A final gate remains. Confirm every imported employee and the full year-to-date history before running the first payroll under the new service. A short set of screening questions will also suggest a suitable plan and feature set if you have not chosen one.

The short version

The switchover problem is smaller than its reputation. Gather the two provider reports, upload them as issued, and let the import plus the expert review carry the load. The only manual work that reliably remains is the sensitive data the old provider would not export in the first place. Get that entered, confirm the history, and the first paycheck under the new service becomes routine rather than risky.