A practical, assurance-led white paper outlining how to de-risk complex public-sector data migrations and deliver stable, predictable go-lives.
STALIS Data Migration as a Public-Sector Delivery Risk WHITE PAPER A Stalis Perspective on the importance of assurance-led delivery to strengthen UK public sector digital transformation programmes.
PUBLICATION DATE March 2026
PREPARED BY Stalis Bloxham Mill Business Centre Banbury OX15 4FF
www.stalis.com
Content is the property of Stalis and may not be distributed or reproduced without permission.
Executive Summary
Public-sector transformation programmes rarely fail because of platform choice. They fail because data migration risk is underestimated, fragmented, or addressed too late. Across central government, NHS and regulated public-sector environments, large-scale EPR programmes continue to experience late-stage delays, cost overruns and early-life instability. In almost every case, the root cause sits outside the core platform, in legacy data, migration scope, cutover execution and governance. This white paper draws on Stalis’ experience delivering some of the UK public sector’s most complex data migrations, including national-scale ERP and EPR programmes. It explains the importance of fusion transformation programmes as large-scale initiatives, whereby organisations modernise core enterprise systems and operating models, typically moving from fragmented, legacy platforms to integrated, cloud-based “Fusion” environments to combine technology change with process, data, and governance transformation. And, it outlines why data migration represents one of the highest-risk workstreams in transformation, why that risk is often poorly owned, and how assured delivery at the data layer materially improves programme outcomes, commercial confidence and long-term system stability.
STALIS IMPACT
As a trusted partner in healthcare data management, and with over 10 years of deep experience working in Ireland, Stalis is uniquely positioned to help deliver on this vision. We’ve supported public sector digital transformation for over three decades, specializing in data migration, archiving, integration, and quality improvement, to guarantee that the data foundations underpinning clinical systems are complete, accurate, and trusted.
Content is the property of Stalis and may not be distributed or reproduced without permission.
The Hidden Failure Point in Public-Sector Transformation
Most public-sector transformation programmes are designed around platform selection, functional design, integration architecture, and governance and assurance frameworks. These pillars provide confidence to sponsors and oversight bodies because they are visible, contractable, and easy to evidence through important processes including business cases, vendor evaluations, target operating models, and assurance reports. Programme progress is therefore often measured by milestones such as system selection, design sign-off, interface completion, and stage-gate approvals. While these elements are essential, they tend to frame transformation as a sequence of architectural and procedural decisions rather than as a complex, data-led change to live operations. As a result, areas that are harder to standardise, less visible in early phases, or span multiple workstreams (particularly data migration) are often deprioritised or treated as downstream technical activity, despite being critical to service continuity and successful go-live in public-sector environments. Within this structure, data migration is often treated as a subordinate technical workstream rather than as a delivery risk in its own right. This becomes a serious issue because data migration is not a self-contained technical task; it is a cross-cutting delivery dependency that directly determines whether a programme can go live safely, compliantly, and on time.
When migration is treated as a subordinate technical workstream, it is typically:
Under-owned - no single accountable leader spans data, operations and assurance. Under-resourced early - detailed data discovery, quality assessment, and remediation are deferred until late phases.
Decoupled from business reality - assumptions are made about data completeness, structure, and usability that only surface when operational teams attempt to use it.
The consequences are structural. Data underpins every business being transformed, yet the migration decisions are often made after platform design is fixed and contracts are signed. This leaves little room to adapt when data does not conform, and it creates late-stage surprises that directly impact cutover, user acceptance, and service continuity.
Content is the property of Stalis and may not be distributed or reproduced without permission.
And, in the public sector, the risk is amplified. Historical data is frequently subject to statutory retention, audit scrutiny, and freedom-of-information obligations. If migrated data is incomplete, inaccessible, or unreliable, the issue cannot be hidden or deferred. Thus, remediation at this stage is expensive, slow, and highly visible, often requiring programme extensions, parallel system running, or emergency workarounds that erode confidence and increase cost. In practice, migration cuts across every business function, directly affects operational continuity, and is inseparable from cutover planning and go-live success. It also carries significant regulatory, audit, and reputational exposure - particularly in highly scrutinised public-sector environments. When data migration issues surface late in a programme, they are rarely contained: problems become harder to isolate, significantly more expensive to remediate, and immediately visible to operational teams, regulators, and service users, turning what is perceived as a technical detail into a critical threat to programme success.
Why Data Migration Risk Is Amplified in the Public Sector
Data migration risk is materially higher in the public sector because transformation programmes operate within environments shaped by longevity and public accountability. The same conditions do not exist to the same extent in the private sector. These factors fundamentally change the nature of migration from a technical activity into a systemic delivery risk. Scale and longevity are the first amplifiers. Public-sector organisations often hold decades of historical data created across multiple generations of systems and data models. This data has accumulated through repeated policy changes, restructures, and regulatory shifts, meaning that records were created under different rules and assumptions. Legacy platforms are frequently heavily customised and poorly documented, making data extraction far more complex than anticipated. The older and more fragmented the estate, the higher the likelihood of hidden data quality issues that only surface during late-stage migration or cutover. Organisational complexity further compounds the risk. Public services most likely span multiple departments and arms-length bodies (ALBs) operating within federated or shared-service models. Data ownership is often diffuse, with no single authority accountable for the quality or structure across the estate. Standards (such as employment terms and conditions) vary by organisation, creating inconsistencies that cannot be resolved through technical mapping alone. Migration therefore becomes as much an organisational alignment challenge as a technical one, requiring decisions about ownership, authority, and accountability that programmes are often not structured to make.
Content is the property of Stalis and may not be distributed or reproduced without permission.
Regulatory and audit pressure introduces a non-negotiable constraint. Public-sector data is subject to statutory retention requirements, Freedom of Information obligations, and workforce continuity considerations. Data cannot simply be discarded or “cleaned up later” without breaching legal or regulatory obligations. Migrated data must be complete, traceable, and defensible under audit. Any loss of records carries immediate legal and operational consequences, significantly raising the stakes of migration failure. Finally, political and reputational exposure magnifies the impact of any issues that do arise. Public- sector transformation programmes are high-visibility by nature, with low tolerance for service disruption or degradation. When data migration problems surface, they rarely remain internal to delivery teams. Delays, workarounds, or service impacts quickly attract scrutiny from regulators, oversight bodies, the media, and the public. Confidence erodes rapidly, and recovery becomes as much a reputational exercise as a technical one. Taken together, these factors mean that data migration failures in the public sector are rarely isolated, recoverable events. They cascade across every area of delivery, turning what might be manageable risk elsewhere into a critical threat to programme viability.
Content is the property of Stalis and may not be distributed or reproduced without permission.
Content is the property of Stalis and may not be distributed or reproduced without permission.
Oracle EBS to Fusion Cloud: A High-Risk Transition Path
The migration from Oracle E ‑ Business Suite (EBS) to Oracle Fusion Cloud is the process of moving an organisation’s core enterprise systems, such as finance, procurement, HR, and supply chain, from a legacy Oracle platform to Oracle’s modern, cloud-based suite. It is significant because it is not a simple upgrade, but a fundamental change in how an organisation operates, governs data, and delivers services. From a technology perspective, the move replaces locally hosted systems that are often heavily customised, with a standardised, modern, and continuously updated cloud platform. Oracle Fusion introduces new frameworks that require organisations to redesign business processes rather than replicate legacy ways of working. For many public-sector organisations, this means rationalising decades of bespoke configurations and aligning to common standards for finance, HR, and procurement. This is often expressed using the mantra, “adopt, not adapt”.
Content is the property of Stalis and may not be distributed or reproduced without permission.
Strategically, the move to Oracle Fusion Cloud is often positioned as a foundation for wider transformation: shared services, improved financial control, better analytics, and integration with other national platforms. Done well, it reduces long-term cost, technical debt, and security risk. Done poorly, it becomes a high-profile source of delay and disruption. That is why the EBS-to- Fusion migration is widely regarded as one of the most significant and high-risk transitions in modern public-sector transformation programmes. Therefore, it is unsurprising that the migration from Oracle E-Business Suite to Oracle Fusion Cloud has become one of the most common transformation routes across UK public-sector programmes, driven by the need to modernise legacy estates and reduce long-term operational risk. While the target platform offers clear benefits including standardisation, improved controls, and cloud scalability, the transition itself introduces a distinct and often underestimated risk profile. At the core is structural change. Oracle Fusion is not a like-for-like upgrade of EBS; it introduces fundamentally different data models, configuration logic, and process assumptions. Chart of accounts structures, supplier (and occasionally customer) models, asset data, HR records, payroll data, and historical transactions often require transformation rather than direct migration. This complexity is amplified by the sheer volume of historical transactional data retained by public- sector organisations, much of which is subject to statutory retention, audit, and FOI obligations and cannot simply be archived or excluded. Data quality is a further pressure point. Many public-sector EBS environments have evolved over decades, with multiple customisations and inconsistent local practices. Data that was “good enough” for legacy operations may not meet Fusion’s stricter validation and control requirements. These issues frequently surface late, because functional sign-off in Fusion is heavily dependent on migrated data behaving correctly within end-to-end business processes, not just passing technical load checks. Added to the complexity there are often data issues reflected in non- reconciling accounts and missing data in related tables.
Content is the property of Stalis and may not be distributed or reproduced without permission.
Critically, migration in an EBS to Fusion programme is tightly coupled to testing and cutover. Incomplete or inaccurate data undermines system integration testing, user acceptance testing, and parallel runs, compressing already tight timelines. When programmes underestimate this dependency, the consequences are predictable: late-stage test failures, extended or repeated cutover windows, instability in early live operation, and a growing reliance on manual workarounds to keep core services running. In the public sector, where financial controls, payroll accuracy, supplier payments, and audit defensibility are non-negotiable, these impacts are not merely inconvenient—they directly threaten service continuity and organisational credibility. Treating Oracle EBS to Fusion migration as a standard technical conversion, rather than as a primary delivery risk, is therefore one of the most common (and costly!) failure modes in large-scale public-sector transformation programmes. Stalis has provided specialist end-to-end data migration services for 40 years, underpinned by a proprietary toolkit, Stalis Advance. This toolkit offers automated and reliable extract, transform, load capabilities, complemented by powerful data quality reporting and reconciliation, that removes chance, inconsistencies, and human error from this complex process. Repeatable, traceable, and auditable, our toolkit assures data confidence and success, providing a trusted blueprint for any data migration project, no matter how large or complex.
Content is the property of Stalis and may not be distributed or reproduced without permission.
The Ownership Gap: Where Programmes Break Down
A recurring failure point in large-scale transformation programmes is the ownership gap around data migration risk. Responsibility is often fragmented across multiple suppliers, with unclear accountability between the systems integrator, the platform vendor, and the client organisation itself. As we’ve touched on previously, migration is frequently treated as a tooling or configuration problem, creating a false sense of security that technology alone will resolve delivery complexity. As a result, migration planning becomes disconnected from the operational realities of cutover and go-live. When issues inevitably surface, this fragmentation slows decision-making, drives escalation between suppliers, and erodes senior confidence, placing great acute pressure on the programme at precisely the moment when clarity, authority, and control are most critical. Stalis Advance efficiently and effectively manages and automates every aspect of end-to-end data migration requirements. The long list of activities, scripts and tasks that need to be run in the correct order is tightly controlled, from running extract routines against the legacy system, through applying mapping and transformation rules, to producing load files and validation/data cleansing reports. The solution can be applied to any source and target system with repeatability, quality and consistency guaranteed by tried and tested scripts and code. It can be used for complete, end-to-end data migration delivery, with the flexibility to also run individual elements of the process in isolation, e.g. to produce a specific load file or re-run validation following the revision of lookup values.
Content is the property of Stalis and may not be distributed or reproduced without permission.
What AssuredDM Looks Like in Practice
AssuredDMDmigration is not defined by speed of execution or the selection of migration tools alone. It is a delivery discipline grounded in clear risk ownership, end-to-end visibility, and operational control. Programmes that achieve stable outcomes treat migration as a primary determinant of go-live success, rather than as a downstream technical activity. This shift in approach is characterised by five core principles. 1 Explicit risk ownership is foundational - AssuredDM programmes appoint a single, accountable owner responsible for migration outcomes across data quality, completeness, clinical or operational safety, and readiness for cutover. This role is distinct from platform delivery and integration responsibilities, with clear boundaries that prevent gaps, overlaps, or deflection of accountability between suppliers and client teams. Ownership is defined in delivery terms and not contractual abstractions.
Early and realistic scoping is equally critical - AssuredDM migration begins with a comprehensive understanding of the legacy landscape, including system variants, historical depth, data quality issues, and regulatory constraints. Clear, early decisions are made on what data must be migrated into the target platform, what should be archived in a compliant and accessible form, and what can remain available through alternative mechanisms. This prevents late-stage discovery and avoids forcing complex trade-offs under time pressure.
2
Governance built for delivery distinguishes AssuredDM programmes - from those that rely solely on architectural or assurance frameworks. Migration is treated as a first-class workstream with senior visibility, formal decision points, and measurable readiness criteria. Programme leadership has clear line-of-sight into migration risk, dependencies, and cutover readiness, enabling informed decisions rather than reactive escalation. 3 4 Cutover-aligned execution ensures that migration design is driven by operational reality rather than technical milestones. Data loads, validation, and testing cycles are structured around how the organisation will actually operate at go-live - covering real user journeys, business-critical processes, and regulatory scenarios. This alignment reduces late surprises and ensures that migrated data is not only present, but usable, trusted, and safe from day one. Early and realistic scoping is equally critical - AssuredDM migration begins with a comprehensive understanding of the legacy landscape, including system variants, historical depth, data quality issues, and regulatory constraints. Clear, early decisions are made on what data must be migrated into the target platform, what should be archived in a compliant and accessible form, and what can remain available through alternative mechanisms. This prevents late-stage discovery and avoids forcing complex trade-offs under time pressure. 5
Content is the property of Stalis and may not be distributed or reproduced without permission.
Why Data Migration Is a Commercial Issue, Not Just a Technical One In large-scale public-sector transformation programmes, data migration performance has a direct and material impact on commercial outcomes. For system integrators and delivery partners, the quality and credibility of migration execution influences procurement confidence, shapes late- stage deal velocity, and directly affects pricing pressure as buyers seek to offset perceived delivery risk. Where migration approaches are vague, under-owned, or deferred, programmes attract increased scrutiny, extended clarification cycles, and demands for commercial concessions to compensate for uncertainty. Migration outcomes also determine referenceability. In regulated environments, early-life stability and audit defensibility are often the criteria by which programmes are judged externally. Migration-led incidents, manual workarounds, or post-go-live instability quickly erode confidence, limiting the willingness of clients to act as references or to endorse suppliers for subsequent phases. This, in turn, constrains account expansion opportunities following go-live, as organisations become focused on risk containment rather than optimisation or additional transformation. Public-sector buyers are increasingly risk-led rather than feature-led. Decision-makers assess not only the target platform, but the supplier’s ability to take ownership of the most complex and exposed elements of delivery. Clear, demonstrable ownership of data migration risk—supported by governance, accountability, and proven execution—has therefore become a decisive factor in programme confidence, supplier selection, and long-term commercial success.
Lessons from Large-Scale Public-Sector Delivery
Across national and multi-organisation transformation programmes, several consistent lessons emerge. The majority of functional issues encountered during testing and early live operation originate in data quality, completeness, or structure, rather than in platform configuration itself. Programmes that invest early in migration assurance—through realistic scoping, validation, and governance—consistently avoid higher downstream costs associated with remediation, programme extensions, and operational workarounds. Clear ownership of migration outcomes reduces ambiguity and prevents the late-stage escalation cycles that erode confidence and consume senior attention. Above all, stable data is a prerequisite for stable operations: systems can only perform as reliably as the information they are built upon.
Content is the property of Stalis and may not be distributed or reproduced without permission.
The largest Oracle myHR implementation to date for one of the largest global logistics companies where 60,000 HR and payroll records were migrated with a 100% success rate at final cutover, achieving outcomes described by the client as “outstanding.” In the UK public sector. The successful migration of more than 2 million records and transactions for one of the UK’s largest County Council’s as it transitioned to Oracle Fusion Cloud ERP, delivering the programme on time and within budget. Supporting a major Metropolitan Borough Council through the successful migration of a feature-rich legacy system landscape holding records for over 9,000 staff into Oracle Fusion.
Content is the property of Stalis and may not be distributed or reproduced without permission.
The Role of Specialist Migration Partners
Given the scale, scrutiny, and operational criticality of modern public-sector transformation programmes, data migration capability has become a scarce and specialist discipline. Generalist delivery teams, often optimised for platform configuration and integration, frequently lack deep experience of Oracle E-Business Suite to Oracle Fusion Cloud transitions, exposure to national- scale and long-lived datasets, and the practical realities of operating under NHS and wider government assurance regimes. These gaps matter: migration risk is cumulative, highly exposed at cutover, and unforgiving of late discovery. Specialist partners like Stalis address this by bringing focused expertise, proven methods, and dedicated ownership of migration outcomes, which in turn reduces delivery risk, eases pressure on core SI teams, and materially increases confidence at senior leadership, assurance, and governance levels.
Conclusion: Treat Data Migration as the Critical Path
Public-sector transformation succeeds when delivery risk is addressed where it most often materialises. Data migration is not a peripheral activity; it is the foundation on which operational continuity, organisational confidence, and programme credibility are built. Organisations that treat migration as a core delivery risk - clearly owned, actively governed, and rigorously assured - consistently achieve cleaner go-lives, stronger delivery outcomes, and more sustainable transformation programmes that can move quickly from implementation into stable business-as- usual operation and long-term optimisation. All organisations - whether customers or implementers - should put data migration at the top of their agendas, and prepare for it as early as possible.
About Stalis
Stalis is a long-standing data migration and integration specialist, with 40 years experience and an unrivalled reputation proven in 600+ complex technology and system change programmes. We have the tools, experience, track record, people, and passion to ensure your data is robust and ready to achieve your organisation’s digital data aspirations.
Content is the property of Stalis and may not be distributed or reproduced without permission.
www.stalis.com Bloxham Mill Business Centre, Banbury OX15 4FF 01608 810015 enquiries@stalis.com
Content is the property of Stalis and may not be distributed or reproduced without permission.
Page 1 Page 2 Page 3 Page 4 Page 5 Page 6 Page 7 Page 8 Page 9 Page 10 Page 11 Page 12 Page 13 Page 14Made with FlippingBook - Share PDF online