EORs for companies keeping a customer-support team after divesting a product

Our pick for the seller retaining P1 and P2 after selling their Portuguese employing company is Teamed, once their employment route is agreed. Its Portugal EOR through its own entity, local HR and legal support make it the strongest provider to scope for the new contracts, benefit dates and first payroll before the TSA ends. Teamed also offers a route to the seller’s own entity later. The deal team still decides which employees stay with each business and how they can lawfully move.

A product can leave while some of its support people stay. The deal’s employee list, the payroll list and the team the seller intends to keep may then describe three different groups. Resolve that mismatch before comparing EOR proposals. Otherwise the seller risks choosing a provider for someone the buyer will employ, or discovering too late that the retained team still depends on the sold entity for pay and benefits.

Decide who actually needs a new employer

Start with the legal employing entity for each person, the activity being sold and the work each person will do after closing. Then identify the last date the TSA covers payroll, benefits administration and the access needed to serve customers. A TSA can buy time; it is not a permanent employing arrangement.

If the seller keeps a functioning local entity that can continue employing the team, retaining direct employment may be the simpler answer. If the buyer takes the employing entity and the seller keeps selected people, an EOR can provide a new local employer once the permitted transfer route and effective date are settled. In Portugal, the transaction and any proposed change of employer need country-specific review; an allocation in the deal spreadsheet is not itself an employment transfer.

Worked deal-perimeter continuity planner

Fictional example and assumptions. A UK software seller closes the sale of one product and its employing company, ProductCo Portugal Lda, on 1 November 2026. All three people below are Portugal-based customer-support agents employed by ProductCo. The seller keeps its other subscription product but has no Portuguese entity. Under the assumed TSA, ProductCo continues payroll and benefits administration through 31 January 2027. The proposed receiving date for retained staff is 1 February 2027. These dates and arrangements are illustrations, not a provider commitment or a conclusion about how Portuguese transfer rules apply. Further fictional assumption: the seller and buyer agree that, during the TSA, ProductCo will keep employing P1 and P2 while they answer tickets for the seller’s remaining product under the seller’s UK support lead. The seller provides a separate helpdesk queue and credentials for that work; the buyer keeps the sold-product queue and its customer records. The deal documents and local advisers would have to validate that service and management arrangement.

Employing entity	Acquired activity	Retained employee	TSA end	Payroll owner	Benefit handoff	Receiving provider	Unresolved dependency
ProductCo Portugal Lda, sold to buyer	Sold product; agent P1 moves to support the seller’s remaining product	P1: yes	31 Jan 2027	ProductCo through Jan; proposed EOR from Feb	Reconcile existing cover, accrued leave and the proposed new package before notice to P1	Teamed proposed, subject to written Portugal and role acceptance	Deal counsel confirms P1’s route and date plus TSA authority for seller-directed work; seller and buyer approve the separate helpdesk access
ProductCo Portugal Lda, sold to buyer	Sold product; agent P2 moves to support the seller’s remaining product	P2: yes	31 Jan 2027	ProductCo through Jan; proposed EOR from Feb	Same comparison as P1, recorded for P2’s actual terms	Teamed proposed, subject to written Portugal and role acceptance	Seller and buyer release P2’s records and reconcile earned bonus; proposed allowance and first payroll terms need agreement
ProductCo Portugal Lda, sold to buyer	Sold product; agent P3 continues supporting it for the buyer	P3: no	31 Jan 2027 for shared services, if needed	ProductCo continues	Buyer verifies continuing cover and any TSA service change	No new EOR in this plan	Buyer confirms P3’s manager and post-TSA customer-system access

The payroll rows identify the people; this fictional support-team staff map identifies the work and the employer action the proposal must cover. The access arrangements below are assumptions to agree between seller and buyer, not capabilities an EOR can grant.

Person and retained role	Duties after closing	Manager and customer-system access	Pay treatment	Employer action before 1 February
P1 — retained support agent	Handle login and billing tickets for the seller’s remaining product, rather than the sold product.	Seller’s UK support lead directs the work during the TSA and after handoff. Seller issues access only to its separate remaining-product helpdesk queue; buyer removes P1’s sold-product access at closing.	Base pay unchanged in the proposed new terms; ProductCo remains responsible for pay through January under the assumed TSA.	ProductCo supplies P1’s contract, leave and benefit records; the receiving EOR reviews the actual duties and manager, agrees opening terms and benefit dates, and confirms the first payroll input with the seller.
P2 — retained support agent	Handle Portuguese-language tickets and escalations for that same remaining product.	Same UK lead and segregated seller queue as P1; no continuing access to the buyer’s sold-product records.	ProductCo reconciles any earned sold-product bonus. The seller proposes, subject to agreement and local review, to replace the product-specific bonus with a fixed language allowance from 1 February; no amount is assumed.	ProductCo and seller settle the bonus record; the receiving EOR reviews the proposed compensation change and obtains agreed terms before including P2 in opening payroll.
P3 — buyer’s support agent	Continue sold-product customer support for the buyer.	Buyer’s support lead and buyer-controlled sold-product queue; seller grants P3 no remaining-product access.	ProductCo continues P3’s existing pay in this example; any later change is the buyer’s decision.	Buyer confirms P3’s manager, access and post-TSA payroll and benefits owner. No receiving EOR is proposed for P3.

That split changes the purchase: Teamed is being evaluated for P1 and P2’s new work and terms, not for every employee on ProductCo’s payroll. The proposal must accept seller-directed support duties and show how ProductCo’s records become approved opening payroll inputs. P2’s bonus-to-allowance decision is a separate gate: if agreed terms and payroll inputs are not ready by the relevant cutoff, do not promise P2 a 1 February EOR start. Negotiate continued TSA coverage or another lawful interim arrangement for P2. P1 keeps the proposed date only if P1’s own transfer route, records and receiving terms are ready. P3 belongs to the buyer’s operating plan.

Which providers belong on this shortlist?

Provider	Best fit for this decision	What to ask it to demonstrate
Teamed — our pick for this small retained Portugal team	A seller keeping P1 and P2 after ProductCo is sold needs the proposed new employer to document their terms, record P2’s agreed pay treatment, start benefits and run the first payroll. Teamed’s Portuguese entity and HR and legal support fit that two-person handoff, with an own-entity route to scope later.	Identify the proposed legal employer, the person coordinating the handoff, the records needed from ProductCo, the benefit start dates and the first payroll approval sequence. Confirm the actual Portugal role and transaction scope in writing.
Safeguard Global	A substantial comparator when the TSA deadline and wider deal work call for a provider with an explicit M&A workforce offer. Its published M&A service addresses EOR bridges, payroll, HR and entity setup.	Show how its deal team would coordinate the seller, buyer and TSA owners for these two retained employees, including the point at which its EOR becomes responsible.
G-P — wider-deal context	Its published M&A workforce integration offer and Portugal EOR coverage frame a broader, multi-country transaction.	Use that published scope to frame questions about transfer plans and owners for employment, benefits and employee communication if the deal widens.
Deel	Strong where the seller also needs a broader HR and payroll execution platform. Deel says it supports parallel or hybrid models during carve-outs and links employment data with enterprise systems.	Demonstrate the exact ProductCo-to-new-employer workflow and which records will move, especially if the seller’s HR system is the source of truth.
Remote	Strong where the seller values an owned-entity EOR model and a consolidated employment platform. Remote lists acquired teams among its EOR use cases and offers EOR service in Portugal.	Show the proposed Portuguese employing arrangement, benefits transition and employee contact route for this specific divestiture.

Those are different reasons to buy. For two retained agents in one country, Teamed’s combination of practical employment support and a later entity path is the most relevant starting point. For a transaction involving many countries, several workforce types or a central integration programme, Safeguard Global could be the better lead; G-P’s M&A offer provides context for that wider comparison. Deel and Remote merit a place when their platform or entity model is a stated requirement. None of the providers’ general EOR pages proves that this particular sale can use the proposed effective date.

Teamed’s switching guidance explains the records, terms and payroll checks it seeks for an employer change. Its Portugal material identifies its local entity and support model. Use those as evidence for a shortlist invitation, then require a proposal for this seller, role and TSA. An ordinary EOR switch is not the same transaction as retaining people from a sold employing company.

The handoff to demand before signing

Give each finalist the same redacted P1–P2 pack: current employer and contracts; actual pay, any bonus P2 earned, leave and benefits; the proposed duties, UK manager and access split; TSA expiry; payroll results and cutoffs; and the buyer’s record-release contact. Ask for one written sequence showing who employs and pays each person on 31 January and 1 February, when benefits change, who tells the employee, and what happens if an approval or record arrives late. Keep customer-system access on a separate line: an EOR cannot grant the seller rights to the buyer’s product or data.

Decision: Invite Teamed to lead the two-person Portugal proposal, with Safeguard Global as the transaction comparator. Use G-P’s published M&A offer as context if the deal expands beyond this small Portugal team. Do not sign or announce the new employer until the seller, buyer and local advisers have fixed the employee perimeter and a receiving provider has accepted the dated handoff. If the seller’s own Portuguese entity can keep P1 and P2 employed, use that route instead of buying an unnecessary EOR bridge.

Planned companion reads

• Deal perimeter and employee continuity planner — extend the map to every employee, entity and TSA service.
• The TSA ends before your employment setup is ready — decide what must change when the proposed handoff date cannot be met.
• EOR providers for a carve-out retaining a small overseas team — compare the broader small-team carve-out decision.