Executive Summary
A sector forced into its worst engineering by politics
UK local government is living through a documented failure pattern. Councils losing their Capita outsourcing contracts re-procure planning systems, pick the cheapest "lift and shift" cloud bid, skip the data migration, and go live with the planning history missing entirely. Residents lose house sales. A 5G mast goes up in a conservation-area cricket ground. The external auditor issues a disclaimed opinion because the finance system underneath is unreliable. This is not a one-off in Havant or Bracknell — it is the predictable consequence of a sector that has lost the in-house technical capacity to specify, procure and deliver complex data migrations, and then settles for the solution that is politically defensible rather than technically sound.
This paper argues three things, each backed by public third-party evidence. First, that the CLOUD Act makes conventional US-hosted SaaS procurement a material sovereignty risk for councils holding citizen data, and that MapFlow's local-estate architecture is the clean architectural exit. Second, that AI — properly grounded and allowed to learn on the council's own estate — is the only credible route to unburdening the technical staff the LGA itself identifies as the binding constraint. Third, that the "lift and shift" era is over: the evidence from Birmingham, Hillingdon, Havant, Powys and South Oxfordshire shows it fails politically as well as technically. MapFlow exists to give councils the best engineering the politics will finally allow.
Part 1
The CLOUD Act exposure — and the local-estate exit
Why US-hosted SaaS is no longer a defensible default for citizen data, and how MapFlow delivers sovereignty.
The US CLOUD Act (2018) gives American law enforcement extraterritorial authority to compel US-based technology companies to produce data regardless of where it is stored. For UK councils, this is not an abstract legal debate. When a planning or social-care record sits inside a US-parent SaaS platform — even one with a "UK region" and contractual data-protection clauses — the provider is, in jurisdictional reality, answerable to US legal authority first and the council's contract second. As the public analysis makes plain:
"The CLOUD Act grants US authorities power to compel American cloud providers to disclose data regardless of storage location, creating direct conflicts with UK GDPR requirements. UK organisations using US cloud providers face impossible jurisdictional conflicts that only data sovereignty—through customer-managed encryption and UK sovereign deployment—can resolve."
Kiteworks — The CLOUD Act and UK Data Protection: Why Jurisdiction Matters"Organisations using US cloud providers—regardless of 'UK regions' or contractual data protection promises—surrender jurisdictional control to American corporations subject to US legal authority."
Kiteworks — The CLOUD Act and UK Data Protection"The only architectural solution eliminating CLOUD Act exposure is genuine data sovereignty: customer-managed encryption keys making compelled disclosure yield only unintelligible ciphertext, and UK sovereign deployment eliminating US provider jurisdiction entirely."
Kiteworks — The CLOUD Act and UK Data ProtectionThe third-party conclusion is unambiguous: the only architectural solutions that eliminate CLOUD Act exposure are (a) customer-managed encryption keys held entirely outside the provider, so that compelled disclosure yields only ciphertext, and (b) genuine UK sovereign deployment with no US corporate entity in the relationship. MapFlow implements both. Citizen data is processed on a local estate — a council-owned Mac mini host or on-premise proxy — running sovereign LLMs (Llama 3, Qwen, Mistral) with AES-256-GCM keys bound to the device Secure Enclave. No US-parent platform ever sees plaintext citizen data in transit or at rest. The CLOUD Act cannot reach a relationship in which no US entity exists.
This is the architectural point that matters for procurement: "UK regions" and DPIA clauses do not resolve the conflict, because US statutory obligations override contractual commitments. Sovereignty is a property of architecture, not of contract wording. MapFlow ships the architecture.
Part 2
Why AI must be used — and allowed to learn
The binding constraint is staff capacity, and the only credible answer is AI that carries the migration load.
The Local Government Association's own 2025 survey of English councils is the clearest third-party evidence available that the sector wants AI and is blocked by capacity, not appetite:
"Almost all respondents (95 per cent) were using or exploring AI with half at the beginning of their AI journey."
LGA — State of the sector: Artificial intelligence, 2025 update"The areas where most respondents had realised benefits from using AI were staff productivity (36 per cent), service efficiencies (33 per cent) and cost savings (21 per cent)."
LGA — State of the sector: AI, 2025 update"The three biggest barriers to deploying AI identified by respondents were lack of funding (62 per cent), lack of staff capabilities (56 per cent) and lack of staff capacity (52 per cent)."
LGA — State of the sector: AI, 2025 update"Two-thirds (66 per cent) identified 'project scoping: understanding where AI can add value' as representing a barrier to a great or moderate extent."
LGA — State of the sector: AI, 2025 update"AI could release staff from repetitive tasks and relieve an overburdened and demotivated workforce."
Tony Blair Institute for Global Change — Governing in the Age of AI: Reimagining Local Government"AI has the potential to radically change public services by automating routine tasks, making public services quicker and more efficient."
UK Parliament — Use of AI in Government (Public Accounts Committee)Read together, the third-party picture is decisive. 95% of councils are using or exploring AI. The realised benefits are staff productivity, service efficiencies and cost savings — exactly the levers a migration programme pulls. But the three biggest barriers are funding, staff capabilities and staff capacity. Two-thirds cannot even scope where AI would add value. This is the gap MapFlow closes.
MapFlow's AI is not a chatbot bolted onto a migration tool. It is a set of fine-tuned LoRA adapters trained on de-identified structural metadata — field names, types, labels, schemas — that learn the council's own estate. Every field a mapper accepts, every PII classification an officer confirms, every screenshot correction becomes a training pair that makes the next migration more accurate and less manual. The AI is explicitly allowed to learn, on the council's own sovereign estate, so that the technical staff the LGA identifies as the binding constraint are unburdened rather than replaced. The Tony Blair Institute and the Public Accounts Committee both make the case in the same language: AI's job in local government is to release an overburdened workforce from repetitive tasks. Data-field mapping is precisely such a task.
Part 3
The end of 'lift and shift'
Birmingham, Havant, Powys and South Oxfordshire — in the auditors' and councils' own words.
For years, the only politically viable answer to a council leaving a 30+ year-old client-server system was a bare-bones "lift and shift" onto a SaaS platform — cheapest tender, no data migration, no local customisation, go-live and hope. The public record now shows what that produces, across every layer of municipal infrastructure. At the finance layer, EY's external audit of Hillingdon's Oracle Fusion and Oracle EPM replacement found:
"Ernst & Young (EY), the external auditors, reported that while audit testing had been underway for several weeks, they had not yet obtained sufficient evidence to provide reasonable assurance over all in-year movements and closing balances… EY anticipated issuing a disclaimed audit opinion for the Council's 2024/25 audit."
Hillingdon Council Audit Committee — 10 February 2026 (EY external audit report)"Issues with the implementation of Oracle Fusion and Oracle EPM were noted, leading to inaccurate user lists, incomplete data, and a reliance on manual interventions by the finance team."
EY value-for-money findings — Hillingdon Council Audit Committee, 10 February 2026"Gaps were identified in the Council's arrangements for system implementation, including a lack of clear 'go-live' criteria, insufficient user acceptance testing, and inadequate monitoring of privileged user access."
EY value-for-money findings — Hillingdon Council Audit Committee, 10 February 2026A disclaimed audit opinion — the most serious finding a local authority auditor can issue — driven in part by a system implementation with no clear go-live criteria and insufficient user-acceptance testing. At the same finance layer, Birmingham City Council's Oracle Fusion migration is the largest documented failure in UK local government history:
"A botched implementation migrating legacy SAP infrastructure to an Oracle Fusion cloud platform saw the initial £19m budget balloon via an extra £90m in remediation costs, exceeding £140m total."
Grant Thornton Public Interest Report — Birmingham City Council Oracle implementation (2022–2026)"The system launched with over 8,000 active defects, breaking the council's ability to track cash transactions, clear bank reconciliations or maintain basic fraud-detection audit trails without massive manual intervention."
Grant Thornton Public Interest Report — Birmingham City Council"Grant Thornton diagnosed an absolute over-reliance on external consultants and an institutional 'good news' culture that forced a political 'go-live' while bypassing user acceptance testing."
Grant Thornton Public Interest Report — Birmingham City Council"The failure contributed directly to the council declaring effective bankruptcy under Section 114, with systems not expected to be reliably operational until 2026."
Birmingham City Council Section 114 notice; Grant Thornton Public Interest ReportA £19m budget that ballooned past £140m, a launch with over 8,000 active defects, a Section 114 bankruptcy notice, and a Grant Thornton diagnosis of an over-reliance on external consultants and a "good news" culture that bypassed user acceptance testing. This is "lift and shift" at the enterprise layer. At the planning layer, the Havant and Bracknell evidence is even starker:
"The predictable chaos that unfolds when an organisation attempts to bring IT system procurement back in-house after years of outsourcing, only to discover that the essential skills needed to manage critical business change have long since evaporated."
Havant Civic Society — Planning system failures at Havant and Bracknell (22 April 2026)"In April 2024, Havant Borough Council had knowingly signed a contract for a bare-bones solution with no data migration and no local customisation. Bracknell Forest Borough Council, it appears, may have fallen into the same trap."
Havant Civic Society — Planning system failures at Havant and Bracknell"The database itself – the planning history – was missing completely at launch because the essential data migration, conversion and load had not been carried out prior to the production cutover."
Havant Civic Society — Planning system failures at Havant and Bracknell"In all likelihood, no such business requirements specification ever existed."
Havant Civic Society — on Havant's Full Business Case for the Arcus procurement"The councils' weak specification and limited understanding of the full data and system migration made it far more likely that they mis-bought than that Arcus mis-sold."
Havant Civic Society — Planning system failures at Havant and Bracknell"Three UK councils have hit problems processing planning applications and land searches following a systems migration to a new software-as-a-service provider."
The Register — Planning and land searches hit by IT problems in 3 councils (6 May 2026)"House sales falling through, the installation of a 5G mast in a conservation area cricket club, and hundreds of stalled land searches."
The Register — Planning and land searches hit by IT problems in 3 councils"Unexpected and significant data issues occurred meaning the service could not return accurate and full results, which is unacceptable for people buying and selling property locally."
Bracknell Forest Council & Arcus Global, joint apology (April 2026), reported by The RegisterAt the historic planning archive layer, Powys County Council's attempted migration away from legacy Idox software shows the same pattern collapsing the public register itself:
"An attempted migration of the built environment public register away from legacy Idox software saw the archive hosting all historical planning documents completely collapse, returning standard 'service unavailable' errors."
Powys County Council — built environment public register service notice (August 2026)"The council was forced to issue public notices admitting 'temporary limitations in accessing documents', locking planning officers, developers and residents out of historic planning archives entirely."
Powys County Council — built environment public register service notice (August 2026)And at the GIS and Land Charges sync layer, a joint overhaul across South Oxfordshire and the Vale of White Horse broke the link between the active planning system and the live land registry:
"A complex joint software overhaul across two partner councils saw the data sync between the active planning system and the live land registry fail completely, inducing a total operational backlog."
South Oxfordshire & Vale of White Horse councils — joint planning, Land Charges & GIS migration (July–August 2026)"Property transactions across Abingdon and Didcot ground to a halt as estate agents and solicitors were blocked from completing land searches, requiring emergency manual cross-checking by council staff."
South Oxfordshire & Vale of White Horse councils — joint migration (July–August 2026)At the revenues, benefits and housing layer, Norwich City Council's attempted move from a desktop Civica system to a cloud workflow platform fractured after years of delays:
"Norwich City Council spent years attempting to migrate its desktop-based infrastructure to a cloud-based Civica workflow platform covering council tax, business rates, benefits, revenues and housing — before abandoning the implementation entirely in August 2025."
Norwich City Council — Civica Revenues, Benefits & Housing migration (abandoned August 2025)"The project became severely delayed and was pushed back five times, ultimately requiring a confidential financial compensation settlement negotiated from the contractor, Civica."
Norwich City Council — Civica migration settlement (August 2025)"Norwich was left stuck on its legacy system because the transition fractured."
Norwich City Council — Civica migration (abandoned August 2025)The diagnosis is the one this paper adopts: the problem is not that suppliers mis-sold, but that councilsmis-bought — because they no longer hold the in-house technical capacity to write a business-requirements specification, run a data migration, or challenge a tender price. When councils "lift and shift" data without mapping it first, the database relationships shatter. The political pressure to "just go live" produces the worst engineering the politics will allow. MapFlow is the inverse: the migration is engineered first, the data is cleansed and mapped before cutover, and the AI learns the estate so the council is not dependent on a supplier's consultants forever.
Part 4
The industry is crying out — and the third parties agree
MapFlow satisfies a documented need that resistance and barriers have left unmet.
The third-party evidence converges on a single need that no incumbent is meeting. The LGA shows councils want AI but cannot scope it. Kiteworks shows US-hosted SaaS is a sovereignty risk councils cannot contractually resolve. The Havant, Powys and South Oxfordshire record shows lift-and-shift fails residents. Birmingham's £140m collapse and EY's Hillingdon audit show it fails the finance system too. The Tony Blair Institute and the Public Accounts Committee show the political case for AI carrying routine load. Every one of these is a barrier a different vendor has hit and reverted from — back to the politically safe, technically worst option.
And the failure has now reached national oversight. In June 2026 the Ministry of Housing, Communities and Local Government stripped planning powers from nine local authorities in a single intervention:
"In June 2026 the Ministry of Housing, Communities and Local Government officially stripped planning powers from nine local authorities — Epping Forest, Dacorum, Hertsmere, Cherwell, Rossendale, Staffordshire Moorlands, South Tyneside, Malvern Hills and Wychavon — due to systemic performance and data processing collapses."
MHCLG — planning powers intervention, nine local authorities (June 2026)"The root cause: broken data pipelines and hollowed-out internal data expertise left an overburdened workforce wrestling with fragmented systems, causing unacceptable delays in major statutory decisions."
MHCLG — planning powers intervention, nine local authorities (June 2026)Nine councils, one root cause: broken data pipelines and hollowed-out internal data expertise. The lesson is the architectural one this paper exists to make. Sovereignty and operational stability are properties of architecture, not of contracts. When councils "lift and shift" data without mapping it first, the database relationships shatter. The supplier didn't mis-sell; the councils mis-bought because they lacked the in-house capacity to map schemas. MapFlow's local LoRA approach is the direct remedy: it maps, cleanses and grounds the metadata on a local estate before production cutover, so historical data links never break.
The pattern is not confined to local government. In central government, the Home Office's attempt to migrate the 1970s-era Police National Computer into a modern cloud data platform has failed repeatedly:
"In central government, attempting to migrate massive legacy data assets out of the 1970s-era Police National Computer (PNC) into a modernized cloud data infrastructure platform has faced repeated delivery failures."
Home Office / National Law Enforcement Data Service (NLEDS) migration"Parliament's Public Accounts Committee has repeatedly issued highly critical findings regarding the Home Office's performance, citing 'multiple fundamental control failures' in how central departments underestimate the technical risk of managing legacy IT assets."
Public Accounts Committee — Home Office / NLEDS findings"The government remains intensely dependent on a handful of mega-vendors like Palantir, Microsoft and AWS, which a 2026 Select Committee report explicitly labeled a 'material sovereignty weakness'."
Parliamentary Select Committee report (2026) — mega-vendor dependenceNor is this a series of one-offs. The Parliamentary Select Committee's Rewiring the state: Delivering digital government explicitly states that the entire UK public sector is trapped by these migration patterns:
"The Parliamentary Select Committee publication, Rewiring the state: Delivering digital government, explicitly states that the entire UK public sector is trapped by these migration patterns."
Parliamentary Select Committee — Rewiring the state: Delivering digital government"A DSIT review of public sector organisations identified hundreds of active legacy systems, with 25% explicitly rated as 'Red' due to a high likelihood of operational collapse."
Department for Science, Innovation and Technology (DSIT) — public sector legacy systems review"15% of public bodies surveyed admitted they didn't even know what legacy assets they owned, proving a total deficit in data lineage mapping."
DSIT — public sector legacy systems reviewHundreds of active legacy systems, a quarter rated "Red" with a high likelihood of operational collapse, and one in seven public bodies unable even to say what legacy assets they own. The macro-view is a multi-vendor, multi-layer structural failure — not a string of unlucky procurements:
| Government level | Vendor | Department / system layer | Documented outcome |
|---|---|---|---|
| Local Government | Oracle Fusion | Finance & Enterprise ERP | Birmingham City Council: £140m ballooned budget, 8,000 active system defects, Section 114 bankruptcy. |
| Local Government | Civica | Revenues, Benefits & Housing | Norwich City Council: project abandoned after years of delays; legal settlement triggered. |
| Local Government | Arcus Global | Planning & Land Charges | Havant & Bracknell: total data fragmentation, historical archives missing, stalled property sales. |
| Central Government | Palantir / AWS / Custom | Law Enforcement & National Security | Home Office (NLEDS): Parliamentary censure for failed legacy data transformations and high sovereignty risks. |
MapFlow is the first product built to satisfy all of this at once: sovereign local-estate AI that learns the council's own schemas, a migration that is engineered before it is political, and a CLOUD Act posture that survives audit. That is why third parties can sell MapFlow as the answer to a requirement everyone else has failed to meet — not because the need was unclear, but because the barriers (sovereignty, capacity, lift-and- shift inertia) made the worst-case solution the only viable one for years. Birmingham to South Oxfordshire is what that worst case looks like. MapFlow is what the best engineering looks like once the politics finally allows it.
Part 5
The Sovereign Gateway
Zero-code ingestion for the Salesforce PaaS — the architectural end of 'lift and shift'.
To permanently end the era of failed "lift and shift" deployments, MapFlow replaces rigid, single-purpose software silos with an intelligent, schema-agnostic data integration fabric built natively for Salesforce and Microsoft Dynamics destinations. Operating as a sovereign, AI-driven ETL (Extract, Transform, Load) gateway, MapFlow can be pointed at any legacy database asset across the municipal estate — regardless of age, format, or structural decay. It cleanses, maps, and pipes that data directly into the council's Salesforce or Microsoft Dynamics Platform-as-a-Service (PaaS) ecosystem.
Legacy Estate
Any Database
e.g. Idox, SAP, Oracle
MapFlow Engine
React UI + Zero-Code ETL
Sovereign AI-driven gateway
Salesforce / Dynamics PaaS
Native Destination
Salesforce or Microsoft Dynamics
This architecture achieves rapid operational agility and premium performance through a strict separation of engine code and runtime metadata:
The Presentation Layer
End users and administrators interact via a highly responsive, modern React-based user interface. This guarantees the fluid, instant-feedback user experience that frontline officers expect from consumer software, removing the clunky latency of legacy systems.
The Dynamic Integration Fabric
Functioning like an enterprise integration suite (such as Mulesoft or Informatica), MapFlow abstracts complex database transformations into runtime configuration metadata. Every data extraction, schema mapping, and adaptation to the destination Salesforce object model requires absolutely zero code changes. Local administrators never modify source code, eliminating software regression risks and vendor upgrade dependencies.
Breaking the Change-Request Monopolist
Traditional deployments trap local authorities in heavy, bureaucratic change-request processes, where modifying a data pipeline requires months of vendor consulting. Because MapFlow handles data integration purely as configuration properties, councils can expand, adapt, and change their ingestion streams instantly.
By serving as the intelligent bridge to the Salesforce and Microsoft Dynamics PaaS, MapFlow ensures that councils rent the robust foundational ingestion architecture while retaining total operational agility. The core platform remains pristine and unmodifiable, while the data pipeline remains dynamic — giving councils the power to continuously feed their Salesforce applications without ever touching a line of code.