You need to transfer South African employees to a new EOR provider without breaking payroll. This is a payroll operations problem before it is a legal or commercial one. Get the cutover right and everything else follows. Get it wrong and the whole team notices on payday.
Most competitor content treats EOR migration as an administrative handover. It is not. It is a controlled multi-stage program. It has named owners at every stage, gates at every decision point, and a parallel payroll run as the essential control before cutover.
This piece sets out the 7-step framework Legends EOR uses when clients migrate in or out. It covers who does what, what evidence needs to change hands, and where the failure points are. Reference it before you sign a migration commercial agreement, not after. For background on the Employer of Record model itself, see our guide to what an EOR is and how it works.
Compare migration approaches before you commit
Not every EOR migration is a switch to another EOR. Three routes solve different problems.
| Migration approach | Payroll and employment continuity checks | Operational workload | When to consider it | Key caution |
| New EOR migration | Reconcile final and first payrolls, review contracts, service dates, benefits, and statutory records | Shared across the client and both EOR providers | You want to continue employing through an EOR without establishing a local entity | Do not treat the provider contract as proof of employment-law continuity |
| Move to a South African entity | Confirm the entity can employ and run payroll, then review contracts, service dates, liabilities, and registrations | Higher internal setup and continuing administration | You have an established entity and want direct control over local employment | Obtain legal and payroll advice before moving employees. See our sibling guide, EOR vs Setting Up an Entity in South Africa, for the cost comparison |
| Termination and rehire | Review final pay, new terms, service treatment, benefits, deductions, and payroll dates | High employee communication and documentation burden | Local advice confirms this structure is appropriate for your case | Termination consequences and continuity outcomes require individual review |
The suitable route depends on your employer structure, employment terms, and workforce profile. South African legal advice should inform the final choice. Between 10 and 20 SA employees on a permanent operating model is where the entity route starts to earn out for many businesses.
The remainder of this piece focuses on the new-EOR migration route. It is the most common scenario for UK companies midway through their SA hiring journey.
Migration timeline benchmarks
Realistic migration duration depends on team size, payroll calendar alignment, and the complexity of the outgoing arrangement.
| Team size | Typical migration duration | Payroll cycles covered |
| 1 to 5 employees | 2 to 4 weeks | Two: final under outgoing, first under incoming |
| 5 to 15 employees | 4 to 6 weeks | Three: two under outgoing, parallel test, first live |
| 15+ employees | 6 to 10 weeks | Four or more: including phased cutover if needed |
These are directional benchmarks based on Legends EOR's observations from migrations completed in the last three years. Your timeline depends on the payroll calendar, contractual notice with the outgoing provider, and whether new contracts are required.
A common mistake is to align cutover with month-end without checking the outgoing provider's notice terms. If notice runs 30 days and month-end is 20 days away, you already have a timing problem. Check both dates before setting the cutover.
What does an EOR migration typically cost?
Direct migration costs are usually small compared to the internal team time required. For a team of 10 to 15 employees, plan for £2,000 to £5,000 in external costs. Add 40 to 80 hours of internal finance, HR, and legal time.
Cost components to model:
- Incoming provider setup fees: Sometimes waived as part of the commercial arrangement. Sometimes charged per employee. Confirm the position in writing during procurement.
- Outgoing provider exit charges: Check the original contract for early-termination fees, final-invoice terms, and administrative charges for data handover.
- Deposit transfers: The outgoing provider's deposit is usually refunded rather than transferred. Budget for a 60- to 90-day return period.
- Legal review costs: SA employment counsel time for the contract review, framework determination, and employee communications. Typically £1,500 to £3,000 for a mid-size team.
- Internal team time: The highest hidden cost. Finance, HR, and legal teams typically absorb 40 to 80 hours across a 4- to 6 week timeline for a team of 10 to 15 employees.
- Employee experience investment: Communication, change management, and post-migration query handling. Usually delivered through existing HR capacity but worth budgeting explicitly.
These figures are directional, based on Legends EOR's observations from migrations completed in the last three years. Your migration cost depends on team size, the complexity of contracts and benefits, and whether new employment contracts are required.
What to expect from the outgoing provider
The outgoing EOR has commercial incentives that shape how it responds to your exit. These are structural realities, not complaints. Plan around them:
- Notice terms may be interpreted more strictly than during onboarding
The provider's account team is often less flexible on exit than on entry. Read the contract, apply the exact wording, and plan cutover dates against those terms.
- Data-return timelines can extend if not contractually fixed
If the contract says "reasonable time" without a fixed deadline, expect the return to take weeks rather than days. Push for a written commitment during Step 2.
- Portal access often ends immediately at exit rather than during a wind-down
Employees may lose access to historical payslips, tax certificates, and personal records on the exit date. Export everything you and employees need before that date.
- Deposit refunds may take 60 to 90 days after migration completion
If the outgoing provider held a deposit, budget for the cash to return two to three months after the last payroll runs.
- Some outgoing providers require final invoices to include the following period even after you have left
Check whether the contract allows an early exit or requires payment through a notice period regardless of when employees transfer.
None of these dynamics is unreasonable on its own. But if you assume goodwill and rely on informal timelines, the migration will slip. Plan against the contract wording and the incentives, not the sales-cycle assurances.
What an EOR migration changes, and what must stay protected
An EOR migration changes the legal employer responsible for employment administration. Your company can continue directing the employee's daily work, priorities, and performance.
The employment-law treatment requires separate analysis from the commercial provider change. Obtain South African legal advice before deciding whether transfer provisions, consultation, termination, or rehire requirements apply.
Before setting the cutover date, identify and verify:
- Salary and variable pay
- Leave balances and benefits
- Original service dates
- Employee deductions
- Tax and payroll records
- Outstanding expenses
- Equity arrangements
- Employee records
- Equipment and system access
Legends EOR can maintain uninterrupted salary payments, correct statutory deductions, and single-currency invoicing during a migration. We also manage the administrative work needed to establish the new payroll arrangement.
The employment relationship and contract position
Contracts
The outgoing EOR is usually the current legal employer. The incoming EOR may need to issue replacement employment contracts, subject to the legal route selected for the transition.
Review each employee's role, remuneration, working arrangements, and contractual benefits. Record any terms that require preservation, confirmation, or fresh agreement.
Service
Confirm how original service dates will be recorded and whether continuity protections apply. Document the agreed treatment before issuing employee communications or finalising contracts.
Legends EOR can replace contracts where required and coordinate the supporting compliance documentation. This work reduces gaps between the commercial arrangement and the employee's legal position.
Payroll, statutory deductions, and year-to-date records
Payroll
Map the final payroll under the outgoing EOR and the first payroll under the incoming EOR through the incoming provider's payroll service. Both providers need the same approved salary, variable pay, and deduction information.
Year-to-date records require careful handling. The incoming EOR needs enough information to configure payroll and maintain accurate employee records. Responsibilities for tax documents and filings must remain clear.
Records
Confirm who retains payroll history, payslips, tax certificates, and proof of statutory deductions. Set access periods for any outgoing provider portal that employees will lose after migration.
Employee benefits, leave, and personal data
Benefits
Compare current membership terms with the incoming arrangements through the employee benefits service. Check enrolment dates, employee contributions, waiting periods, and outstanding claims before promising continuity.
Leave
Obtain an approved balance for each leave category. Decide how each balance will be treated, record the decision, and show the confirmed balance to the employee.
Data
Transfer only the employee information required for employment, payroll, and benefit administration. Legends EOR can support benefit transfers and a secure handover of records to reduce gaps and misclassification risk.
The 7-step migration plan Legends EOR uses
A migration plan needs named owners, decision points, and evidence. The payroll calendar should control the schedule because a missed deadline can affect every employee in the relevant pay cycle.
Legends EOR uses structured onboarding and offboarding processes during moves from another EOR. These processes support payroll continuity and employee engagement throughout the change.
Step 1: Create the contract, employee, and payroll inventory
Accountable owner
The client should appoint one accountable migration lead. Finance, HR, and legal teams can provide inputs, but one person must control the complete inventory.
Compile the following:
- Employee roster
- Signed contracts
- Pay elements
- Benefits and leave balances
- Service dates
- Payroll calendar
- Expense commitments
- Equipment records
Assign a named owner and completion date to every missing item.
Decision point
Decide whether the records are complete enough to support contract review, payroll configuration, and employee communication.
Do not proceed until: every employee has a complete record, or an approved action owner is resolving each gap.
Step 2: Review notice, exit obligations, and transition risks
Accountable owner
The client's commercial or legal lead should own the outgoing-provider review. The payroll lead should confirm processing deadlines and final payment responsibilities.
Review the outgoing provider's exit terms carefully:
- Notice requirements
- Termination clauses
- Deposits and refund conditions
- Final-invoice terms
- Data-return obligations
- Employee communication restrictions
- Unresolved disputes
Notice periods vary by contract, so use the signed agreement rather than an assumed standard.
Decision point
Confirm whether the intended cutover date satisfies commercial obligations and leaves enough time for payroll processing.
Do not proceed until: the outgoing EOR has acknowledged the exit plan, data requirements, and final payroll responsibilities in writing.
Step 3: Onboard the incoming EOR before offboarding the outgoing provider
Accountable owner
The client migration lead remains accountable. The incoming EOR should own its onboarding tasks and report progress against the payroll cutover date.
Legends EOR aligns the transition with South African labour requirements through new contracts where required. Our role can include statutory registration work and compliance checks on employment documentation through the EOR Migration service.
Provide the incoming EOR with the approved employee inventory, payroll calendar, and contract analysis. Complete commercial onboarding early enough to configure and test payroll before the outgoing arrangement ends.
Decision point
Confirm that the incoming EOR can employ and pay each person from the planned start date.
Do not proceed until: required contracts, registrations, payroll settings, and support routes are ready for employee onboarding.
Step 4: Prepare employee records and payroll inputs
Accountable owner
The client's payroll or finance lead should control the handover log. The outgoing EOR supplies records, while the incoming EOR confirms usability.
Record the transfer of:
- Payroll history
- Tax records
- Bank details
- Payment information
- Benefits and leave balances
- Expenses and equity data
- Relevant employee personal data
For every transfer, log data-access permissions, file format, transfer date, authorised recipient, confirmation of receipt, validation result, and deletion or return requirement.
Decision point
Confirm whether the incoming EOR can import, interpret, and reconcile every required record.
Do not proceed until: the handover log shows receipt and validation of all payroll-critical information.
Step 5: Run a parallel payroll validation
Accountable owner
The client payroll lead should approve the comparison. The incoming EOR prepares the test payroll, while the outgoing EOR provides the approved baseline.
Compare the results employee by employee. Check the following as separate controls:
- Salary
- Approved variable pay
- Deductions
- Net pay
- Leave and benefits
- Total invoice values
Record each discrepancy with an owner, explanation, and required correction. Re-run affected calculations after changes rather than relying on a written assurance.
Decision point
Decide whether all differences are expected, supported, and approved.
Do not proceed until: every unexplained payroll discrepancy has a documented resolution and final sign-off.
Step 6: Complete the payroll cutover and employee transfer
Accountable owner
The client migration lead owns the cutover runbook. Each EOR remains responsible for the tasks assigned to it.
The written runbook should confirm the final outgoing payroll and first incoming payroll. It should also cover:
- Contract documents
- Employee acknowledgements
- Payroll approval steps
- Escalation contacts
Set deadlines for client funding, employee data changes, and variable-pay approval. Confirm which provider handles late expenses, corrections, and payroll queries that cross the cutover date.
Decision point
The accountable lead gives or withholds final cutover approval.
Do not proceed until: contracts, payroll sign-off, funding, and employee communications are complete.
Step 7: Reconcile the first payroll and provide post-cutover support
Accountable owner
The client payroll lead should approve the first payroll reconciliation. The incoming EOR should investigate and correct errors within its remit.
Compare the approved test payroll with the live payroll, payment file, invoice, and employee payslips. Confirm that recurring inputs, benefits, and deductions are operating as configured.
Legends EOR applies strict payroll verification and corrects its payroll errors immediately, so clients do not incur penalties for our mistakes. Employee questions and corrections should remain on a tracked log until closure.
Decision point
Close the migration only when payroll, HR, and employee issues have been resolved or assigned for continuing support.
Do not proceed until: payment status is confirmed, and every open exception has an owner, deadline, and employee communication.
The 12-row payroll cutover checklist
Agree which provider processes each item and in which payroll cycle. No balance or obligation should be treated as automatically transferred.
The incoming EOR's setup work can include employment contracts, payroll configuration, and employment documentation. Onboarding and offboarding support can also cover PAYE, UIF, and SDL registration, plus coordination of IT and office access where applicable.
| Cutover item | Outgoing EOR responsibility | Incoming EOR responsibility | Client decision or evidence required | Do not proceed until |
| Final payroll date | Confirm the final cycle, inputs, payment date, and final payslip access | Record the boundary between providers | Approved payroll calendar and written exit confirmation | The final processing date and owner are agreed |
| First payroll date | Confirm no duplicate payment will be made | Confirm the first cycle, funding deadline, and payslip process | Approved start date and payroll sign-off route | The incoming payroll calendar is confirmed |
| Salary | Provide the latest approved salary and payroll record | Configure and validate recurring salary | Signed contract or approved pay record | Salary matches across the contract, payroll, and test |
| Bonus | Confirm approved amounts already processed or outstanding | Process only assigned and approved amounts | Written approval, value, and payment cycle | Ownership and timing are documented |
| Commission | Provide the approved calculation and unpaid position | Configure or process the approved instruction | Commission plan, calculation, and approval | The amount and processing provider are confirmed |
| Leave balances | Supply approved balances by leave category | Record the agreed opening position | Balance report and documented treatment | The client and employee-facing record agree |
| Deductions | List recurring, statutory, and authorised deductions | Configure deductions assigned to the first payroll | Deduction authority and reconciliation evidence | Each deduction has a valid basis and owner |
| Tax certificates | Confirm responsibility for prior-period and final documents | Confirm responsibility from the new employment date | Record of filing and document responsibilities | Employees know where to obtain each document |
| Benefits | Confirm termination, transfer, or continuation arrangements | Complete enrolment and payroll configuration | Membership evidence, contribution details, and approved treatment | Cover dates and deductions are verified |
| Expenses | Identify submitted, approved, and unpaid claims | Process only claims assigned to the new cycle | Approved claim log and cutover rule | Every open expense has a processing owner |
| Equity | Provide payroll-related records and outstanding instructions | Record relevant payroll treatment where applicable | Plan documents and authorised instruction | Legal, tax, and payroll responsibilities are assigned |
| Employee personal data | Export authorised and necessary records securely | Restrict access, confirm receipt, and validate files | Access approval and transfer log | Receipt, access, and retention controls are confirmed |
After completing the table, payroll owners should check:
- Gross-to-net calculations
- Statutory deductions
- Approved pay changes
- Leave records
- Benefit deductions
- Payment status
- Invoice currency
- Employee payslip access
- Payroll query escalation contacts
Verify South African employment and compliance requirements before cutover
A South African compliance checklist should record questions, evidence, and approvals. It should not assume that one legal mechanism applies to every EOR migration.
Local legal counsel should confirm the employment-law position. Payroll and tax advisers should verify responsibilities that depend on the parties, dates, and employee records.
The South African legal frameworks that govern the choice
Three SA employment law frameworks shape how a migration must be handled. Legal counsel should confirm applicability to your migration.
Section 197 of the Labour Relations Act
This governs automatic transfer of employment when a business or part of a business transfers as a going concern. Depending on the arrangement, employees may transfer to the new employer with continuity of service, terms, and conditions preserved by law.
Section 189 of the Labour Relations Act
This governs retrenchment procedures. If the termination-and-rehire route is used, Section 189 sets the required consultation, notice, and severance framework.
The CCMA (Commission for Conciliation, Mediation and Arbitration)
This is the dispute resolution mechanism for South African employment matters. Awards for unfair dismissal can reach twelve months' remuneration. Migration steps that trigger disputes route here.
The commercial migration decision does not determine which framework applies. That determination sits with South African employment counsel based on the facts of your arrangement, your workforce, and the migration approach chosen.
Employment contracts, continuity, and service dates
Confirm whether employees require new contracts and whether existing terms need preservation. Check how job title, salary, benefits, and place of work will appear in the incoming documents.
Ask South African legal counsel to determine whether the arrangement creates transfer, termination, or rehire consequences. Record how prior service will be treated and what employees will receive in writing.
The commercial agreement between providers does not decide the workforce's legal position by itself. Complete the employment review before issuing final documents or making continuity assurances.
PAYE, UIF, SDL, and payroll records
Map responsibility for PAYE, UIF, and SDL administration across the final and first payroll periods. Confirm which party handles registrations, payroll records, and relevant filings.
The compliance file should identify responsibility for:
- Year-to-date payroll records
- Employee payslips
- Tax certificates
- Statutory deduction evidence
- Corrections linked to an earlier cycle
- Employee access to historical documents
Do not close the outgoing account until the responsible team has retained required records. Confirm how employees can obtain documents after portal access ends.
Leave, benefits, and employee entitlements
Reconcile accrued leave by employee and leave category. Document whether balances will be recognised, settled, or handled through another approved route.
Compare benefit membership, contribution rates, and payroll deductions. Check open claims, enrolment requirements, and the date on which each provider's responsibility changes.
Legends EOR's migration support can coordinate benefit transfers and secure record handovers. Our local HR team applies South African labour-law knowledge, while hands-on IT support can help prevent access delays.
Personal-data transfer controls
Identify who has lawful authority to access and transfer employee information. Limit files and permissions to people who need them for the migration.
Use secure transfer methods and retain a complete transfer log. The log should name the sender, recipient, transfer date, files, and validation status.
Confirm the outgoing provider's deletion or return arrangements. Remove temporary access after validation and investigate unexpected downloads, missing files, or unauthorised recipients.
Assign responsibilities before anyone starts the transfer
A responsibility matrix prevents assumptions between the client and both EOR providers. It also gives employees a clear route for questions and required actions.
Legends EOR assigns a dedicated Account Manager and local HR oversight. Employees continue reporting operationally to your company, while we manage employment administration and compliance.
Migration RACI matrix
In this matrix, Responsible completes the work, Accountable gives final approval, Consulted provides input, and Informed receives updates.
| Migration activity | Client | Outgoing EOR | Incoming EOR | Employees |
| Notice delivery | Accountable | Informed | Consulted | Informed |
| Employee roster validation | Accountable | Responsible | Consulted | Consulted |
| Contract review | Accountable | Consulted | Responsible | Consulted |
| Payroll-data export | Accountable | Responsible | Consulted | Informed |
| Benefits and leave confirmation | Accountable | Responsible | Consulted | Consulted |
| New contract issuance where required | Consulted | Informed | Accountable | Responsible |
| Payroll parallel testing | Accountable | Consulted | Responsible | Informed |
| Final payroll approval | Accountable | Responsible | Consulted | Informed |
| First payroll approval | Accountable | Consulted | Responsible | Informed |
| Employee communication | Accountable | Consulted | Responsible | Informed |
| Post-cutover query handling | Accountable | Consulted | Responsible | Consulted |
Adjust the matrix if contractual responsibilities differ. Preserve one accountable decision-maker for each activity.
Legends EOR maintains on-the-ground relationships in Cape Town and Johannesburg with regulators, suppliers, and service providers. This local model supports direct responses from real people, not a dashboard.
Employee communication checklist
Employees should receive clear, sequenced information before they are asked to sign documents or update personal details.
Cover the following points:
- The reason for the operational provider change
- The planned transition date
- Whether day-to-day reporting will change
- Actions each employee must complete
- When contract documents will arrive
- How salary and payslips will work
- How benefits and leave will be checked
- Where employees can raise questions
- How urgent payroll issues will be escalated
Separate confirmed facts from items awaiting review. Avoid unverified assurances about service dates, benefit continuity, tax treatment, or legal transfer status.
Use one controlled communication owner and a shared question log. Record answers that affect contracts or payroll so every employee receives consistent information.
Warning signs from the incoming provider during migration
Migration is when the incoming provider's operational strength gets tested. Five warning signs indicate the provider is not ready to run your payroll.
- Cannot commit to a parallel payroll run
The parallel run is the essential control before cutover. A provider that cannot or will not do one is asking you to trust their configuration without verification. Do not proceed.
- Will not name their local SA support contact
Your employees will have questions on day one. A dashboard is not a substitute for a named person in Cape Town or Johannesburg who can answer them.
- Requires signed contracts before parallel testing
A provider that requires commercial commitment before demonstrating payroll accuracy is protecting itself, not you. Insist on parallel testing before contract signature.
- Cannot provide a migration project plan with dates
A provider without a written project plan is running migration ad hoc. That is where missed deadlines and payroll errors come from.
- Deposit terms that lock you in before the first live payroll
Deposits are commercial norms. But a deposit structure that means you cannot leave in the first cycle if the payroll fails is a lock-in signal, not a commercial one.
None of these red flags is disqualifying on its own if a provider gives you a good reason. But a provider that stumbles on two or more should not be running your migration.
The 10 risks that break EOR migrations
Controlled planning reduces migration risk. It still depends on timely records, client approvals, and appropriate legal review.
The risk register should stay active until the first payroll reconciliation is complete. Owners should update warning signs, controls, and actions throughout the transition.
The cost of a failed cutover
A missed or incorrect payday in South Africa creates immediate and cascading consequences.
First: employees may claim damages under the Basic Conditions of Employment Act and can raise complaints with the Department of Employment and Labour.
Second: employees may resign with constructive dismissal claims, exposing the client to CCMA awards of up to twelve months' remuneration.
Third: trust in the incoming EOR is often unrecoverable. This is why the parallel payroll run and the "do not proceed until" gates matter. The controls exist to prevent the cost, not to explain it after the fact.
The 10 risks in detail
| Risk | Early warning sign | Preventative control | Owner | Contingency action |
| Payroll-data gaps | Missing salary history, bank details, or employee records | Complete the inventory and assign owners to gaps | Client payroll lead | Escalate missing records and hold cutover approval |
| Unclear exit obligations | The outgoing EOR disputes timing or final responsibilities | Review notice, termination, and data-return clauses early | Client legal or commercial lead | Revise the cutover plan and obtain legal advice |
| Missed payroll deadlines | Inputs or funding remain unapproved near processing cut-off | Use a payroll calendar with named approvers | Client finance lead | Escalate to the named decision-maker and apply the approved correction process |
| Contract delays | Employees have not received or acknowledged required documents | Track drafting, review, issue, and acknowledgement separately | Incoming EOR | Escalate unresolved terms and reassess the employment start date |
| Benefit discrepancies | Contribution details or enrolment dates do not match | Compare membership and payroll records before onboarding | Incoming EOR HR lead | Contact affected employees and arrange the approved interim response |
| Deductions errors | Test payroll differs from the authorised deduction record | Reconcile every deduction during parallel testing | Incoming EOR payroll lead | Correct the instruction and re-run the affected calculation |
| Incorrect leave balances | Employee, client, and outgoing records show different values | Obtain approved balances by leave category | Client HR lead | Investigate source records and issue a corrected opening balance |
| Employee confusion | Repeated questions or missed employee actions | Issue sequenced communications with one question route | Client migration lead | Hold a briefing and send an updated written explanation |
| Inaccessible payroll records | Portal access ends before records are downloaded | Export and validate required history before closure | Outgoing EOR | Request a formal record retrieval and log missing documents |
| Data-transfer issues | Files are incomplete, corrupted, or sent to unauthorised recipients | Use controlled access, secure transfer, and receipt checks | Client data owner | Restrict access, investigate the incident, and resend validated files securely |
Contingency plan for payroll exceptions
Set one named decision-maker for payroll exceptions. Provide employees with an emergency contact route that does not depend on access to an old provider portal.
Before live payroll, document:
- The correction approval process
- The person authorised to release funding
- The route for urgent employee queries
- The evidence required for a correction
- The escalation contacts at both providers
- The method for tracking closure
Legends EOR provides HR and payroll handover support during a provider switch. This includes local HR oversight and coordinated payroll continuity controls.
Confirm funding before the payment process begins. If an exception occurs, tell the affected employee what is known, who owns the correction, and when the next update will arrive.
A worked migration example
Consider a team of 8 South African employees currently on a platform-only EOR. Migrating to a full-service EOR typically takes 4 to 6 weeks and covers three payroll cycles.
Week 0
Migration lead appointed. Employee inventory started. Outgoing provider notice terms reviewed.
Weeks 1 to 2
Employee inventory completed. Contracts reviewed. Incoming EOR selected and commercial onboarding started. Payroll calendar agreed.
Week 3
Payroll under the outgoing provider runs as normal. Incoming EOR configures test payroll based on inventory. Contract documents prepared.
Week 4
Parallel payroll test runs at the incoming EOR. Discrepancies logged and resolved. Employees receive communication about the change and any contract updates.
Week 5
Final payroll under the outgoing provider processes normally. New contracts signed. Data handover completed with validated transfer log.
Week 6
First live payroll under the incoming provider. Reconciliation against test results. Payslip access verified. Post-cutover query log opened.
This timeline assumes the outgoing provider's notice terms allow the pace. It also assumes the payroll calendar aligns with the cutover date and the parallel run does not surface material discrepancies. Larger teams and complex benefit arrangements can extend the timeline by 2 to 4 weeks.
After the migration: what changes for your team
The migration ends with Step 7. Your team continues operating under the new arrangement from Day 1 of the first live payroll onwards. Set expectations across the following areas.
- Payroll cadence
Payroll runs on the new provider's calendar. Cutoff dates for variable pay approval, expense submissions, and employee data changes may differ from the outgoing arrangement.
- HR queries
Employees route questions to the new provider's local team rather than the outgoing portal. Update internal manager guidance to reflect the new escalation path.
- Benefits administration
The look and feel of benefits enrolment, claims processes, and member portals may change. Prepare employees for the transition even where the underlying benefits are equivalent.
- Payslip formatting
Employees may notice line-item and layout differences on the first payslip. Communicate this in advance so the differences do not trigger unnecessary queries.
- Internal team involvement
Your finance, HR, and legal teams shift from migration project management to routine oversight. Document who owns which ongoing responsibility.
None of these is a problem. But each is a change employees will notice. Plan the communication rather than leave it to chance.
Why Legends EOR handles migrations differently
Legends EOR employs 1,846 South African professionals for 326 international clients across offices in Cape Town and Johannesburg. Migration support forms part of the EOR Migration service.
Four elements distinguish Legends' approach:
- Named account manager and local HR oversight
Every migrating client works with one named contact through the transition, plus a local HR team that understands South African labour law and the CCMA process.
- Parallel payroll testing before cutover
Legends completes a full parallel run against the outgoing baseline for every migration, not just complex ones. This is the control that catches configuration errors before they hit real employees.
- Single-currency invoicing to UK clients
Legends invoices UK clients in sterling with a transparent FX position. This avoids the double-conversion cost that platform-only providers often build into rand-denominated arrangements.
- Payroll error responsibility
Legends EOR applies strict payroll verification and corrects its payroll errors immediately, so clients do not incur penalties for our mistakes. This is a contractual commitment, not an operational aspiration.
Ready to plan your migration?
Migration decisions should start with the payroll calendar, not the sales conversation.
Ready to size the cost of the destination? Use our Salary Benchmarking Tool to compare UK and SA employment costs by role.
Weighing an EOR migration against setting up your own SA entity? See our sibling guide, EOR vs Setting Up an Entity in South Africa, for the cost comparison.
Want to see the wider cost picture? Our page on how UK businesses save by hiring in South Africa breaks down the total-cost-of-workforce calculation.
Ready to plan your migration? Schedule a free consultation to review your payroll calendar, employee data, contracts, and transition risks. Get a personalised migration plan within 48 hours.
Legends EOR can support payroll continuity, statutory deductions, and contract replacement where needed. We also coordinate benefit transfers, secure records handovers, and structured onboarding and offboarding.