Microfinance core banking migration and data cutover: cost 2026

The verdict in three sentences

For a microfinance institution with 25,000 clients, the main migration risk is not the software chosen but data migration: balances, repayment schedules, collateral and arrears history. The 2026 budget sits between FCFA 15 and 60 million (about EUR 22,870 to 91,470) for core banking and FCFA 3 to 8 million for extraction, cleansing and reconciliation. The non-negotiable rule: 2 to 3 dry-run cutovers and a portfolio at risk at 30 days (PAR 30) rebuilt identically before the real cutover, otherwise next month's BCEAO reporting becomes indefensible.

Why unmaintained software becomes a prudential risk

A core banking system whose vendor has disappeared or no longer ships fixes exposes the MFI to three concrete risks: inability to adapt regulatory reports when the BCEAO changes its templates, unpatched security flaws on an often ageing server, and dependence on one or two in-house IT staff who alone know how to produce the reports. Inspections regularly flag the lack of a maintenance contract and business continuity plan.

For 25,000 clients, SaaS at USD 1 per account comes to roughly FCFA 180 million over 10 years. That figure must be compared with licence plus maintenance over the same period before signing.

Data migration: where projects fail

The migration workstream breaks down into separate lots, each with a quantified reconciliation check. The FCFA 3 to 8 million cost depends mostly on source data quality: duplicate clients, restructured loans keyed as new loans, unlinked collateral.

Each dry run replays the whole chain on a production copy: extract, transform, load, then compare trial balances and portfolio reports. The first one usually surfaces 2,000 to 5,000 anomalies, the second a few hundred, the third must reach zero variance on accounting balances.

Typical timeline and success conditions

A realistic project runs 7 to 10 months: 6 weeks of scoping and data audit, 3 to 4 months configuring products (rates, fees, declining or flat schedules), then 2 months of dry runs and training branch staff. The real cutover happens at month-end, over a weekend, after the accounting close. Branches run in degraded mode (numbered paper receipts) for 24 to 48 hours at most.

Three conditions make the difference: a steering committee including finance and internal control, a freeze on new products for the last 3 months, and a 1-month parallel run where the old system stays available read-only.

Mini case study

Illustrative scenario: Mr Ouedraogo, operations director of an MFI in Ouagadougou, manages 25,000 clients, 9,500 active loans and a FCFA 6.2 billion portfolio. Budget retained: regional core banking at FCFA 24 million, data migration at FCFA 5.5 million, training and support at FCFA 2.5 million, i.e. FCFA 32 million (about EUR 48,780).

Expected gain: today, 3 staff spend 6 days a month manually rebuilding BCEAO reports and PAR, i.e. 18 person-days. At FCFA 450,000 monthly loaded cost per person, automation frees about FCFA 370,000 per month. The main gain lies elsewhere: a 1-point drop in PAR 30 thanks to automated SMS reminders means FCFA 62 million of portfolio better monitored, far beyond the project cost.

FAQ

How many dry runs should we plan?

At least 2, ideally 3. The FCFA 3 to 8 million migration budget must include them explicitly, each one tying up the accounting team for 3 to 5 days of reconciliation.

What if source data is inconsistent?

Fix it at source where possible, otherwise document every adjustment with internal control sign-off. On a 25,000-client base, 3 to 8% duplicates is a common level.

Is BCEAO reporting included in core banking?

Regional solutions usually ship the main reports, but configuring them to your chart of accounts takes 3 to 6 weeks. Test at least 2 monthly closes before cutover.

Can we keep the old software for lookups?

Yes, and it is recommended for 6 to 12 months read-only, to handle complaints. Full archiving must respect a 10-year retention period for accounting records.

Should mobile money be connected from day one?

Not necessarily. An Orange Money or Moov Money integration for repayments is often planned as phase 2, 2 to 3 months after cutover.

Let's scope your project. Send us your number of clients, active loans and the name of your current software: we will price the data audit and migration, with an indicative budget and cutover calendar. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.