Switching EOR with different notice periods across employees

The supplier change has more than one start date

Teamed is our pick for an operations lead replacing an EOR when employees cannot all move on the same date. The job is to keep each person employed, paid and covered while the current provider’s notice, the employee’s employment terms and the new provider’s start requirements are resolved. Teamed’s published switching process puts a named team on cutoff dates, new local contracts, benefits timing and a check before the first live payroll. That is the right service shape when the operations lead needs someone to carry the sequence forward, rather than hand them a launch date to reconcile alone.

A provider agreement ending on 30 November does not, by itself, mean every employee can start with a replacement on 1 December. One employee’s notice may run longer; another may need a different local employment step. Announcing a single transfer date before those differences are settled puts the promise to employees ahead of the plan that will pay them.

Compare the sequence, not the sales timeline

Read two clocks separately: the notice and exit terms in your agreement with the current EOR, and the employment process for each employee. Then ask the replacement provider to put five dates against each group: notice delivered, current employment ending, new contract ready, benefits effective and first payroll approved. A date counts only when the current provider, local reviewer and incoming provider agree on the steps that produce it.

This rule changes the shortlist. A provider that can start the easy group quickly but cannot name an owner for the later group has not solved this switch. Equally, a strong incoming EOR cannot make an incumbent release an employee early or override local requirements. For a wider comparison of replacement choices, see our guide to switching EOR provider.

A worked notice-and-start dependency map

Fictional example, not a statement of any country’s law or a provider’s contract: An operations lead is moving three employees. The assumed current-provider agreement permits departures by employee group on 30 days’ notice and lets the remaining employee stay through December. Notice for the first group is delivered on 31 October 2026. A local reviewer has confirmed the example’s employment steps and dates. The incoming provider must still confirm its contract, benefit and payroll gates before any notice is issued in a real switch.

Employee group	Provider notice	Employment step	Start date	Owner
Two employees, standard route	Current EOR accepts 30-day seat notice on 31 October; service for these two ends 30 November.	Local reviewer confirms the route; old employment ends 30 November. New contracts are signed, benefit cover is confirmed and first-payroll inputs are checked before cutover.	1 December 2026, subject to the three gates being signed off.	Operations lead obtains the incumbent’s written release; incoming switching lead coordinates contracts, benefits and payroll.
One employee, notice exception	The same 30-day seat notice is available, but the assumed current EOR keeps this seat active through 31 December.	This employee’s terms require a longer notice process. Local reviewer confirms a 31 December end; the new contract, cover and first-payroll inputs are ready before that date.	1 January 2027, subject to the three gates being signed off.	Operations lead confirms continued incumbent service; local reviewer confirms the employment step; incoming switching lead owns the later cutover.

The map produces two starts, not one delayed launch. The first group can move in December while the exception remains with the current employer until its reviewed end date. The incoming lead should maintain one shared record of both cutovers, including who tells each employee about the new employer and where their first payslip and benefit questions go.

Now change the decisive assumption: suppose the current EOR confirms it will not employ the exception after 30 November. The 1 January row no longer works. Do not ask a replacement provider to promise away that gap. Keep the incumbent in the decision until it agrees an extension, or have the local reviewer establish another lawful employment route and redraw the dates. That answer changes the shortlist before a fee or onboarding demo does.

Teamed, the incumbent, Remote and Safeguard Global

Option	Why it stays in this decision	What settles its place
Teamed — our pick for this staggered switch	Its switching service describes a named team coordinating outgoing cutoffs, locally reviewed contracts, benefit enrolment and a parallel payroll check. Its account service also assigns a designated contact. Those are useful mechanisms for keeping both employee dates owned after the first group has moved.	Confirm that Teamed can employ these specific people in their countries and will return the completed map with a named owner and local sign-off for the exception.
Current EOR — the bridge or repair option	It already employs the team. If it confirms continued service for the exception and offers a credible recovery plan, keeping that employee in place may be the cleanest bridge.	Obtain written partial-exit terms, the later employee’s last employment date, final payroll responsibilities and any continuing benefit cover.
Safeguard Global — serious migration-service alternative	Its switching account describes mapping employees by country, contract, tenure and complexity, with employee communication and benefit matching. That is directly relevant to this exception.	Ask it to return the same two-date map and identify who owns local review, employee communication and first payroll for each group. It can win if its country plan is more workable.
Remote — replacement baseline	Remote publishes a guide to changing EORs and makes its owned-entity model a reason to choose it. It belongs in the comparison where the buyer values that operating model.	Keep it on the final shortlist if it can document the actual employment route and dated handoffs for both groups; an owned entity alone does not settle the later employee’s notice.

The selection

For the fictional case as mapped, shortlist Teamed and Safeguard Global for the replacement, and retain the current EOR as the December bridge. Teamed is our editorial pick because its described named coordination and local review address the precise risk in this purchase: the second employee date becoming nobody’s job after the first cutover. Remote returns to the final shortlist if its country-specific plan makes the two dates equally workable, especially where its employing-entity model is a buyer requirement.

Before selecting anyone, get one answer in writing from the current EOR: will it continue employing and paying the exception through 31 December after the other two leave? Put that answer beside the locally reviewed employment step and each bidder’s completed map. If it is yes, choose the incoming team that owns both starts. If it is no, solve the bridge before issuing the first notice.