The first question after the directive is how exposed each institution is. The answer depends on who you are. Banks, fintechs and infrastructure providers face different versions of the same deadline. Some will find this easier than others. None will find it easy.
Banks: the migration-scale problem
The largest Nigerian banks are already spending heavily on technology. The top ten banks spent a combined N177.91 billion on IT in the first quarter of 2026, up 30.8% from the same quarter last year. The FUGAZ four (First Bank, UBA, GTCO and Access) accounted for N119 billion of that total, up 43% year on year.
UBA stands out. Its first-quarter IT spend was N22.07 billion, up 257% from a year ago. IT spend does not grow by 257% unless an infrastructure programme is under way. UBA is further along than most.
No Nigerian bank has publicly declared its data localisation migration complete. Galaxy Backbone has been hosting second-quarter webinars to pitch its sovereign cloud and PCI-DSS certified data centres to bank chief information officers. The banks are attending. Nobody is saying the work is done.
That is not surprising. Banks carry the largest data volumes and the longest legacy. A bank that has run core banking systems on offshore infrastructure for a decade cannot flip a switch. The migration requires a data flow inventory, residency classification, target architecture design, cut-over runbooks and rollback plans, then execution, testing and validation.
The banks that started infrastructure planning early (UBA, with the highest IT spend growth, and Zenith, with its Oracle Flexcube migration completed in late 2024) are in a better position. They have the organisational muscle for a large cut-over. But a completed core banking migration does not mean the localisation work is done. It means the team is practised at big infrastructure moves.
For the banks that did not start early, the window is tight. Five months to design and begin executing a migration of this scale is aggressive. It is doable, but the work needs to start this month.
Fintechs: volume and concentration
Fintechs face a harder problem than banks in at least two ways.
First, their transaction volumes are enormous. Moniepoint processes about 1.6 billion transactions per month and moved N400 trillion in 2025. OPay and PalmPay operate at comparable scale. Moving that volume from AWS or Azure infrastructure to onshore colocation without introducing latency regressions is an architecture problem, not a logistics problem. The database cannot simply be copied and the DNS updated. The data paths must be re-architected so the system stays fast after the move.
Second, the circular's market concentration caps add a layer that banks do not face. No single institution may control more than 25% of card issuing or more than 15% of merchant acquiring. Interswitch, Moniepoint and OPay are the most exposed. They need to separate their issuing and acquiring stacks to comply with the caps, on top of moving the data onshore. That is two structural changes running in parallel.
Flutterwave and Paystack are in a different position. They benefit from regulatory clarity: the circular covers payment transaction data specifically, and both companies have been moving toward local infrastructure investment. But they still face the same fundamental question. Where does the data live on 2 January 2027, and is it compliant?
The fintech advantage is architecture flexibility. Most fintechs run cloud-native stacks with shorter infrastructure half-lives than banks, and can re-architect faster. The disadvantage is team size. A fintech with twenty engineers can design a migration, but it cannot run the business, build features and execute a data localisation migration at the same time. Something has to give.
Infrastructure providers: ready but concentrated
Nigeria has about 28 data centre facilities. Roughly 18 are commercial. The combined live capacity is about 50 to 56 megawatts of power. Including expansion projects that are built but not fully equipped, installed capacity rises to about 124 MW. The market is projected to grow to between 210 and 300 MW by 2030. The operators (Galaxy Backbone, Rack Centre, MDXi by Equinix, OADC and Kasi Cloud) are building.
The problem is geography. About 84% of data centre capacity sits in Lagos, mostly in Lekki, Ikeja and Eko Atlantic. Abuja, Kano, Enugu and Port Harcourt have facilities, but they account for a small fraction of the total. A Lagos outage takes out most of the onshore capacity.
Galaxy Backbone's Kano facility is the strongest second-site option. It is Tier IV certified with PCI-DSS, designed for disaster recovery and business continuity. Banks that are serious about resilience will use it.
There is another problem. The data centres provide the physical environment: power, cooling, security and connectivity. They do not provide the cloud platform layer. A bank migrating from AWS is not looking for a colocation rack. It is looking for compute, storage, networking and the management tools that come with a cloud platform. Some operators offer sovereign cloud services on top of their infrastructure, but maturity varies.
Kasi Cloud's chief executive, Johnson Agogbua, said it directly in a recent interview: "Physical data centre capacity is not the problem. The real question is whether we have enough cloud computing and storage platforms that can support this migration at scale."
The talent gap underneath everything
Every bank and fintech in Lagos is hiring for cloud architecture roles. Most have been hiring for months. The candidates are the same small pool of people moving between the same three or four companies.
Nigeria does not have enough experienced cloud migration architects to staff the localisation wave, not in five months and not in twelve. The senior architects are already employed. The freelance market barely exists.
The Big Four firms can provide advisory decks and compliance frameworks. They can state what the circular says and what a compliant architecture looks like on paper. They rarely have the hands-on migration architecture skill that comes from designing IAM permission boundaries across a hundred accounts and running cut-over runbooks at 2 a.m.
The colocation vendors have sales teams who understand their infrastructure. They are not migration architects. They cannot design a hybrid topology or audit data flows.
This is the gap that matters most. The regulation is clear. The data centres exist. The deadline is fixed. What is missing is the layer between the requirement and the working migration. That layer is architecture, and it requires people who have done it before.
Where each player sits
For a bank: the budget and organisational scale exist. The risk is complexity: legacy systems, multiple data sources, a larger compliance surface. Start now.
For a fintech: the architecture flexibility exists, but not the team depth. The risk is bandwidth: running the business while redesigning the data topology. Treat the migration as a distinct workstream with dedicated people.
For an infrastructure provider: the capacity and regulatory tailwind exist. The risk is that customers skip the architecture step and blame the provider when the migration is harder than expected. Offer architecture support, not just rack space.
The talent gap is the one thing nobody can solve with spending alone, in five months. Institutions that have the right architect should lock them in now. They will be booked solid by September.
The position of this Journal
The layer between the requirement and the working migration is exactly what Kaliabe builds. Sovereign data infrastructure is not a rack with a power feed. It is the platform layer: in-country compute and storage, residency enforced by rule, and the migration architecture that moves an institution's record onshore without breaking the service. The institutions that start this month will clear the deadline with room to spare. The ones that wait will discover that the bottleneck is not capacity. It is the architects, and they are already booked.
FIG. J2 — ECOSYSTEM EXPOSURE · BANKS · FINTECHS · INFRASTRUCTURE · THE DEADLINE, BY PLAYER