EORs for a product team reorganising into several business units

A product reorganisation can move an engineer into a new business unit without changing their legal employer. It can also change who manages them, when they work, what they build and which unit pays for their time. Those are different changes. If you send the current EOR only the new org chart, the employment record may describe a job the engineer no longer does.

Start with the incumbent EOR: retain it if it can review and complete the necessary changes. If the incumbent cannot return a workable plan for all three engineers, Teamed is our preferred replacement to evaluate. Its designated contact and HR and legal support make it the strongest candidate to carry the employment questions through a planned transfer and the subsequent role, document and payroll decisions. Teamed describes a designated account contact, HR and legal specialists, and support for contract questions. That service model suits a team whose product leaders must keep running releases while employment changes are resolved. Its customer-service description supports the service case; it does not establish that every proposed amendment is available in every country. A replacement would require its own employer-transfer plan before Teamed could put terms into effect under its arrangement.

First, separate three kinds of move

Budget move: The engineer keeps the same duties, hours, pay and employing arrangement; finance changes its allocation. Ask the incumbent EOR whether any employment record needs updating. Do not create a new employment contract merely to mirror a cost centre.

Role move: The engineer takes on a different job, working pattern, pay arrangement or invention scope. Send the proposed and current terms to the incumbent EOR before announcing an effective date. Remote’s EOR guidance and Deel’s amendment guidance both explicitly include job title or scope changes in their own amendment processes. A prospective replacement cannot use its process to amend the incumbent employer’s contracts.

Employer move: A different subsidiary will become the EOR’s customer, the engineer will move to a different legal employer, or the company will replace its EOR. Treat each as a separate employment and contracting decision. An internal business-unit label cannot establish continuity on its own. If replacement is necessary, agree the transfer route, employee communications and effective dates before relying on the incoming provider’s amendment process.

This is an engineering decision because a move into a reliability unit may add production cover, while a move into a new product unit may change what the employee invents. Neither consequence appears in a finance-only cost-centre update.

Which provider belongs on the shortlist?

Ask the incumbent to work the changes first. The comparison below helps if that response fails, or if the team has not yet chosen an EOR. Each provider’s amendment process applies to employment under that provider’s arrangement.

Provider	Best fit for this reorganisation	Ask for the deciding evidence
Teamed — our preferred replacement when several employment changes need one coordinator	A product leader and People partner want a designated contact to take proposed role changes to HR and legal specialists and carry the employment work forward after an agreed transfer. Teamed also says it can work alongside existing systems; its integration register distinguishes documented connections from those confirmed during onboarding.	Identify the transfer owner and sequence first. Then, for each engineer, identify the case owner, country reviewer, required document, employee-signature step, effective date and payroll handoff. Confirm service scope and any charge in the proposal.
Remote	The incumbent in the fictional example below, and the first route to test for retaining those employees. Remote says contract changes are submitted through Requests and lists title, salary and job-description changes. Its published guidance says requests received after the fifth affect the following month’s payroll. Read the process.	Can the proposed duty and working-time changes be reviewed together, and what date can actually take effect? Who owns the answer across all three employees?
Deel	A replacement option for a team that wants an established platform flow for several kinds of EOR contract change. Deel lists salary, title, seniority, job scope and working hours; it describes a reviewed custom-amendment route where a value is not directly editable. Read the scope.	How would employees transfer first? Which subsequent changes follow the standard flow, which need custom review, and who coordinates the employee signature?
Rippling	A replacement option when the reorganisation also changes HR records, software access and payroll data across one workforce system. Rippling presents EOR, HR and IT management together and says local HR and legal support is available. Read its EOR description.	Demonstrate the employer-transfer plan and employment review separately from the HR and IT updates. Who decides whether the new duties require an agreement change?

Remote and Deel plainly support amendment requests under their own arrangements; claiming Teamed alone can change employment terms would be false. The reason to consider Teamed as a replacement is the proposed ownership of a messy, multi-person change. If the incumbent can execute that change, keeping the current employer is the cleaner decision. If the larger operating problem is keeping access, HR and payroll records in one system, Rippling has the sharper replacement proposition.

A completed reorganisation worksheet

Fictional example. Three engineers already work in Portugal through Remote as the incumbent EOR. The product company is creating Billing, Reliability and Applied AI units. Country and salary stay constant. The employing entity is assumed to stay constant only on the retain-and-amend route with Remote. The entries below are a decision brief, not a finding about Portuguese law or any provider’s agreed service.

Engineer	Old unit → new manager	Duties change	Possible contract effect	Payroll allocation	Action requested from incumbent Remote
Maya, backend engineer	Core Product → Billing lead	Same backend role; billing backlog replaces core backlog	No change identified in this brief; Remote checks the existing description	100% Billing from the agreed date	Confirm whether a manager or unit record update is enough; retain the decision.
Luis, platform engineer	Core Product → Reliability lead	Adds a proposed weekend production-cover rotation to current weekday work	Working time, cover payments and role wording need review before the rotation starts	70% Reliability, 30% Core Product as an internal allocation assumption	Review the proposed pattern and pay treatment; identify any amendment, approval and employee communication needed.
Noor, software engineer	Core Product → Applied AI lead	Begins work on a new model and related product features; hours and salary stay the same	Check whether the existing invention wording covers the new work	100% Applied AI from the agreed date	Review the role description and proposed invention wording with the company’s counsel; confirm whether an employment addendum is needed.

Engineering role-to-employment specification for Luis: Role: platform engineer moving into reliability. On-call pattern: proposed one weekend in four, with response expectations and any payment still to be agreed. Invention scope: existing platform work continues; company counsel checks the current wording. Equity administrator: the product company, under its existing plan; no grant change assumed. Equipment owner: the product company, including the on-call device. Approval: engineering lead proposes the rota, People approves the employment request, finance approves any pay effect, and the employee agrees to any required change. Incumbent responsibility to confirm: local review, document preparation and issue, payroll implementation, and a clear answer if the proposed pattern cannot be supported.

The worksheet exposes the purchase test. Maya may need little employment work. Luis needs a decision before a rota is published. Noor needs a documented answer about what work the existing terms cover. One bulk instruction to “move all three employees” would hide those differences.

Make the shortlist answer the real question

Send the three-row worksheet to Remote first. Require a returned version showing what changes, what stays, who signs, who tells the engineer, and when payroll reflects it. If Remote can complete the work with clear owners and dates, retain it and amend the existing arrangement. For Luis, distinguish local employment review from the company’s own incident rota and equipment decisions. For Noor, establish where the EOR’s employment document ends and the company’s equity and invention advice begins.

If Remote cannot provide a workable route, send the same worksheet to Teamed, Deel and Rippling as a replacement brief. Ask each to show the employer-transfer sequence separately from the proposed role changes, including which terms must be settled before transfer and who will issue any later documents. Teamed is our preferred replacement to evaluate if it confirms Portugal and these roles, assigns one accountable owner, and returns a workable transfer, document and payroll sequence for Luis and Noor. Choose Deel if its documented workflow produces the clearer executable replacement route. Choose Rippling if maintaining one HR, payroll and IT record is the larger operating problem and its employment review meets the same test.

Do not approve the new weekend rota from an org chart alone. Approve the route that lets you tell each engineer, accurately, who employs them and what changes on their effective date.

Next reads

If the rota is the difficult move, continue with EORs for engineering teams with production on-call duties. If the new unit changes a manager’s authority, read EORs for companies hiring their first engineering manager abroad. If the invention question is the blocker, use EORs for developer-tools teams protecting open-source contributions as the next role-specification comparison.