Digital transformation in government and public sector: How to modernise legacy document systems

A citizen submits a planning application, a benefits claim, or a freedom of information request, and somewhere behind the scenes a case worker is searching three different systems to find the paperwork that should already be attached to the record. That gap between what the public expects from digital government and what the underlying document systems can actually deliver is where most digital transformation in government and public sector stalls.

According to the State of Digital Government Review (Cabinet Office and DSIT, January 2025), 28% of central government IT systems are now classified as legacy technology, up from 26% in 2023, and maintaining them costs three to four times more than running modern alternatives. Every year spent patching an old document repository is a year not spent on the services citizens actually notice.

This guide walks through how to modernise legacy document systems in a public sector organisation: what the process actually involves, the checklist to work through before you start, and where the common pitfalls sit. The aim is a document environment that actively supports digital transformation targets.

Key takeaways

• 28% of UK central government IT systems are classified as legacy, and keeping them running costs three to four times more than modern platforms, according to the State of Digital Government Review
• Legacy document modernisation is a phased migration, not a single cutover: it separates metadata, content, and access rules so services keep running throughout
• A structured methodology moves platforms like IBM FileNet or OpenText Documentum with zero downtime, as demonstrated in live financial-sector migrations completed in months
• Compliance has to travel with the migration: UK GDPR, Companies Act retention rules, and records management standards such as ISO 15489-1:2016 all apply to the new system from day one
• Modernised document management is the foundation for the AI and automation ambitions most public sector digital strategies are now built around

What is legacy document system modernisation?

Legacy document system modernisation is the process of moving records and case files off outdated, unsupported document or content management platforms and onto a modern system, without losing the metadata, audit trail, or retention rules attached to that content. In government, this means replacing ageing ECM platforms such as IBM FileNet or OpenText Documentum.

The real cost of clinging to legacy document systems

Legacy platforms rarely fail all at once. They degrade slowly, and that's precisely what makes them dangerous to leave alone. Four costs stack up quietly while the system keeps running.

Specialist skills are disappearing

Administrators for older FileNet and Documentum environments are increasingly hard to find and expensive to retain when you do. Every custom workflow built on top of the platform over the last decade becomes another thing nobody currently on staff fully understands.

The maintenance premium compounds every year

The review cited above puts the cost of legacy technology at three to four times the cost of a modern equivalent, a gap that only widens as vendors wind down support for older releases.

Compliance risk hides in the fragmentation

Freedom of information requests, subject access requests, and audits all depend on being able to locate and produce a document quickly and prove it hasn't been altered. A fragmented legacy estate, where content sits in disconnected repositories with inconsistent retention rules, turns a routine request into a week of manual searching, and turns an audit into a genuine risk.

AI and automation stay out of reach

Intelligent document processing, automated case routing, and AI-assisted search all need clean, structured, well-governed content to work from. Bolting AI onto a legacy system with no consistent metadata is like asking someone to navigate a building with the room numbers half missing. Our broader guide to preparing legacy systems for AI and automation covers the readiness gap in more depth.

How to modernise legacy document systems: step by step

Hey Doxi, how do you modernise legacy document systems?

Your legacy system migration checklist

Before signing off a modernisation project, confirm the plan covers each of these:

• Full inventory of source systems, document types, and volumes, including anything nobody has looked at in years
• A named migration partner or vendor with documented experience on your specific source platform, whether that's FileNet, Documentum, or an older Content Manager environment
• A metadata-first approach that doesn't force an all-at-once bulk content copy
• Zero-downtime delivery, with live services running throughout the migration window
• A verification and proof-of-integrity step built into every stage
• Retention rules and access permissions explicitly mapped and re-applied in the new system
• A decommissioning plan for the legacy platform, agreed in advance

Challenges of modernising government systems, and how to solve them

These four issues come up in nearly every public sector legacy modernisation project, along with the fix that actually works.

Budget approval cycles that don't match project reality

Legacy modernisation competes for funding against more visible, headline-friendly transformation initiatives. A business case built around the ongoing maintenance premium lands better with finance and audit committees than one built around the one-off migration cost.

Nobody fully understands the old system's customisations

Years of bespoke workflow tweaks rarely get documented as they happen. Build a discovery phase into the project timeline specifically to reverse-engineer these customisations before migration starts.

Fear of downtime affecting public-facing services

This is the single biggest source of project delay. A phased, metadata-first migration methodology exists specifically to avoid the all-or-nothing cutover that makes downtime a real risk in the first place.

Compliance requirements getting lost in the technical project

Retention schedules and access controls are easy to treat as an afterthought once the technical migration is underway. Assign compliance sign-off as a formal gate at each migration stage.

Beyond migration: managing the full document lifecycle

Migrating off a legacy platform solves today's problem. What happens to those documents for the next ten years is a separate question, and it's the one most modernisation projects underestimate.

Once content lands in a modern system, it still needs:

• Consistent capture and classification at the point of creation, so it's findable months or years later
• Retention rules applied automatically, with the audit trail written as the work happens
• Fast retrieval when an audit or an FOI request demands a document on short notice
• A single home for document management, records management, and enterprise archiving

A public sector organisation that solves migration but leaves content scattered across separate tools has simply relocated the fragmentation problem. This is where AI-driven automation turns from aspiration into something deployable: structured, well-governed content is what makes intelligent document processing, automated case routing, and AI-assisted search work at scale.

How Doxis supports digital transformation in government

Doxis replaces legacy document and case management platforms including IBM FileNet and OpenText Documentum through the Doxis Consolidation Service, a structured, zero-downtime migration methodology built specifically for organisations that can't afford a disruptive cutover. Metadata and content structure move first, with original content accessible in place, so migrations stay fast and auditable even at large scale.

Migration is only the starting point. Doxis brings document management, records management, workflow automation, and enterprise archiving together on a single Intelligent Content Automation platform, alongside dedicated government solutions built around public sector case handling.

That platform breadth matters for compliance specifically:

• Third-party ISO 16175-2:2020 certification for records management
• Records management capabilities built to conform to ISO 15489-1:2016 and MoReq2010, the specification widely used across European public administration
• Support for UK GDPR-driven data handling requirements

Doxis is also recognised as a Leader in the Gartner Magic Quadrant for Content Platforms.

Key benefits for public sector digital transformation:

• Zero-downtime migration off FileNet, Documentum, and other legacy ECM platforms, with a documented, repeatable methodology
• Records management built to conform to MoReq2010 and ISO 15489-1:2016, with third-party ISO 16175-2:2020 certification
• One unified platform covering document management, records management, workflow, and archiving
• A governed content foundation that makes AI-driven document processing and automation genuinely deployable at scale
• Independently studied ROI within the first year of case management implementation, with Doxis recognised as a Gartner Magic Quadrant Leader

If legacy document systems are the thing standing between your department and its digital transformation targets, get in touch with Doxis for a demo to see how the migration path would work for your specific environment.

FAQs on digital transformation in government