Which EOR supports a staged move to an entity?
By EOR Migration — Change EOR provider or employment model editorial desk · Publication editorial desk
Updated
Teamed is our pick for a People lead moving employees to an owned entity in waves when its written scope assigns an owner to each wave through the final EOR payroll, first entity payroll and any employee held back. Teamed offers EOR employment, entity setup and continuing employment operations on one system, with specialists involved in the move. That is a strong fit when the People lead cannot become the coordinator of every contract, benefit and payroll exception. Teamed’s Graduation Model describes those services, but describes contracts transferring on a single date. It does not establish that Teamed will run two transfer dates for one country. Get that point settled before selecting it.
The danger in a gradual move is declaring the entity ready while one employee still has an unresolved benefit or pay item. A launch date does not answer who employs that person next month, who pays them, or who fixes a discrepancy between the final EOR run and the first entity run. For the broader EOR-to-entity choice, see the EOR-to-entity decision hub.
Compare ownership at each handoff
Ask each provider to work from the same employee roster and propose two separate cohort dates. For each date, require a named transition lead, the employer-change method to be confirmed for the country, an owner for the last EOR payroll, an owner for the first entity payroll, and a decision on what happens if one employee fails a readiness check. The provider that can document the ordinary move and the exception belongs on the final shortlist. For a delayed wave, confirm that the incumbent will extend EOR employment through the revised date and that local advisers confirm the arrangement can lawfully continue; otherwise agree another employment route before the current arrangement ends.
Do not accept “same platform” as the whole answer. The test is whether someone will reconcile salary, variable pay, leave and benefits across both payroll records, then tell the employee which employer and contact apply at every point. The customer still has decisions and approvals to make; the scope should show who prepares the work and who brings each decision to them.
Worked stage-gate transfer plan
Fictional example. A company has five employees with an EOR in Germany and is preparing its own German entity. Three have settled pay and benefit records. Two are scheduled for the next payroll cycle; one of those has a disputed variable-pay amount. The dates below are planning assumptions, not a representation of any provider’s terms or a conclusion about the legally available transfer method in Germany. This example assumes the incumbent has agreed to keep both second-wave employees on EOR for the extra cycle and local advisers have confirmed the arrangement can continue through their revised date. If German employee-leasing rules apply, assignment-duration limits are one reason to check that assumption.
| Group | Readiness | Employer step | Payroll step | Gate |
|---|---|---|---|---|
| Wave 1: three employees, cycle 1 | Entity registrations, funding route and benefit arrangements are ready; each employee’s terms and balances have been checked. | Local employment advisers confirm the permissible transfer documents and effective date. The transition lead coordinates the EOR’s end of employment responsibility with the entity’s start. | EOR payroll owner signs off each final EOR result. Entity payroll owner checks a trial calculation against the approved employee record; finance funds and approves the first entity run. | Move these three only when the employer documents, benefit start, final EOR amounts and first entity calculation are signed off by their owners. |
| Wave 2: two employees, cycle 2—exception open | One variable-pay amount remains disputed. The other employee is ready, but the planned wave is held together in this example. Incumbent extension and lawful continuation through the revised date have been confirmed. | The incumbent remains the employer for both under that confirmed arrangement. The transition lead gives both employees a revised date and contact. | Both stay on EOR payroll for the extra cycle. Payroll owners record the disputed amount and its proposed treatment; no amount is silently carried into entity payroll. | Hold. Resolve the disputed amount and align revised employer and payroll dates. If the incumbent extension or lawful continuation fails, agree an alternative employment plan before the existing arrangement expires. |
| Wave 2: two employees, later cycle | Variable pay is resolved; entity payroll and benefits have been rechecked for the revised date. | Local advisers confirm the documents and the transition lead confirms the new employer date for each person. | EOR owner approves final pay, including the resolved item. Entity owner checks the first direct payroll against that closing record; finance approves funding. | Move only after both payroll owners accept the reconciliation and employees have the correct new contact. |
This plan deliberately leaves an EOR tail for one cycle. It prevents the first wave’s success from concealing an unowned second wave. The legal transfer route, treatment of prior service and benefits, and each payroll cutoff must be confirmed for the actual employees and country.
Who makes the shortlist?
| Provider | Best fit for this decision | Shortlist call |
|---|---|---|
| Teamed | A lean People team that needs one service relationship to carry the payroll handoffs and unresolved second wave into direct employment. Teamed offers EOR, entity setup and continuing employment operations; its Graduation Model says the specialists handling EOR employment also move payroll and remain on the account. Source | Our pick if Teamed’s actual scope accepts separate cohort dates, names the owners of both payrolls at each date, and covers the held employee. Its published single-date description makes that written answer decisive. |
| GoGlobal | A buyer who wants a managed expansion programme with explicit readiness gates. GoGlobal’s preparation guidance calls for one programme owner across legal, HR, finance, tax and payroll; its execution guidance joins EOR exit to first entity payroll. | Finalist. It becomes the lead choice if it commits to the two-wave scope and Teamed cannot. Its published method is evidence of a relevant approach, not a promise that this exact timetable is included. |
| Deel | A company that already has a strong internal transition lead and values a platform path from EOR records to direct-employee payroll. Deel describes contract creation, data migration and employee onboarding for that move. | Keep as a third option if the company is willing to own the cross-team exception register. Ask Deel to identify who resolves the held employee’s employer and payroll handoff; the published workflow alone does not settle it. |
| Remote | A company comfortable taking more HR responsibility when it moves from EOR to its own payroll. Remote’s conversion guide explains its payroll implementation and first-run support, while assigning contracts, amendments, benefits and other HR tasks to the customer after conversion. | Leave this final shortlist for a People lead seeking continuing hands-on employment coordination. Reconsider if the company has its own HR and legal capacity and mainly needs the EOR-to-payroll route. |
Change one assumption and the choice changes: if Teamed can support only one transfer date for all five employees, it leaves this shortlist for the staged plan. GoGlobal moves to first place if its proposal assigns an owner and payroll handoff to each of the two dates. If neither provider accepts the held-employee case, keep the second wave with the incumbent only if it agrees and local advisers confirm lawful continuation through the revised date. Otherwise secure an alternative employment plan before the current arrangement expires; do not promise a transfer date that leaves either employee uncovered.
Send Teamed and GoGlobal the worked roster and ask: “Will your scope run two employer-change dates in Germany, keep the unresolved employee on EOR between them, and name who signs off the final EOR and first entity payroll for each wave?” Select the provider whose written answer completes that plan.