Most African HR teams know their spreadsheet payroll has to go. The blocker isn't deciding — it's how to switch without missing a pay cycle, losing historical data, or burning out the two people who actually understand the current spreadsheet.

This is the playbook we run with new SmartHR Africa customers moving off spreadsheets. Ninety days, week by week, from kick-off to the first full live cycle. Written for HR managers, payroll administrators, and finance leads — the people actually doing the work.

Before day 1: what to have ready

You're not ready to start until you have:

Buy-in from the person who signs payroll (CFO, MD, or HR director). Without it, the project stalls every time it needs a decision.
A named project lead on your side who can spend at least 30% of their time on the migration for 12 weeks. This is usually the senior HR or payroll administrator.
The current payroll spreadsheet — exactly as it was last cycle — plus the contracts, statutory registration documents, and most recent payroll reports.
A list of every country you operate in, with statutory IDs (KRA PIN, NSSF number, SARS number, PAYE registration etc.) per entity.
A target go-live month. The first full cycle in the new system should be at least 8 weeks from kick-off — anything faster fails.

Weeks 1–2: discovery and data audit

The discovery phase isn't a vendor sales pitch. It's an honest audit of your current state.

Map every employee. Active, on leave, terminated in the current FY. Confirm the headcount in your spreadsheet matches the headcount in your contracts.
Map every pay element. Basic, allowances (housing, transport, meal, communications), overtime, bonus structures, commission. For each: how is it calculated, what triggers it, who approves changes?
Map every deduction. Statutory (PAYE, SHIF, NSSF, Housing Levy in Kenya; PAYE, UIF, SDL in SA; etc.), pension contributions, SACCO, loan repayments, salary advances, garnishees.
Map every leave type and its accrual rule. Annual, sick, maternity, paternity, study, compassionate, unpaid. The accrual rate (e.g. 1.75 days/month for 21-day annual), the carry-forward rule, the cash-out policy.
Identify the edge cases. The employee with the unusual contract. The maternity case in progress. The pension fund transferring in. The cross-country transfer. Each one is a future migration headache if not surfaced now.

For multi-country teams, the country guides are the reference for what statutory items to confirm per country.

Weeks 3–4: configuration in the new system

Now the data is mapped, configuration begins in the new system. This is mostly the vendor's implementation team's work, with your review.

Company entity setup per country, with statutory IDs.
Pay structures: basic + allowances + deductions templates per role family.
Leave types with country-specific accrual rules.
Statutory configuration: PAYE bands, social security rates, deduction caps — confirmed against current gazette.
Roles and permissions: Global Admin, country HR, supervisor, employee ESS.
Custom workflows: leave approval chain, overtime approval, document approval.

By the end of week 4, the system should be configured to the point where you can manually create a test employee, run a test payslip, and have the numbers match what your current spreadsheet would produce. This is the gate before bulk data migration.

Weeks 5–6: data migration and validation

Bulk import of historical and current data:

Employee master data: personal details, contracts, statutory IDs, bank/mobile money accounts.
Current pay structure per employee: gross, allowances, deductions, year-to-date totals.
Leave balances as of the cut-over date.
Loan and advance balances.
Open salary advances and pending approvals.

Validation is the critical step. For every employee, run a test payslip in the new system using last month's source data and compare line-by-line against the actual payslip you issued. Any variance beyond rounding (a cent or two) gets investigated. Don't accept "close enough" — the variance will compound across cycles.

Weeks 7–8: parallel run

Run the next payroll cycle in both systems simultaneously. Your existing spreadsheet stays the official record. The new system produces a parallel output. Reconcile line-by-line. Investigate every variance.

Common variances:

Pro-rata calculation differences for new hires, leavers, and mid-month changes — usually traceable to a different day-count basis (working days vs calendar days).
Overtime rate differences — usually traceable to a different basis (basic only vs basic plus allowances).
Statutory rounding differences — usually fine, but worth documenting.
Leave balance differences — usually traceable to a different accrual start date or pro-rata method.

By end of week 8, the parallel run output should match your live output within a defensible tolerance. If it doesn't, do a second parallel run before going live — never skip this step under pressure.

Weeks 9–10: training

Two audiences:

HR / payroll administrators who will run the system day-to-day. 4–6 hours of structured training plus a recorded reference video. Cover the monthly cycle (data entry → payslip review → approval → disbursement → statutory submission), leave processing, employee onboarding, employee exit.
Managers and supervisors who approve leave, timesheets, and overtime. 1 hour, ideally live with Q&A.
Employees using the ESS portal. 15-minute video walking through the mobile app, payslip download, leave application.

Pin the recorded materials inside your intranet. People will need them again in month two.

Weeks 11–12: go-live

The first full live cycle in the new system, with the spreadsheet retired (but not deleted — keep it as a fallback for 90 more days).

Run the cycle in the new system only.
Reconcile against the spreadsheet (kept in shadow mode) one last time.
Issue payslips through ESS.
Disburse via the live bank file or mobile money batch.
File statutory returns from the new system's outputs.

At end of week 12, the spreadsheet is no longer maintained. It's archived as historical reference. The next 90 days are stabilisation: the system is live, you fix the few things that surfaced during the first cycle, and by month 4 the team has stopped reaching for the spreadsheet by reflex.

Mistakes that derail migration projects

Trying to go live in 4 weeks. The parallel-run step gets skipped; variance is discovered live, in front of staff payslips. Trust evaporates.
Not naming a single project lead on your side. Decisions take a week each. Twelve weeks becomes thirty.
Skipping edge cases. The one unusual contract becomes the production blocker on day one.
Going live without statutory year-to-date totals migrated. The end-of-year tax certificate (P9 in Kenya, IRP5 in SA, etc.) is then a manual rebuild.
Migrating mid-year without a clear approach to mid-year tax catch-up. Some employees end up over- or under-withheld.
Not running a fire drill before go-live. What happens if the bank file is rejected? Who fixes it? Who pays staff today? Run the scenario before it's real.

The 90-day checklist

Week 1–2: discovery and data audit ✓
Week 3–4: system configuration and test payslip validation ✓
Week 5–6: data migration and per-employee validation ✓
Week 7–8: parallel run with full reconciliation ✓
Week 9–10: training (admins, managers, employees) ✓
Week 11–12: go-live, first full cycle, fallback drill ✓

If you're at the start of this and want a working session to map your specific situation — current spreadsheet, country list, edge cases — book a 30-minute discovery call. Or if you'd rather try the system first, start a free trial with your own employee data.

From Spreadsheet to System: a 90-Day HR & Payroll Migration Playbook for African Teams