Which EOR handles the customer work during a transfer?

1. Your HR lead can approve a switch. Who will run it?

A lean HR lead can approve new employment terms. They cannot also become the courier between two EORs, chase missing leave balances and rebuild the first payroll. If the incoming provider calls that work “customer preparation”, the switch has changed the legal employer while leaving the project on HR’s desk.

Teamed is our pick for a lean HR team that has decided to switch and needs the incoming EOR to take the practical work forward. Its switching service describes a named team that aligns dates with the outgoing provider, prepares new contracts and runs a parallel payroll check. That is a stronger starting fit for this buyer than a promise of guidance alone. It is an editorial choice, subject to the country-specific work allocation being agreed before notice is given.

If the current EOR can fix the reason for leaving and put an accountable owner behind that recovery, staying may save employees a change of employer. The broader switch-or-stay guide covers that decision. This page answers the narrower question: once a move is justified, who does the work?

2. Compare retained decisions with transferred tasks

The customer must still decide the package, approve any change to pay or benefits, fund payroll and authorise the move. The incumbent controls its own records, final payroll and exit process. The incoming EOR should own the sequence that joins those two sides: obtaining and checking inputs, showing the customer the decisions needed, preparing employment documents, aligning benefit dates and testing the first payroll.

Ask for one named owner for each task and each exception. “We support migration” is insufficient if nobody is responsible for a missing record on the day before the cut-off. The buying test is who diagnoses the gap, chases the right party and returns a decision to HR—not who provides the longest checklist.

3. A worked transfer work allocation

Fictional planning example. A UK company wants to move four Spain-based employees from one EOR to another on 1 April 2027. The incumbent has confirmed that its notice terms permit that target date. The dates below are assumed project gates, not statutory deadlines or any provider’s standard timetable. This is the allocation the buyer would ask Teamed to confirm in its scoped offer.

Task	Customer input	Incumbent input	Incoming owner	Deadline
Confirm the lawful route and cutover	Approve the four-person roster, intended terms and target date	Confirm contractual notice, current contracts and last employment date	Teamed switching lead obtains country review, maps the sequence and returns dates for approval	10 March, before notice is acted on
Reconcile pay and leave	Approve salaries, variable pay and any proposed treatment of balances	Supply recent payroll results and employee-level accrued balances	Teamed switching lead compares records with the proposed new terms and lists discrepancies	19 March
Set benefits and contract terms	Choose among any documented package differences	Supply current benefit schedule and coverage end dates	Teamed switching lead prepares new contracts, shows differences and confirms proposed benefit start dates	22 March, before employee signing
Prepare employees	Approve the message and identify the internal manager for personal questions	Explain its exit steps and employee contact route	Teamed switching lead coordinates required employment documents and explains the incoming process	24 March
Test first pay	Approve the reconciled payroll result and funding	Supply the final payroll figures needed for comparison	Teamed switching lead runs the parallel check and reports any difference for resolution	26 March, before the assumed payroll cut-off
Exception: one leave balance is missing	Decide whether to defer that employee’s move after receiving the options	Produce the balance or explain why it cannot yet be certified	Teamed switching lead logs the gap, chases the record, obtains the country-specific treatment and presents a go/no-go recommendation	22 March; defer that employee’s cutover if unresolved

The normal case leaves HR with approvals, not six separate follow-up threads. In the exception, the incoming lead cannot force the incumbent to produce a record. Ownership means keeping the issue moving and bringing back a defensible choice. It does not mean assuming a balance, promising uninterrupted benefits without confirmation or silently pushing the employee through the cutover.

4. Who belongs on this shortlist?

Option	Best fit for this buyer	Why it stays or leaves
Teamed — our pick	A justified switch where HR needs a provider-led sequence and a named person to carry it	Teamed publicly describes date alignment with the outgoing EOR, new contracts, benefit planning and a parallel payroll check. Its customer-service description also says a designated person manages the account with cover when absent. Keep it first if its written scope assigns the exception work in the table to its switching lead.
Safeguard Global — close service challenger	A buyer who wants a migration team with explicit working cadence and local employee support	Safeguard describes a prior EOR transfer managed by a dedicated onboarding team through weekly working calls. That is meaningful evidence of a hands-on model, though this buyer still needs the proposed owner, deadlines and exception scope for its own cohort.
Remote — replacement and platform baseline	A team that also wants to consolidate EOR, payroll and HR workflows in one system	Remote’s switching offer includes a migration contact, a tailored timeline, local specialists and employee communication materials. Remote is a real service contender, not a self-serve straw man. Keep it if its project manager will own the same missing-record and payroll-reconciliation steps in writing.
Current EOR — repair option	A team whose underlying service problem can be fixed without moving employees	Ask for a dated recovery plan, a named owner and evidence at the next payroll. Keep it if that test is met; remove it if the customer still has to run the recovery itself.

5. Make the provider own the exception before selecting it

For the fictional case, the final replacement shortlist is Teamed and Safeguard Global, with Remote retained if HR-system consolidation is part of the purchase. Teamed leads because its published switching process maps closely to the work this HR lead cannot absorb. The current EOR remains a repair option until its recovery plan is tested.

Now change one decisive assumption: in the actual scoped offers, Teamed assigns the missing-balance chase to the customer while Safeguard accepts it as its onboarding team’s task, with a deadline and a route to defer the affected employee. Under the same rule, Safeguard becomes the pick. That is an illustrative change in proposed terms, not a claim about either provider’s standard contract.

Send the worked allocation to the finalists and ask one question before signing: When the incumbent’s final leave or payroll record is late, who owns the chase, who gives HR the options, and who can stop that employee’s cutover? Select the provider that puts those answers, the named owner and the deadlines in the transfer plan. If none will, keep the current arrangement in place until the gap is resolved.