Payroll migration is the operational process of moving employee records, payroll history, tax information, deductions, benefits data, and system settings required to run payroll accurately into a new system.
The work involves more than importing a spreadsheet. Before the first live payroll, the new system must correctly calculate gross pay, taxes, deductions, employer liabilities, net pay, payroll funding, and year-to-date totals. Your team must also know which provider will make each tax deposit, file each return, and prepare each year-end form.
This payroll migration checklist divides the transition into three phases: prepare, migrate, verify, and go live. It applies when moving between online platforms, replacing manual or spreadsheet-based payroll, or consolidating payroll work currently spread across several systems.
Use it as the companion to How to Switch Payroll Providers, which covers timing, provider evaluation, and the broader decision to switch.
Important: Payroll, tax, benefits, and recordkeeping responsibilities vary by provider, jurisdiction, contract, and service model. Confirm account-specific requirements with both providers and consult a qualified payroll, tax, benefits, accounting, or legal professional when necessary.
What is payroll migration?
Payroll migration is the process of transferring and recreating the information, records, and configurations needed to calculate, pay, record, and report payroll in a new system.
The migration may include:
Business and payroll-tax account information
Employee and contractor records
Pay rates and pay schedules
Year-to-date wages and taxes
Pre-tax and post-tax deductions
Employer contributions
Garnishments and support orders
Paid time off balances and policies
Benefits and retirement elections
Direct-deposit setup or reauthorization
Accounting and general-ledger mappings
Time-tracking and HR integrations
Historical payroll and tax records
Switching payroll providers is the business decision to replace one service with another. Payroll migration is the technical and operational work required to make the replacement system accurate and ready to use.
Migration complexity generally increases when a business has:
Employees in multiple tax jurisdictions
Several pay schedules or legal entities
Numerous earnings and deduction types
Benefits or retirement plans
Active garnishments
Custom job-costing or accounting rules
Multiple connected HR and finance systems
A professional employer organization, or PEO, relationship
Payrolls already processed during the current calendar year
When is the best time to migrate payroll?
The first check date of a new calendar year is often the simplest migration point because the replacement provider does not need to incorporate payrolls from earlier in that year.
A quarter boundary may also create a clearer reporting checkpoint because federal Form 941 and many state payroll returns cover quarterly periods. It does not eliminate the need to transfer annual wage information, unemployment tax data, account authorizations, or the responsibility for year-end forms.
A mid-year payroll migration is workable, but it requires complete information for every earlier check date in the calendar year. The business must also determine which provider or party will handle:
Payroll-tax deposits
Quarterly returns
State unemployment payments
Local payroll taxes
Corrections and amendments
Form 940
Forms W-2 and W-3
Forms 1099
Tax notices for periods before the switch
Choose a target date based on the actual work involved, not the calendar alone. Consider:
Upcoming check dates and processing deadlines
Provider onboarding requirements
Bank verification and payroll-funding lead times
State and local tax registrations or authorizations
Contract termination and notice provisions
Benefits, retirement, and workers’ compensation transitions
Staff availability
Bonuses, commissions, open enrollment, or year-end processing
The amount and quality of historical data that must be transferred
Who should manage a payroll migration?
One person may hold several roles at a small business, but every responsibility should still have a named owner.
Role | Primary responsibility |
Project lead | Maintains the timeline, coordinates providers, tracks decisions, and approves go-live |
Payroll administrator | Exports records, recreates settings, validates calculations, and runs payroll |
Finance or tax reviewer | Reconciles wages, tax liabilities, deposits, returns, funding totals, and accounting entries |
HR or benefits owner | Verifies worker records, deductions, paid time off, benefits, retirement, and garnishments |
IT or integration owner | Reconnects systems, tests data flows, and reviews user access and permissions |
Provider contacts | Explain import formats, setup requirements, deadlines, tax responsibilities, and unresolved issues |
Create one controlled migration tracker for deadlines and decisions. Do not place Social Security numbers, full bank-account numbers, tax credentials, or other protected payroll data in an unsecured project spreadsheet.
Payroll migration checklist
Phase 1: Prepare
1. Define the migration scope
Owner: Project lead
Dependency: The replacement provider or system has been selected.
Document exactly what must move or be recreated. Payroll may connect to time tracking, scheduling, benefits, retirement, workers’ compensation, expense management, HR records, and accounting software.
List the:
Legal entities
Employees and contractors
Active and terminated workers paid during the year
Work locations
Tax jurisdictions
Pay groups and schedules
Benefit and deduction programs
Accounting dimensions
Required integrations
Separate first-payroll requirements from improvements that can wait until after launch.
Complete when the internal team and both providers understand what is included, what is excluded, and what is required before the first live payroll.
2. Audit the current payroll configuration
Owner: Payroll administrator
Document the current production setup before changing it:
Pay schedules, periods, and check dates
Salaried, hourly, commission, bonus, tip, and other earnings
Overtime and multiple-pay-rate rules
Pre-tax and post-tax deductions
Employer contributions
Benefits and retirement deductions
Garnishments and support orders
Paid time off policies and balances
Federal, state, and local tax jurisdictions
State unemployment insurance accounts and rates
Workers’ compensation settings
Job, project, department, and location codes
General-ledger mappings
Administrator roles and approval rules
A general ledger mapping is the set of rules that maps payroll wages, taxes, deductions, reimbursements, and liabilities to the appropriate accounts in an accounting system.
Complete when: The audit reflects the active payroll setup and someone other than the preparer has reviewed it.
3. Review the existing contract and exit process
Owner: Project lead or authorized account administrator
Review the signed agreement, order form, renewal notice, and product-specific terms. Confirm:
The authorized cancellation method
Any notice period
The contract end or renewal date
Final billing rules
Data-export procedures
How long will administrator access continue
Responsibility for unfinished deposits and filings
Responsibility for W-2s, 1099s, and amendments
Separate termination requirements for add-ons
Effects on benefits, retirement, workers’ compensation, or other connected services
Tell the former provider that you are moving payroll to another system and ask how the transition affects each open tax, benefits, and reporting responsibility.
Do not assume that canceling the core payroll subscription automatically cancels every connected service.
Complete when: The company has a documented service end date and written confirmation of the former provider’s remaining responsibilities.
4. Build the migration schedule
Owner: Project lead
Work backward from the first planned check date in the new system. Include deadlines for:
Final payrolls in the old system
Data exports
Tax-account setup and authorization
Employee setup
Bank verification
Payroll funding
Benefits and deduction configuration
Integration testing
Data reconciliation
Payroll preview or parallel testing
Employee communication
Go-live approval
Contract cancellation
Allow time to correct rejected files, missing registrations, bank-verification issues, and calculation discrepancies. Do not rely on a generic implementation estimate unless both providers have confirmed it for your account.
Complete when: Every milestone has an owner, a due date, a dependency, and an escalation contact.
5. Establish change control
Owner: Payroll and HR leads
Track changes made after the initial export, including:
New hires
Terminations
Raises
Address or work-location changes
New benefit elections
Bank-account changes
New or modified garnishments
Paid time off adjustments
Voids, reversals, and manual checks
A short data-freeze period may help, but payroll activity rarely stops completely. Maintain one authoritative change log rather than relying on email threads or memory.
Complete when: Every change between the initial export and go-live has been recorded and reflected in the appropriate systems.
Phase 2: Migrate
6. Export payroll and employee data
Owner: Payroll administrator
Export records before canceling service or losing administrator access. Depending on the business and provider, the migration package may include:
Legal business name and federal employer identification number, or FEIN
State and local tax account numbers
State unemployment insurance rates
Employee and contractor rosters
Hire and termination dates
Compensation and pay rates
Tax-withholding elections
Payroll registers and pay statements
Year-to-date wages, taxes, deductions, and contributions
Forms 941, 940, W-2, W-3, and 1099
State and local returns
Tax-deposit confirmations
Garnishment and support-order records
Paid time off balances
Benefits and retirement elections
Accounting mappings and payroll journals
Employee documents and authorizations
Audit or change records when available
Include terminated employees and anyone paid earlier in the calendar year, even when they will not be active in the new system.
Confirm how direct-deposit data will be handled. Some reports mask bank account information, and the replacement provider may require employees to enter or reauthorize their banking details securely.
Complete when: The export covers all workers, entities, jurisdictions, check dates, deposits, and filings needed for setup and record retention.
7. Create a secure backup outside the old platform
Owner: Payroll administrator and IT owner
Keep an independent copy of:
Original export files
Payroll registers
Pay statements
Quarterly and annual tax forms
Tax-payment confirmations
Configuration records
Provider correspondence
Contract and cancellation documentation
Use access controls and encryption appropriate for sensitive payroll information. Preserve the unmodified source files even after cleaning or converting them so the business has an audit trail.
Federal employment tax records generally must be retained for at least 4 years. Other federal, state, employment, benefits, litigation, or business requirements may require longer retention.
Complete when: Authorized staff can reach a secure, unmodified backup without signing in to the former provider.
8. Clean and reconcile the source data
Owner: Payroll administrator and finance reviewer
Check for:
Duplicate workers
Missing Social Security numbers or taxpayer identification numbers
Incorrect active or terminated status
Outdated home or work addresses
Missing check dates
Inconsistent earnings or deduction names
Incorrect state unemployment rates
Unrecorded voids or reversals
Missing garnishments
Payrolls processed outside the primary system
Workers assigned to the wrong legal entity
Current-year workers are omitted because they are no longer active
Reconcile completed quarters to the applicable Forms 941 and state returns. Reconcile the current quarter to payroll registers, tax-liability reports, and tax-payment records. Then compare full-year totals with the system’s year-to-date reports.
Do not use a single Form 941 as a year-to-date payroll ledger. Form 941 reports federal employment tax information for one quarter and does not provide the employee-level history needed for migration.
Complete when: Payroll, tax, funding, and accounting totals tie to the authoritative records, and each unresolved discrepancy has an owner.
9. Map fields between the systems
Owner: Payroll administrator and implementation contact
Create a mapping document showing how each required source field will appear in the new system.
Old-system field | New-system field | Conversion or decision |
Regular Hourly | Regular earnings | Direct match |
Medical Pre-Tax | Medical deduction | Confirm tax treatment |
Location 02 | Providence office | Rename |
Custom Dept. A | Operations department | Create a new department |
Unsupported custom field | No equivalent | Preserve separately or redesign |
Pay particular attention to:
Pre-tax versus post-tax treatment
Employer and employee contribution rules
Annual contribution limits
Local tax codes
Job-costing structures
Custom fields
Department and location hierarchies
Paid time off accrual rules
Garnishment balances and priorities
Two fields with similar names may not use the same calculation or tax treatment.
Complete when every launch-critical field has a destination, a conversion rule, or a documented exception.
10. Import data and configure the new system
Owner: Payroll administrator and new-provider contact
Import the records that the new system supports and manually configure anything that cannot be transferred. Set up:
Pay schedules and first check dates
Earnings and pay rates
Deductions and employer contributions
Tax accounts, rates, and filing frequencies
Paid time off policies and opening balances
Garnishments
Benefits and retirement deductions
Direct-deposit settings
Departments, locations, jobs, and projects
Accounting mappings
Administrator permissions
Payroll approval workflows
Employee self-service access
Do not assume that an employee or payroll-history import will automatically create deductions, benefits, contributions, accounting mappings, or other payroll rules.
Complete when: The new system contains the records and settings needed to calculate a complete payroll preview.
11. Reconnect and test integrations
Owner: IT or integration owner
Reconnect each required system separately, including:
Time tracking
Scheduling
Accounting
HR systems
Retirement providers
Benefits systems
Expense tools
Workers’ compensation
Point-of-sale systems
Identity or provisioning systems
For each connection, confirm:
Which system owns each data field
Whether data moves in one direction or both
Sync timing
Employee and account matching
General-ledger mappings
Error notifications
Historical-data behavior
User permissions
How corrections and reversals sync
An integration appearing as active does not prove that every record or field is moving correctly. Test actual transactions and review the result in the receiving system.
Complete when: Each required integration has passed a documented end-to-end test.
Phase 3: Verify and go live
12. Verify the migrated records
Owner: Payroll administrator and finance reviewer
Compare the new system with the final approved source data. Review every employee’s high-risk fields:
Employment status
Pay type and pay rate
Work and home tax locations
Federal and state withholding setup
Year-to-date wages and taxes
Pre-tax and post-tax deductions
Employer contributions
Garnishments
Paid time off balances
Direct-deposit status
Also compare:
Employee counts
Legal entities
Department and location assignments
Tax-account numbers
State unemployment rates
Payroll schedules
Accounting mappings
Administrator permissions
Do not rely only on spot checks for tax identification numbers, garnishments, year-to-date totals, or banking status. These fields should receive employee-level review.
Complete when: Differences have been corrected or formally accepted, and payroll and finance have approved the records.
13. Confirm tax-filing responsibilities
Owner: Finance or tax reviewer
Obtain written confirmation of who will handle:
Completed quarterly returns
The quarter containing the first new-system check date
Federal tax deposits
State and local deposits
State unemployment taxes
Form 940
Forms W-2 and W-3
Forms 1099
Corrections and amended returns
Tax notices relating to periods before the switch
Confirm that the replacement provider has the required:
Tax-account numbers
State unemployment rates
Deposit schedules
Filing frequencies
Agency authorizations
Signed forms
Prior payroll history
Proof of tax payments already made
Do not assume the provider registers the business in every jurisdiction unless that service is explicitly included.
Each deposit, return, amendment, and annual form should have one named responsible party. Avoid unintentionally authorizing two providers to file for the same period.
Complete when: Every tax responsibility has an owner and no period has been left unassigned or assigned twice.
14. Run a test or parallel payroll
Owner: Payroll administrator
Run a payroll preview in the replacement system and compare it with the expected results from the old system or a controlled calculation. A parallel payroll is a comparison exercise; it does not mean paying employees twice.
Compare:
Hours and gross wages
Overtime
Bonuses, tips, and commissions
Federal, state, and local withholding
Social Security and Medicare
Pre-tax and post-tax deductions
Garnishments
Employer payroll taxes
Employer benefit contributions
Paid time off balances
Net pay
Total payroll funding
Accounting entries
Investigate differences instead of automatically forcing the new system to match. A discrepancy may reveal an error in either the new configuration or the former setup.
Complete when: Material differences have been resolved, expected rounding differences are documented, and the project lead has approved launch.
15. Prepare employees for the change
Owner: HR or payroll lead
Tell employees:
The date of the first payroll in the new system
Whether the pay schedule or payment method will change
How to activate their accounts
How to verify personal and tax information
Whether they must re-enter direct-deposit details
Where to find pay statements and tax documents
Whom to contact about a problem
The deadline for completing the required setup
Do not ask employees to send bank account or tax information through ordinary email.
Complete when: Employees have received instructions, a deadline, and one clearly identified support contact.
16. Run and review the first live payroll
Owner: Payroll administrator and project lead
Before submission:
Review the payroll register
Confirm the funding amount
Check approval records
Verify the check date
Confirm the payment method
Review tax liabilities
Verify unusual or one-time earnings
After processing, confirm:
The payroll was accepted and funded
Employees received the expected net pay
Tax debits match the approved liabilities
Direct deposits or checks were issued
Accounting entries were posted correctly
Benefits and retirement deductions were transmitted as expected
Employees can access pay statements
Integrations did not create missing or duplicate records
Maintain an escalation plan for funding or payment problems. Identify provider support contacts, authorized internal decision-makers, bank contacts, and any approved emergency-payment procedure.
Complete when: Employees have been paid, and payroll, tax, funding, accounting, and integration results match the approved run.
17. Monitor the first two or three payroll cycles
Owner: Project lead and payroll administrator
Review the early payrolls more closely than routine runs. Track:
Rejected tax registrations
Tax notices
Incorrect withholding
Deduction or contribution differences
Garnishment problems
Paid time off balance changes
Integration failures
Accounting reconciliation issues
Employee account-access problems
Unexpected provider invoices
Outstanding responsibilities from the former provider
Keep the old account active only as long as the contract, access policy, and transition plan require it. Before closing it, confirm that all needed records have been exported and all remaining filing and benefits responsibilities are documented.
Complete when: Early payrolls reconcile correctly, open issues have owners, and the former account can be closed without losing records or interrupting another service.
Migrating from manual or spreadsheet payroll
A business moving from spreadsheets, handwritten records, or a mostly manual process will not have a standardized system export. It must build a reliable source file from the records used to calculate, pay, and report payroll.
Gather:
Forms 941 for each completed quarter
Form 940 and prior year-end forms, when relevant
State and local payroll returns
Federal, state, and local deposit confirmations
Current-quarter payroll registers or calculation sheets
Bank and check records
Employee Forms W-4 and state withholding forms
Pay rates and compensation agreements
Deduction and contribution records
Garnishment orders
Paid time off balances
Employee and contractor payment history
Forms 941 provide quarterly company totals, not a complete year-to-date employee payroll ledger. Reconstruct employee-level and check-date history from payroll calculations, pay records, and payment documentation rather than relying only on tax forms or bank withdrawals.
Ask the replacement provider for its import or setup template before building the final file. The template can reveal missing fields and reduce unnecessary reformatting.
Require an independent review of manually reconstructed payroll history before importing it.
Common payroll migration challenges and how to avoid them
Challenge | Preventive action |
Incomplete payroll history | Reconcile every completed quarter and the current quarter before importing |
Incorrect field mapping | Document tax treatment and calculation rules, not only field names |
Missing terminated employees | Include everyone paid during the calendar year |
Missing garnishments | Maintain a separate list of active orders, balances, agencies, and payment schedules |
Tax-account delays | Identify registrations and authorizations early and track each jurisdiction separately |
Duplicate or missing filings | Assign each return, deposit, annual form, and amendment to one party |
Failed integrations | Test real records and verify results in both systems |
Lost historical access | Export and secure records before canceling the former service |
Employee disruption | Communicate requirements early and identify one support contact |
Untracked late changes | Maintain a migration change log through the first live payroll |
Incorrect manual data | Require an independent review of the reconstructed history |
Banking-data gaps | Confirm whether employees must securely re-enter or reauthorize direct deposit |
Businesses leaving a PEO need an additional transition workstream. Depending on the arrangement, the PEO may have handled wage reporting, payroll-tax filings, benefits, workers’ compensation, retirement administration, or other employer functions.
Leaving the PEO may affect:
Federal or state tax accounts
The entity reporting wages
Benefits coverage
Workers’ compensation
Retirement plans
COBRA responsibilities, when applicable
Year-end tax forms
Confirm the exact responsibilities with the PEO, replacement provider, benefits professionals, and tax advisers before choosing a launch date.
How Gusto supports payroll migration
Gusto uses a step-by-step onboarding process that identifies the forms and information a business needs to provide. Gusto also states that its team can help customers set up benefits, payroll deductions, paid time off policies, and integrations.
During onboarding, Gusto’s payroll transfer automation accepts specified employee and payroll-history reports from:
QuickBooks Online Payroll
QuickBooks Desktop Payroll
RUN Powered by ADP
Paychex
The Paychex payroll history import is in beta and may not be available to all customers. The transfer tool handles employee and payroll-history data; it does not create deductions, contributions, or other pay items. Administrators must configure those items separately.
Businesses joining Gusto after processing payroll elsewhere during the same year must provide complete prior-payroll records and documentation of payroll-tax payments. Gusto states that the prior provider generally handles completed quarters, while Gusto handles quarterly filings beginning with the quarter containing the first Gusto check date. Gusto also states that it prepares the year-end forms when it has the complete prior wage and tax information.
Businesses should still document the handoff and tell the former provider not to submit duplicate quarterly or annual forms.
Gusto payroll plans include unlimited payroll runs, including off-cycle runs. Confirm the migration service, import availability, plan features, and implementation responsibilities for your account before committing to a launch date.
Payroll migration checklist: Printable summary
Phase 1: Prepare
Define the migration scope
Audit the existing payroll configuration
Review the provider contract and exit process
Assign migration roles
Build the migration schedule
Establish change control
Phase 2: Migrate
Export employee, payroll, tax, and configuration data
Plan for direct-deposit reauthorization when needed
Create a secure, independent backup
Clean and reconcile the source data
Map fields between the systems
Import records and configure payroll
Reconnect and test integrations
Phase 3: Verify and go live
Verify employee and company records
Confirm tax accounts and filing responsibilities
Run a test or parallel payroll
Send employee instructions
Run and review the first live payroll
Monitor the first two or three payroll cycles
Export final records
Close the former account when appropriate
Related payroll-switching guides
Frequently asked questions
What is payroll migration?
Payroll migration is the process of moving and recreating the employee records, payroll history, tax information, deductions, benefits data, and settings needed to run payroll in a new system. It includes exporting, cleaning, mapping, importing, configuring, testing, and verifying the data.
How long does payroll migration take?
There is no universal timeline. The schedule depends on employee count, tax jurisdictions, benefits, integrations, data quality, bank verification, provider assistance, contract requirements, and whether the change occurs mid-year. Build the project around the first planned check date and account-specific provider deadlines.
How do I migrate payroll data to a new provider?
Export and secure the old records, reconcile payroll and tax totals, map source fields to the new system, import supported data, recreate payroll configurations, confirm tax responsibilities, run a payroll comparison, and monitor the first several live payrolls.
Can I migrate payroll mid-year?
Yes. A mid-year migration requires complete payroll history for earlier check dates, documentation of tax deposits, and a clear handoff for quarterly returns and year-end forms. Confirm which provider will handle each filing and prevent both providers from filing for the same period.
What are the biggest payroll migration risks?
Common risks include incomplete payroll history, incorrect year-to-date totals, missing terminated employees, lost garnishments, deduction-mapping errors, unresolved tax registrations, failed integrations, duplicate filings, banking-data gaps, and loss of historical access after cancellation.
How do I verify that migrated payroll data is accurate?
Compare wages, taxes, deductions, contributions, garnishments, paid time off, and net pay with the approved source records. Reconcile quarterly tax totals and run a payroll preview or parallel comparison before submitting the first live payroll.
How do I migrate from manual payroll to an online platform?
Compile employee records, payroll calculations, tax returns, deposit confirmations, bank and check records, deductions, contributions, and current-quarter history. Reconstruct employee-level and check-date details, then organize the records using the replacement provider’s setup or import template.
Will employees need to reenter their direct deposit information?
They may. Bank-account details and existing authorizations do not always transfer between providers, and some exports mask account numbers. Confirm the replacement provider’s process and have employees submit any required banking information through a secure system rather than email.
