Can You Transfer Employees from a BPO to an EOR? 2026 Guide

Author: Martin English
Date Updated: June 8, 2026

TL;DR: Can you transfer employees from a BPO to an EOR?

Sometimes, but it is not automatic.

Employees working under a BPO arrangement can potentially move into an Employer of Record structure, but only if the BPO agreement allows it, employees voluntarily agree, transfer or buyout terms are handled correctly, and the move does not breach non-solicitation, non-circumvention, replacement, or client-conversion clauses.

The safest answer is: review the BPO contract first, then decide whether to transfer existing staff, rebuild the team under an EOR, or run a hybrid BPO and EOR model.

You should not approach, solicit, or offer roles to BPO staff until the BPO agreement has been reviewed for restrictions. This guide is for general information only and should not be treated as legal advice.

For the full transition framework, see How to Move from a BPO to an EOR in the Philippines.

Quick answer: is a BPO employee transfer legal?

A BPO employee transfer can be legal if the contract permits it, the employee consents, notice periods are followed, and any transfer, release, or buyout terms are properly handled.

A company should never assume that BPO staff can simply be moved into an EOR arrangement. In most BPO models, the staff are employed or engaged by the BPO, not by the client company. That means the client usually does not have automatic hiring rights over those people.

Before discussing employment opportunities with BPO staff, review:

• non-solicitation clauses
• non-circumvention clauses
• replacement clauses
• employee transfer terms
• buyout or placement fees
• minimum contract terms
• notice periods
• exit and handover obligations

If the contract is restrictive, you may need to negotiate with the BPO, hire new staff through an EOR, or run a phased hybrid model.

Who is this guide for?

This guide is for companies using a BPO in the Philippines and considering whether some or all staff should move into a dedicated EOR structure.

It is especially relevant for:

• founders reviewing vendor dependency
• COOs moving from outsourced delivery to an embedded team
• HR leaders planning a workforce transition
• finance teams comparing BPO vs EOR costs
• operations leaders trying to retain top BPO staff
• companies worried about non-solicit or transfer restrictions
• businesses planning a phased BPO-to-EOR transition

If the BPO model is still working well and you prefer vendor-managed delivery, staying with the BPO may be sensible. If you want dedicated staff, direct management, clearer payroll records, and stronger employment visibility, an EOR model may be worth reviewing.

Why companies want to transfer BPO employees to an EOR

Companies usually ask this question when outsourced staff have become too important to remain fully vendor-managed.

Common reasons include:

• retaining top performers
• reducing dependency on the BPO provider
• building a dedicated offshore team
• improving employee engagement
• gaining more control over hiring and performance
• improving payroll and cost visibility
• obtaining clearer employment documentation
• aligning employees with company culture
• supporting long-term team growth

As offshore teams mature, many businesses realise they do not only want outsourced capacity. They want people who operate as a long-term extension of the company.

For a broader model comparison, see Employer of Record vs Staff Leasing vs BPO.

What determines whether BPO employees can be transferred?

Several factors influence whether a transfer is possible.

1. The BPO contract

The BPO agreement is usually the most important document.

Review:

• non-solicitation clauses
• non-circumvention clauses
• replacement clauses
• employee buyout provisions
• transfer fees
• notice requirements
• exclusivity provisions
• recruitment restrictions
• termination clauses
• data handover obligations

Some BPO agreements prohibit clients from hiring or approaching staff. Others allow transfers after a period, with consent, or upon payment of a release or placement fee.

2. Employee consent

Employees cannot be moved into an EOR structure without their agreement.

Even if the BPO allows transfers, employees must voluntarily choose to join the new arrangement. They may consider:

• salary
• benefits
• HMO coverage
• job security
• work schedule
• manager relationship
• career progression
• remote work arrangements
• employment documentation

A transfer should be explained clearly and should not feel forced.

3. BPO cooperation

Some BPO providers support structured transitions. Others enforce transfer restrictions strictly.

A cooperative BPO exit can make it easier to handle:

• notice periods
• release terms
• knowledge transfer
• employee communications
• data handover
• final billing
• service continuity

If the BPO does not cooperate, a rebuild or hybrid model may be safer than forcing a direct transfer.

4. Timing and payroll cutover

Timing matters because employment transfer affects pay, benefits, contracts, access, and service continuity.

Check:

• when the current BPO contract ends
• whether notice periods apply
• whether there are minimum seat commitments
• whether the BPO charges transfer or release fees
• when the EOR can issue employment documents
• when first EOR payroll can run
• whether benefits can start without a gap

Poor timing can create payroll disruption, employee anxiety, and unnecessary cost.

Three ways to move from BPO staff to an EOR model

There are three practical pathways: direct transfer, new hiring, or hybrid transition.

Transition option	Best when	Watch-outs	Continuity
Direct staff transfer	The BPO allows release or buyout, employees want to move, and knowledge retention is critical	Non-solicit clauses, buyout fees, notice periods, employee consent, final pay, benefits continuity	High
New EOR hiring	The BPO contract restricts transfers or the company wants a clean separation	Recruitment time, training, knowledge rebuild, temporary productivity dip	Medium
Hybrid BPO + EOR model	Service continuity matters and the company wants to reduce transition risk	Temporary duplicate costs, clear role split, management complexity	High

For many companies, the hybrid path is safest. It allows the BPO to continue handling existing work while the company builds a dedicated EOR team gradually.

Option 1: Direct transfer from BPO to EOR

A direct transfer means specific people move from the BPO arrangement into a new EOR employment structure.

This can be useful when:

• the BPO agreement allows staff release
• the employee wants to move
• the role is hard to replace
• continuity matters
• training time would be costly
• customer or process knowledge is important

The main benefit is continuity. The main risk is contractual. Do not begin direct employee discussions until the BPO agreement has been reviewed.

Option 2: Rebuild the team through an EOR

If direct transfer is restricted, the company can hire new staff through an EOR.

This can be cleaner when:

• the BPO does not allow staff transfer
• the contract has strict non-solicit terms
• the BPO relationship needs to stay separate
• the company wants a fresh team structure
• the current staff do not want to move

The downside is ramp-up time. You may need to rebuild knowledge, train new hires, and run parallel operations while the new team stabilises.

Option 3: Hybrid BPO and EOR transition

A hybrid transition keeps some work with the BPO while building a dedicated EOR team.

This can work when:

• service continuity is critical
• you cannot risk a sudden transition
• only some roles should move
• contract restrictions limit direct hiring
• the company wants to test the EOR model first

A hybrid model is often the lowest-risk pathway because it avoids an all-at-once switch.

What should you check before approaching BPO staff?

Before approaching, soliciting, or offering roles to BPO staff, review the agreement carefully.

Contract item	Why it matters	What to check
Non-solicitation clause	May restrict hiring or approaching staff	Who is covered, for how long, and under what conditions?
Non-circumvention clause	May restrict bypassing the BPO	Does the contract prevent direct engagement with workers?
Replacement clause	May restrict hiring BPO staff after service termination	Does it apply after the contract ends?
Buyout or transfer fee	May allow transfer for a fee	What is the amount and process?
Notice period	Affects timing	How much notice must be given?
Minimum term	May delay transition	Is the contract still locked in?
Data handover	Affects onboarding	What employee, process, or payroll data can be shared?
Confidentiality	Affects communications	What can be discussed and with whom?
Exit support	Affects service continuity	Does the BPO need to support transition?

This review should happen before employee communications begin.

How to transfer employees safely

A safe transfer should protect contract compliance, employee trust, payroll continuity, and operational performance.

Step 1: Review the BPO agreement

Identify restrictions, notice periods, transfer terms, buyout fees, and exit obligations.

Step 2: Choose the transition path

Decide whether to pursue direct transfer, new hiring, or a hybrid model.

Step 3: Design the employment package

Confirm salary, benefits, HMO, leave, work schedule, manager, start date, role scope, and 13th month treatment.

Step 4: Plan payroll cutover

Align final BPO billing, final BPO payroll responsibilities, first EOR payroll, benefits activation, statutory setup, and employee start date.

Step 5: Prepare employee communication

Explain what changes, what stays the same, who the legal employer will be, how payroll works, and who employees can contact.

Step 6: Issue EOR employment documents

Prepare contracts, compensation schedules, benefits summaries, confidentiality clauses, payroll forms, bank details, and government information.

Step 7: Validate first payroll and onboarding

Check salary, deductions, benefits, payslips, statutory setup, bank details, leave balances, and employee questions.

What happens to benefits, leave, and 13th month pay?

Benefits, leave, and 13th month pay should be addressed before the transition.

Review:

• HMO coverage
• dependant coverage
• leave balances
• government contribution records
• final BPO payroll responsibilities
• first EOR payroll date
• 13th month accrual treatment
• reimbursements or pending allowances
• tax documentation status

The EOR should explain how each item will be handled before employees transfer.

For employment structure and classification questions, see Contractor vs Employee in the Philippines: Classification Rules Explained.

What proof should you keep during a BPO-to-EOR transfer?

Keep a transition proof pack that includes:

• BPO contract review notes
• transfer or release approvals
• employee consent or acknowledgement records
• employee communications
• new employment agreements
• salary and benefits summaries
• payroll start dates
• first payslips
• payroll registers
• benefits documentation
• statutory setup confirmation
• onboarding records
• issue logs

This creates a clear audit trail for HR, finance, leadership, and future provider reviews.

When should you not transfer BPO employees?

You may decide not to transfer employees when:

• contractual restrictions are significant
• buyout or transfer costs are too high
• employees prefer the BPO structure
• service continuity is at risk
• the company lacks internal management capacity
• the BPO relationship needs to remain stable
• rebuilding the team would be cleaner

In some situations, staying with the BPO or using a hybrid model is the better decision.

Common mistakes to avoid

Avoid these mistakes:

• approaching staff before reviewing the BPO agreement
• assuming employees can transfer automatically
• ignoring non-solicit or non-circumvention clauses
• focusing only on salary
• forgetting benefits, HMO, leave, and 13th month pay
• rushing payroll cutover
• failing to communicate clearly with employees
• starting EOR payroll before documents are signed
• not planning for knowledge transfer
• failing to keep a proof pack

A transfer should reduce risk, not create a contract dispute or payroll problem.

Why Smart Outsourcing Solution for BPO-to-EOR transfers?

Smart Outsourcing Solution helps companies build dedicated Philippine teams without establishing a local entity.

For BPO-to-EOR transitions, SOS can support:

• transfer, rebuild, or hybrid pathway planning
• workforce transition planning
• role and team mapping
• EOR employment setup
• payroll onboarding
• employee communication support
• benefits coordination
• SSS, PhilHealth, and Pag-IBIG administration
• BIR withholding support
• 13th month administration
• payroll validation
• local account management

SOS can help companies evaluate whether a direct transfer, team rebuild, or hybrid model is the safest approach.

To learn more about local employment support, see Employer of Record Services in the Philippines.

Related resources

• Convert Contractors to Employees Philippines
• Contractor Misclassification Philippines
• Cheapest EOR Provider in the Philippines

FAQs

Can employees legally move from a BPO to an EOR?

Yes, but only if contractual restrictions are respected and employees voluntarily agree to the move. The BPO agreement should be reviewed before any direct approach is made.

Can a BPO stop employees from transferring?

A BPO cannot force employees to stay indefinitely, but the client may be restricted by non-solicitation, non-circumvention, transfer, buyout, or notice clauses. These terms can affect whether and how a transfer can happen.

Do employees need to sign new contracts?

Yes. Employees moving to an EOR will generally receive new employment documentation from the EOR, including compensation details, benefits terms, confidentiality clauses, and payroll forms.

Is a direct transfer always the best option?

No. A direct transfer can preserve knowledge, but it may create contract risk if the BPO agreement restricts hiring. A rebuild or hybrid model may be safer in some cases.

How long does a BPO-to-EOR transfer take?

Many transitions can be planned within 30 to 90 days, depending on contract terms, team size, employee consent, payroll timing, and whether the BPO cooperates.

What happens to benefits during the move?

Benefits should be reviewed before transfer. The goal is to avoid HMO or coverage gaps and clearly explain when new benefits begin under the EOR.

What happens to 13th month pay during the move?

13th month pay should be reviewed before cutover. The transition plan should clarify whether amounts are settled by the BPO, started under the EOR, or handled through another agreed arrangement.

Can an EOR help with employee communications?

Yes. A good EOR can support transition planning, onboarding communications, employment documentation, payroll setup, and employee questions.

Should I move all BPO employees at once?

Not necessarily. Many companies start with key roles and expand gradually. A phased or hybrid approach can reduce operational risk.

Final takeaway

Yes, employees can sometimes move from a BPO to an EOR, but the process is not automatic.

The safest approach is to review the BPO contract first, avoid approaching staff too early, respect employee choice, plan payroll carefully, protect benefits continuity, and choose the transition path that best balances continuity, compliance, and long-term team ownership.

A direct transfer can work when the contract allows it and employees want to move. A rebuild may be cleaner when restrictions are tight. A hybrid model can reduce disruption when service continuity matters.

Ready to evaluate a BPO-to-EOR transfer?

Thinking about moving outsourced staff into a dedicated Philippines EOR structure? Contact Smart Outsourcing Solution to review your contract risks, transition options, payroll planning, and employee transfer strategy before making a decision.