Every EOR Relationship Should Have an Expiration Date
EOR is a tool, not a permanent infrastructure. The companies that use it best treat it as a bridge — fast market entry, compliance coverage while you test headcount growth, and a clean exit when the numbers justify your own entity. The ones who stay on EOR indefinitely at 30+ employees in a single country are overpaying by $100,000–$300,000 per year in fees that would disappear with a local entity.
The strongest next step is to pair this viewpoint with EOR comparisons, EOR cost modeling, and term-level clarity in the EOR glossary.
The breakeven point varies by country, but the rule of thumb holds: once you have 8–15 employees in a single market, the math tilts toward entity setup. The question isn’t whether to exit — it’s how to do it without disrupting your employees, your compliance posture, or your operations.
When to Start Planning the Exit
Three signals that it’s time:
Headcount concentration. You have 10+ employees in a single country through your EOR. At $500/month per employee, that’s $60,000/year in EOR fees for that country alone. A local entity costs $15,000–$50,000 to set up (depending on jurisdiction) and $3,000–$8,000/month to maintain with local payroll, accounting, and compliance. The crossover happens fast.
Strategic commitment. You’ve decided this market is permanent. If you’re testing whether Brazil works for your engineering team, keep the EOR. If you’ve hired 12 engineers in São Paulo and plan to double that number, it’s time to own your infrastructure.
EOR limitations are hurting you. Certain things are harder through an EOR: equity compensation (the EOR entity can’t issue your stock options), signing authority for local contracts, applying for government grants or incentives that require a local entity, and building a local brand as an employer. If any of these matter to your business, the EOR has become a constraint.
The Transition Timeline by Country
Entity setup speed varies dramatically. Plan your exit around the slowest step, which is almost always government registration.
| Country | Entity setup time | Employee transfer time | Total transition |
|---|---|---|---|
| United Kingdom | 1–2 weeks (Ltd) | 2–4 weeks | 4–6 weeks |
| Singapore | 1–2 weeks (Pte Ltd) | 2–4 weeks | 4–6 weeks |
| United States | 1–4 weeks (varies by state) | 2–4 weeks | 4–8 weeks |
| Germany | 4–8 weeks (GmbH) | 4–6 weeks | 8–14 weeks |
| India | 4–8 weeks (Pvt Ltd) | 4–6 weeks | 8–14 weeks |
| Brazil | 8–16 weeks (LTDA) | 6–8 weeks | 14–24 weeks |
| France | 4–8 weeks (SAS) | 4–8 weeks | 8–16 weeks |
| Japan | 4–12 weeks (KK or GK) | 4–8 weeks | 8–20 weeks |
“Employee transfer time” includes drafting new employment contracts under your entity, obtaining employee consent, handling any statutory notice or consultation requirements, and processing the administrative transfer of benefits and payroll. These steps can overlap with entity setup but can’t start until the entity is legally registered and has the necessary employer registrations (tax, social security, insurance).
Brazil deserves special attention. The entity registration process involves the Junta Comercial (commercial registry), Receita Federal (tax authority), INSS (social security), FGTS (severance fund), and municipal authorities. Each step has dependencies on the previous one. Rushing it causes errors that create compliance problems for years.
The Employee Transfer Process
This is where most transitions go wrong. You’re not “moving” employees — legally, you’re terminating their employment with the EOR entity and hiring them as new employees of your entity. That distinction matters because:
Termination triggers statutory obligations. In many countries, ending an employment relationship — even when the employee immediately starts a new one with you — triggers severance, notice periods, or terminal benefits. In Brazil, “termination without cause” requires payment of a 40% FGTS penalty. In Germany, termination after 6 months requires social justification. In India, gratuity vests after 5 years. Your EOR provider should help you structure the transfer to minimize these costs, but they can’t eliminate them in every jurisdiction.
Continuity of service matters. The best practice is to recognize the employee’s original start date with the EOR for purposes of vacation accrual, seniority, and benefits eligibility under your new entity. This isn’t legally required in most countries (the new employment is technically a new relationship), but failing to do it signals to employees that the transition is a downgrade. Put it in writing in the new employment contract.
Benefits gaps must be avoided. The employee’s health insurance, pension contributions, and other benefits through the EOR end on their termination date. Your entity’s benefits must start on day one of the new employment. Any gap — even a single day — creates personal liability for the employee (no health coverage) and erodes trust. Coordinate the effective dates precisely.
Consent is required. You cannot unilaterally transfer an employee from an EOR to your entity. The employee must agree to the new terms. In practice, most employees welcome the transfer (it usually comes with direct equity eligibility and the stability of employment with their actual employer). But the legal requirement for consent means you need to communicate the transition clearly, share the new contract in advance, and give employees time to review.
How to Plan the Transition
Phase 1: Decision and entity setup (Month 1–3). Decide which country or countries to transition. Engage a local law firm or incorporation service to set up the entity. Begin employer registrations in parallel where possible. Notify your EOR provider — most contracts require 30–90 days’ notice of intent to off-board employees.
Phase 2: Employment contracts and benefits design (Month 2–4). Draft employment contracts under local law for your new entity. Design the benefits package — aim to match or exceed what the EOR was providing. If you’re offering equity, set up the local stock option plan or RSU scheme. Get local legal review of all contracts.
Phase 3: Employee communication and consent (Month 3–4). Share the transition plan with affected employees. Provide new contracts for review. Address questions about benefits continuity, equity, and any changes to terms. Collect signed contracts.
Phase 4: Cutover (Month 4–5). Coordinate the termination date with EOR and the start date with your entity. Process final payroll through the EOR (including any accrued vacation payout). Process first payroll through your entity. Transfer benefits enrollment. Confirm all statutory registrations are active.
Phase 5: Post-transition audit (Month 5–6). Verify all employees are correctly registered with tax and social security authorities under your entity. Confirm benefits are active and claims are processing. Close out the EOR relationship and retrieve any deposits.
What Your EOR Provider Should Do During the Exit
Good EOR providers support clean exits. Here’s what to expect — and what to push for if it’s not offered:
Transition support. Your provider should assign a dedicated contact for the transition, provide employment contract templates or reference terms, and share historical payroll data for each employee. Deel and Remote both offer structured off-boarding processes. Some smaller providers make exits painful, hoping friction keeps you on their platform.
Deposit return. Most providers hold a security deposit (typically one month’s gross salary per employee). This should be returned within 30–60 days after the final payroll run. Get the return timeline in writing before the transition starts. Some providers hold deposits for 90–180 days citing “contingent liability” — push back on anything beyond 60 days.
Data handover. Request complete payroll records, tax filings, benefits enrollment history, and any employment-related documents filed with local authorities. You’ll need this for your entity’s records and for continuity of the employment relationship.
No penalty clauses. Review your EOR contract for early termination penalties or minimum commitment periods. Enterprise contracts sometimes include 12-month minimums with penalties for early exit. Know your exposure before you start the transition.
The Hybrid Model: EOR + Entity
You don’t have to go all-or-nothing. Many companies set up entities in their top 2–3 markets while keeping EOR coverage for countries with fewer than 5 employees. This hybrid approach optimizes cost (entity where headcount justifies it, EOR where it doesn’t) and speed (EOR for new markets you’re still testing).
The hybrid model works best when your EOR provider also offers global payroll services for your own entities. Deel, Remote, and Rippling all offer this, meaning you can run entity-employed and EOR-employed workers through a single platform. That consolidation saves your HR and finance teams significant time on reporting and reconciliation.
The exit from EOR isn’t a breakup — it’s a graduation. The best providers know this and build their relationship model around earning the global payroll contract that follows the EOR exit. The worst ones make the exit painful enough that you stay longer than you should.
To move from strategy to execution, use remote jobs by country and benchmark provider options in EOR comparisons.
Further Reading
- EOR vs. Entity Setup — When to stick with EOR and when to build your own infrastructure
- EOR for Enterprise — How enterprise companies use EOR strategically alongside owned entities
- Deel Review — Off-boarding process, deposit return, and transition support
- Remote Review — How Remote handles entity transitions and global payroll
- What Is Global Payroll? — The service your EOR provider wants to sell you after you set up your entity
- Compare EOR providers
Was this page helpful?
Tell us or send a correction.