Switching offshore staffing providers: the handover risks nobody mentions

Moving one offshore hire to a new provider is an administrative task. Moving an established team of twenty or thirty is a different exercise entirely, and the risks are not where most people look for them.

We transitioned a thirty-three person Philippine team onto our entity on a single effective date. The contracts were the easy part. Here’s what actually needed managing.

The risk is continuity of service, not the contracts

When staff move from one employer to another, the critical question is whether the new employer is treated as continuing the old employment or starting a fresh one.

It matters because Philippine statutory entitlements accrue with length of service. Separation pay, thirteenth month, retirement entitlements under RA 7641, seniority. If the new employer’s documentation reads as though service carried across, years of accrued exposure can attach to the new entity — for a period during which it received no fees, held no funds and had no involvement.

The old provider, meanwhile, has a signed exit and considers the matter closed.

Certificates of employment are where it goes wrong

This surfaced for us after go-live, and it’s the specific trap worth knowing about.

Staff need certificates of employment for ordinary life — bank accounts, loan applications, rental agreements. It’s a reasonable request and one an employer is obliged to meet on request.

The draft wording that came to us described the staff as having undergone a “transition of their employment” from the previous company. Innocuous phrasing. It also reads as an acknowledgment that the new employer is continuing the old employment relationship, which is exactly the admission you don’t want sitting in a signed document.

The fix is simple and costs nothing. Each employer issues a certificate covering its own period only. The old provider certifies the period it employed them. The new employer certifies from the transition date forward. The employee gets two documents, which together do everything one document would have done, and neither employer has conceded anything.

Add an express line that the certificate doesn’t constitute recognition of continuous service for statutory purposes.

Make the break explicit in the new contract

Each new employment agreement should state plainly that any employment or contractor relationship with the previous arrangement ended permanently on a specified date.

Two drafting notes from doing this at scale. Say “any employment or contractor relationship” rather than “any and all relationships” — the broader wording sweeps in things nobody intended and invites an argument. And make the date a variable rather than hard-coding it, because in a transition of any size somebody will move on a different date.

Then check the other side. Were final pay and quitclaims actually executed when the staff separated from the previous employer? If the old provider never closed the relationship properly, the clean break exists only in your paperwork.

Protect the team leader’s authority

The most likely thing to go wrong in a transition of this size has nothing to do with law.

An established team has someone who runs it. If that person’s authority is unclear for even a fortnight, you get confusion about who to escalate to, decisions stalling, and a team that feels handed over rather than moved.

In our thirty-three person transition, the existing team lead kept running her team exactly as before. We sat behind her on compliance, payroll and administration. Staff reported to the same person on day one as they had the week before. That was the single most deliberate decision in the whole project, and the main reason it was uneventful.

The things that only bite at scale

Some obligations don’t apply to a team of three and do apply to a team of thirty. Leave entitlements can cross statutory headcount thresholds. Regional and provincial holidays reach every staff member assigned to that workplace, not just the ones who live there — we had a provincial charter day land four days after go-live, and the cost and coverage options needed deciding before payroll ran, not after.

Night differential, rest day and overtime loadings should be written into the agreements with the statutory references, not summarised in a sentence. At scale, “we’ll handle it in payroll” is not a policy.

A checklist before you move a team

Who is the legal employer after the move, and in which country is that entity registered?

Does the new documentation avoid any language implying continuity of service?

Will each employer issue its own certificate for its own period?

Were final pay and quitclaims executed on the outgoing side?

Does the new client agreement indemnify you for claims relating to the pre-transition period?

Does the existing team leader keep their authority through the change?

Have you checked for statutory obligations that apply at the new headcount but didn’t at the old one?

General information, not legal advice. A transition of any size should be reviewed by Philippine counsel against your specific facts.