The Excel inheritance
Walk into almost any African public sector directorate and you will find Excel everywhere. Provincial summaries in one spreadsheet, certification logs in another, multiplier registries in a third, monthly stock reports emailed as attachments and consolidated by hand. The format is familiar, flexible, and free, which explains its dominance. It is also fundamentally incompatible with national governance at scale.
The limits show up the moment two questions are asked together. Which provinces had certified seed shortages last quarter, broken down by variety. Which multipliers have produced lots that later failed certification, broken down by season. With Excel, these answers require manual aggregation that takes weeks. With a unified platform, they are queries.
The migration is not a tooling exercise
The temptation is to treat the migration as a software procurement. Buy a platform, import the spreadsheets, declare victory. This approach almost always fails, for reasons that have nothing to do with the software.
The spreadsheets contain implicit governance rules. Which fields are mandatory. Who validates what. How exceptions are handled. How disputes are resolved. These rules are encoded in the heads of the staff who maintain the spreadsheets, in column headers that mean different things in different provinces, and in informal email threads that never enter the data. A migration that ignores this implicit layer produces a platform that nobody trusts and nobody uses.
What the migration actually involves
Done properly, the migration is a governance transition with three concurrent workstreams. A diagnostic phase that maps the implicit rules, the actor relationships, and the data flows as they really exist on the ground, not as the official process diagram describes them. A design phase that translates these rules into a coherent data model with explicit roles, validation logic, and audit trails. A capacity transfer phase that brings the institutional users from spreadsheet operators to platform administrators, on a system they can extend and operate independently.
What we did for FAO Burundi
PANEOTECH, with ASER Technologies as implementation partner, ran exactly this transition for FAO Burundi on the Imbuto platform, with co financing from the African Development Bank and government leadership from the Ministry of Environment, Agriculture and Livestock. The diagnostic week mapped the seed sector as it operates in practice, including the partial standalone tools that preceded Imbuto and the provincial spreadsheets that fed national reports. The architecture phase translated the findings into seven explicit user profiles with role based permissions across all eighteen provinces. Two days of in person training in Bujumbura completed the capacity transfer to ministerial and certification authority staff.
The platform is in production. The Ministry has the source code, the documentation, and a six month support engagement that runs alongside continued institutional capacity building. The Excel inheritance is replaced by a digital backbone the institution itself can operate.
The institutional lesson
Public sector digital transformation succeeds when it is treated as a governance transition, not a procurement. The platform matters, but the diagnostic, the design fidelity to actual practice, and the capacity transfer matter more. Skip any of the three and the platform becomes another tool nobody trusts.
We deliver public sector platforms that institutions actually adopt and operate.
From diagnostic and architecture through to deployment, training, and long term support.
