EOR Migration Checklist: Move Employees Between Providers in 30 Days

EOR Migration Checklist: Move Employees Between Providers in 30 Days

Author: Martin English
Last Updated: June 4, 2026

Moving employees from one Employer of Record provider to another can be done in around 30 days, but only if payroll data, benefits, statutory records, employee communication, and cut-over timing are handled carefully.

The biggest risk is not the provider change itself. The biggest risk is a messy handover: missing payroll history, incorrect leave balances, delayed benefits enrolment, unclear employee messaging, missing statutory proof, or no clear owner for payroll validation.

Direct answer: To move employees between EOR providers in 30 days, start with a clear exit notice, collect the full employee and payroll data pack, confirm benefits continuity, run a parallel payroll validation, make a D-7 Go/No-Go decision, cut over preferably at month-end, and complete a post-switch compliance check within the first 30, 60, and 90 days.

This checklist is designed for companies moving Philippines-based employees from one EOR provider to another, including companies switching from a global EOR platform to a local Philippines-focused EOR.

How SOS helps: Smart Outsourcing Solution supports Philippines EOR migrations by helping employers validate payroll data, coordinate employee onboarding, manage local employment documentation, support benefits transition, set up payroll administration, and create post-switch compliance records.

For the full step-by-step migration guide, read Switching EOR Providers in the Philippines in 30 Days.

TL;DR: 30-day EOR migration checklist

Migration stage	Checklist outcome
D-30 to D-21	Confirm exit terms, assign owners, request employee and payroll data from the current EOR
D-20 to D-14	Configure the new EOR setup, validate employee records, map payroll fields, confirm benefits transition
D-13 to D-7	Run parallel payroll validation and check salary, deductions, statutory contributions, leave, and 13th month accruals
D-7	Make a Go/No-Go decision based on payroll accuracy, benefits continuity, statutory proof, and employee communication readiness
D-6 to D-1	Freeze payroll changes, send employee communications, confirm cut-over timing, and pre-fund payroll if required
D-0	Cut over to the new EOR, preferably at month-end
D+1 to D+30	Validate payslips, statutory records, benefits activation, employee support, and audit documentation
D+31 to D+90	Complete post-switch health checks and close any payroll, HR, benefits, or documentation gaps

Quick copy/paste EOR migration checklist

Use this summary checklist before confirming cut-over:

• ☐ Exit terms and notice period confirmed
• ☐ Internal migration owner assigned
• ☐ Payroll owner assigned
• ☐ Employee communication owner assigned
• ☐ Full employee master data received
• ☐ Employment documents received
• ☐ Payroll history and payslips received
• ☐ Leave balances validated
• ☐ 13th month year-to-date accrual confirmed
• ☐ SSS, PhilHealth, Pag-IBIG, and BIR-related records checked
• ☐ BIR Form 2316 continuity considered
• ☐ Benefits and HMO transition confirmed
• ☐ New EOR employment documents prepared
• ☐ Parallel payroll completed
• ☐ Payroll variances explained and approved
• ☐ Employee communication approved
• ☐ D-7 Go/No-Go decision completed
• ☐ Cut-over date confirmed
• ☐ First payroll after migration reviewed
• ☐ Post-switch 30/60/90 health check scheduled

Do not migrate in 30 days if these risks are unresolved

A 30-day EOR migration is only realistic when the data, payroll, benefits, and employee communication are ready.

Do not force a 30-day cut-over if:

• the current EOR has not provided complete employee records,
• payroll history is missing or inconsistent,
• leave balances cannot be verified,
• 13th month pay accruals are unclear,
• benefits cannot be transitioned without a gap,
• there are unresolved employee disputes,
• employees have complex allowances, schedules, or pending final pay items,
• the old provider is not cooperating with data export,
• the new EOR has not completed parallel payroll validation,
• the company has no internal migration owner.

In these cases, use a staged migration or extend the timeline. A slower migration is better than a payroll or benefits failure.

Who should use this EOR migration checklist?

Use this checklist if your company:

• already has employees in the Philippines under an EOR,
• wants to move employees to a new EOR provider,
• is switching from a global EOR platform to a Philippines-focused provider,
• is unhappy with payroll support, costs, communication, or local HR handling,
• wants to avoid employee disruption during the provider change,
• needs proof that payroll, benefits, and statutory records are clean after migration.

If you are still choosing which provider to move to, read Best EOR for Switching EOR Providers in the Philippines.

What counts as an EOR migration?

An EOR migration is the process of moving employees from one legal employment and payroll provider to another while keeping the employees’ roles, work arrangements, pay expectations, benefits, and day-to-day management as stable as possible.

In a Philippines EOR migration, the handover usually involves:

• employee master data,
• employment documentation,
• payroll history,
• payslip records,
• leave balances,
• statutory contribution records,
• BIR-related payroll records,
• 13th month pay accruals,
• HMO or benefits records,
• employee communication,
• new employment onboarding,
• cut-over payroll validation,
• post-switch compliance proof.

The goal is simple: employees should not experience payroll disruption, benefits confusion, missing records, or unclear employment communication.

The 30-day EOR migration timeline

Timeline	Main objective	Key deliverables
D-30 to D-21	Plan the exit and migration	Exit notice, RACI, data request list, employee list, migration calendar
D-20 to D-14	Build the new EOR setup	Employee data validation, payroll mapping, benefits transition plan
D-13 to D-7	Validate payroll and records	Parallel payroll run, variance report, leave balance check, 13th month accrual review
D-7	Decide Go or No-Go	Signed migration approval, escalation list, cut-over confirmation
D-6 to D-1	Prepare employees and payroll	Employee comms, payroll freeze, final data lock, pre-funding if required
D-0	Execute cut-over	New EOR employment activation, payroll ownership transfer
D+1 to D+30	Confirm migration success	Payslip validation, statutory record check, benefits confirmation, issue log
D+31 to D+90	Complete post-switch audit	30/60/90 health check, final audit pack, process improvements

D-30 to D-21: Migration planning checklist

Start by confirming why you are switching, who owns the migration, and what the current EOR must provide.

Checklist item	Owner	Status
Confirm commercial reason for switching EOR providers	Client leadership	☐
Review current EOR contract, notice period, exit fees, and data export terms	Client legal / operations	☐
Confirm intended cut-over date	Client + new EOR	☐
Choose month-end or mid-month cut-over	Client finance + payroll	☐
Assign internal migration owner	Client operations / HR	☐
Assign payroll owner	Client finance / payroll	☐
Assign employee communications owner	Client HR / people team	☐
Assign new EOR implementation owner	New EOR	☐
Create migration tracker	Client + new EOR	☐
Identify employee-risk groups, such as new starters, leavers, night-shift workers, employees with complex allowances, or employees with pending HR matters	Client + old EOR + new EOR	☐

D-30 data request: what to ask from the current EOR

The quality of the migration depends on the quality of the data export.

Request the following from the current EOR as early as possible:

Data category	Required records
Employee master file	Full name, address, contact details, role, start date, employment status, compensation, work schedule
Employment documents	Contracts, amendments, offer letters, policy acknowledgements
Payroll setup	Salary, allowances, deductions, bank details, tax setup, pay cycle, pay components
Payroll history	Year-to-date payroll ledger, previous payslips, payroll register, adjustment records
Leave records	Accrued leave, used leave, pending leave, unpaid leave, leave policies applied
Benefits records	HMO enrolment, dependents, benefit start dates, premiums, coverage details
Statutory records	SSS, PhilHealth, Pag-IBIG, BIR-related payroll records where applicable
BIR documentation	BIR Form 2316 continuity, withholding records, and tax-related payroll information where applicable
13th month pay	Year-to-date accrual records, prior payments, calculation basis
Timekeeping records	Attendance, overtime, night differential, holiday work, schedule adjustments
Employee relations records	Active warnings, grievances, performance issues, ongoing HR matters
Offboarding records	Any pending resignations, separations, clearance records, final pay items
Data protection records	Data handover confirmation, access revocation plan, deletion or retention confirmation request

D-20 to D-14: New EOR setup checklist

Once the data pack is received, the new EOR should configure employment, payroll, benefits, and HR records.

Checklist item	Owner	Status
Validate employee names, start dates, job titles, and compensation	New EOR	☐
Confirm employee classification and employment type	New EOR + client	☐
Map pay components from old EOR to new EOR	New EOR payroll	☐
Confirm bank details securely	New EOR payroll	☐
Confirm payroll calendar	Client + new EOR	☐
Confirm statutory IDs and records	New EOR	☐
Validate leave balances	Client + new EOR	☐
Validate 13th month pay accruals	New EOR payroll	☐
Confirm BIR-related payroll records and Form 2316 continuity	New EOR payroll	☐
Confirm HMO or benefits transition plan	New EOR HR	☐
Prepare new employment documentation	New EOR	☐
Confirm employee onboarding steps	New EOR HR	☐
Create employee helpdesk or escalation channel	Client + new EOR	☐

Philippines statutory proof checklist

For Philippines-based employees, the migration audit pack should preserve evidence that payroll and statutory records moved cleanly.

PH-specific item	Why it matters	Status
SSS contribution records	Supports employee contribution continuity	☐
PhilHealth contribution records	Helps confirm health contribution continuity	☐
Pag-IBIG contribution records	Supports employee housing fund contribution continuity	☐
BIR withholding records	Helps preserve payroll tax documentation	☐
BIR Form 2316 continuity	Important for annual employee tax documentation	☐
13th month year-to-date calculation	Prevents year-end underpayment or double counting	☐
Leave balance report	Prevents entitlement disputes	☐
Final or transition pay confirmation	Avoids pay gaps between old and new provider	☐
Payslip history	Supports payroll auditability	☐
Certificate of employment handling, if applicable	Supports employee record continuity	☐

Payroll migration checklist

Payroll is the highest-risk part of an EOR migration. Do not cut over until payroll has been tested.

Payroll item	Validation question	Status
Base salary	Does salary match the old payroll record and employee agreement?	☐
Allowances	Are recurring allowances mapped correctly?	☐
Deductions	Are deductions accurate and authorised?	☐
Leave balances	Do leave balances match approved records?	☐
Overtime	Are overtime rules and calculations configured correctly?	☐
Night differential	Are applicable night differential rules included?	☐
Holiday pay	Are holiday work rules and multipliers configured correctly?	☐
13th month pay	Are year-to-date accruals captured accurately?	☐
Statutory contributions	Are contribution records and employee details aligned?	☐
Tax and withholding setup	Are payroll tax details configured correctly?	☐
Bank file	Has the bank file format been tested?	☐
Payslip format	Does the payslip clearly show pay components and deductions?	☐

D-13 to D-7: Parallel payroll validation checklist

A parallel payroll run is the main control that prevents employee disruption.

Use the old payroll data and run it through the new EOR’s payroll setup before going live.

Validation test	Target
Gross salary match	Salary should match employee records
Net pay variance	Variance should be explained and approved before cut-over
Allowance mapping	All recurring allowances should be mapped correctly
Deduction mapping	All deductions should be validated
Leave balance match	Leave records should match approved source data
13th month accrual match	Accrual should continue without gaps
Statutory contribution review	Employer and employee records should be checked
BIR-related payroll review	Withholding and tax documentation continuity should be checked
Payslip review	Payslip should be clear and complete
Exception report	All differences should be logged and resolved
Approval	Payroll owner signs off before Go/No-Go

D-7 Go/No-Go checklist

Do not proceed to cut-over until the critical items are ready.

Go/No-Go question	Go condition	Status
Has the current EOR provided the required employee data?	Complete data pack received	☐
Has parallel payroll been completed?	Yes, with variances explained	☐
Are salary and pay components accurate?	Confirmed by payroll owner	☐
Are leave balances accurate?	Confirmed by client and new EOR	☐
Is 13th month accrual continuity confirmed?	Confirmed by payroll owner	☐
Are statutory records complete?	SSS, PhilHealth, Pag-IBIG, and BIR-related records checked	☐
Are benefits ready?	HMO or benefit plan confirmed	☐
Are employee communications ready?	Approved message and FAQ prepared	☐
Are escalation contacts ready?	Contacts shared with employees	☐
Is payroll funding ready?	Funding process confirmed	☐
Is cut-over timing confirmed?	Month-end or approved mid-month split	☐

If any critical item is incomplete, delay the cut-over or use a staged migration.

Month-end vs mid-month EOR migration

A month-end cut-over is usually cleaner because it reduces payroll splitting and record complexity.

Option	Best for	Advantages	Watch-outs
Month-end cut-over	Standard migrations	Cleaner payroll period, easier payslips, simpler contribution tracking	May require waiting for the next payroll cycle
Mid-month cut-over	Urgent migrations	Faster transition	Requires split payroll, pro-rated salary, and careful records
Staged migration	Larger or complex teams	Lower operational risk	Takes longer and requires more coordination

D-6 to D-1: Employee communication checklist

Employee communication should be clear, calm, and practical.

Employees need to know what is changing, what is not changing, and who to contact.

Communication item	Status
Explain why the EOR provider is changing	☐
Confirm that day-to-day role and manager remain the same, if applicable	☐
Confirm whether salary, benefits, and work schedule remain the same	☐
Explain any new employment documents to sign	☐
Confirm payroll date	☐
Confirm benefits transition timing	☐
Share HR and payroll support contacts	☐
Share FAQ for common employee questions	☐
Explain data privacy and document collection requirements	☐
Confirm when the new EOR becomes active	☐

Sample employee communication

Subject: Update on EOR Provider Transition

Hi team,

We are moving to a new Employer of Record provider for our Philippines team. This change is being made to improve local employment support, payroll coordination, benefits administration, and employee service.

Your day-to-day role, manager, and work responsibilities are not changing because of this provider transition. We will share any documents or onboarding steps required by the new EOR, along with the timeline and support contacts.

Our priority is to make the transition smooth and avoid any disruption to payroll, benefits, or HR support.

If you have questions, please contact [insert contact name] or [insert support email].

Thank you,
[Company Name]

D-0 cut-over checklist

On cut-over day, keep the process controlled and avoid last-minute changes.

Cut-over item	Owner	Status
Confirm final employee list	Client + new EOR	☐
Confirm payroll ownership start date	Client + new EOR	☐
Confirm old EOR end date	Client + old EOR	☐
Confirm benefits activation date	New EOR	☐
Confirm employment documents are signed	New EOR	☐
Confirm employee support contacts are live	Client + new EOR	☐
Freeze non-critical payroll changes	Client payroll	☐
Confirm bank file and funding process	New EOR payroll	☐
Confirm escalation process for payroll or HR issues	Client + new EOR	☐

D+1 to D+30: Post-migration validation checklist

The migration is not complete on cut-over day. It is complete when payroll, benefits, statutory records, and employee support have been validated.

Post-switch item	Validation method	Status
First payslip issued correctly	Employee and payroll review	☐
Net pay confirmed	Payroll report and employee confirmation	☐
Benefits active	HMO or benefit confirmation	☐
Leave balances correct	HRIS or payroll record check	☐
13th month accrual continued	Payroll report	☐
SSS, PhilHealth, and Pag-IBIG records checked	EOR statutory documentation	☐
BIR-related records checked	Payroll and tax documentation review	☐
Employee questions resolved	Issue log	☐
Old EOR access removed	Access review	☐
Data deletion or retention confirmed	Old EOR confirmation	☐
Migration audit pack created	Shared folder or compliance archive	☐

After cut-over, run a structured review using the 30/60/90-Day Post-Switch Health Check.

Migration audit pack checklist

Create one central folder for the migration audit pack.

Document	Why it matters
Current EOR termination notice	Confirms formal exit process
New EOR agreement	Confirms new provider terms
Employee master data file	Shows transferred employee details
Employment documents	Preserves employment record continuity
Payroll mapping file	Shows how pay components moved
Parallel payroll variance report	Proves payroll was checked
Leave balance report	Supports employee entitlements
13th month accrual report	Prevents year-end payment gaps
SSS / PhilHealth / Pag-IBIG contribution records	Supports statutory record validation
BIR withholding and Form 2316-related records	Supports annual tax documentation continuity
Benefits transition confirmation	Reduces HMO or coverage disputes
Employee communication record	Shows employees were informed
First payroll report after cut-over	Confirms live payroll success
Payslip sample review	Confirms payslip format and accuracy
Final or transition pay confirmation	Prevents gaps between old and new provider
Data deletion or retention confirmation	Reduces data privacy and access risk
Issue log and resolution notes	Shows post-switch remediation

EOR migration risk checklist

Risk	What can go wrong	Control
Missing payroll data	Incorrect salary, deductions, or payslips	Request full payroll ledger and run parallel payroll
Wrong leave balances	Employee disputes or payroll errors	Compare old EOR, employee, and client records
13th month gaps	Underpayment or year-end errors	Transfer year-to-date accrual data
Benefits lapse	Employee loses HMO or benefit continuity	Confirm activation before cut-over
Poor employee communication	Confusion, anxiety, attrition risk	Send clear communication and FAQ before D-0
Mid-month split errors	Duplicate or missing pay	Prefer month-end or document split payroll carefully
Missing statutory proof	Weak audit trail	Request and archive SSS, PhilHealth, Pag-IBIG, and BIR-related records
Data privacy gaps	Old provider retains access too long	Confirm access revocation and deletion or retention process
No escalation path	Issues take too long to resolve	Assign named contacts before cut-over

EOR migration RACI

Workstream	Client	Old EOR	New EOR
Migration plan	Accountable	Consulted	Responsible
Contract exit	Accountable	Responsible	Consulted
Employee data export	Consulted	Accountable	Responsible for validation
Payroll mapping	Accountable	Consulted	Responsible
Parallel payroll	Accountable	Consulted	Responsible
Benefits continuity	Consulted	Consulted	Accountable
Employee communication	Accountable	Consulted	Responsible support
Cut-over payroll	Accountable	Consulted	Responsible
Post-switch validation	Accountable	Not usually involved	Responsible
Audit pack	Accountable	Consulted	Responsible support

Cost checklist for moving EOR providers

An EOR migration may involve more than a new monthly provider fee.

Cost area	What to check
Old EOR exit costs	Notice period, termination fees, data export fees, contract minimums
New EOR onboarding costs	Setup fee, implementation fee, contract processing
Payroll overlap	Funding needs during the first payroll cycle
Benefits transition	HMO changes, premium timing, dependent coverage
Equipment or access changes	Device policies, software accounts, security tools
Internal team time	HR, finance, legal, operations, and employee communication
FX or payment timing	Currency differences and payroll funding deadlines
Post-switch remediation	Corrections, employee support, document cleanup

For fee comparison, read Employer of Record Pricing Philippines and Employer of Record Cost Breakdown.

EOR migration vs staff leasing vs BPO transition

Not every provider change is an EOR migration. The checklist changes depending on the model.

Transition type	What changes	What to check
EOR to EOR	Legal employer and payroll provider	Employment documents, payroll, benefits, statutory records
Contractor to EOR	Worker classification and employment structure	Contracts, salary, benefits, payroll setup, employee communication
Staff leasing to EOR	Operating and employment model	Control, supervision, HR handling, employment records
BPO to EOR	Service model to direct team model	Role ownership, employee management, tools, KPIs, data access

For model comparison, read Employer of Record vs Staff Leasing vs BPO.

Switching from a global EOR platform

Many companies consider moving from a global EOR platform to a local Philippines-focused EOR when they mainly employ people in the Philippines and want more local support, clearer pricing, or better employee communication.

The migration process is similar, but pay extra attention to:

• contract notice terms,
• data export rules,
• employee record ownership,
• payroll history format,
• local statutory records,
• benefits continuity,
• employee communication,
• post-switch compliance proof.

For a provider-specific transition example, read Switch from Remote.com to a Philippines-Focused EOR.

Frequently Asked Questions

How long does it take to move employees between EOR providers?

Many EOR migrations can be completed in around 30 days if the old provider supplies the required data, the new provider can onboard quickly, payroll is validated, and benefits continuity is confirmed. Complex teams may need more time.

What is the most important part of an EOR migration?

The most important control is the parallel payroll validation. It helps identify salary, deduction, leave, benefit, 13th month, and statutory record issues before employees are moved to the new provider.

Is month-end or mid-month better for an EOR migration?

Month-end is usually cleaner because it avoids split payroll periods. Mid-month migration is possible, but it requires careful pro-rating, clear payslip records, and agreement on which provider handles each part of the pay period.

Will employees lose benefits during an EOR migration?

They should not lose benefits if the transition is planned properly. Benefits continuity should be confirmed before cut-over, especially for HMO coverage, dependents, premium timing, and benefit start dates.

What records should the old EOR provide?

The old EOR should provide employee master data, employment documents, payroll history, payslips, leave balances, benefits records, SSS, PhilHealth, Pag-IBIG, BIR-related records, 13th month accrual data, and relevant HR records.

Do employees need to sign new documents?

Usually, employees will need updated employment or onboarding documents with the new EOR. The exact documents depend on the migration structure, provider process, and employment arrangement.

Can we move employees from a global EOR to a local Philippines EOR?

Yes. Companies with Philippines-heavy teams often assess local EOR options when they want more local payroll support, clearer pricing, or stronger employee service. The transition should still be managed through a structured data, payroll, benefits, and communication process.

What happens after the EOR migration is complete?

After cut-over, the company should validate the first payroll, confirm benefits activation, check statutory documentation, resolve employee questions, and complete 30/60/90-day post-switch health checks.

What is the biggest mistake in an EOR migration?

The biggest mistake is treating cut-over day as the finish line. The migration is only complete when the first payroll is validated, benefits are active, statutory records are preserved, employee issues are resolved, and the post-switch audit pack is complete.

Move Employees Between EOR Providers with Less Risk

If you are planning to move Philippines-based employees from one EOR provider to another, SOS can help you map the migration, identify payroll and benefits risks, review employee communication, and plan a cleaner 30-day cut-over.

Smart Outsourcing Solution can help with:

• migration planning,
• employee data handover,
• payroll setup and validation,
• benefits transition,
• employee communication,
• post-switch compliance checks,
• Philippines-focused EOR onboarding.

Contact SOS to review your EOR migration plan

About the Author

Martin English writes about Employer of Record services, compliant offshore hiring, and building Philippines-based teams for international businesses. His work focuses on practical workforce structures, payroll transparency, and sustainable offshore growth.

Disclaimer

This guide provides general operational information only. It is not legal, employment, payroll, tax, privacy, or compliance advice. EOR migration requirements depend on contracts, employee circumstances, provider terms, payroll setup, and applicable regulations. Businesses should obtain appropriate advice before making employment, payroll, tax, privacy, or compliance decisions.