SAP ECC6 decommissioning in local government

Many local authorities across the UK are mid-way through, or have recently completed, major ERP migrations, swapping out legacy SAP ECC6 systems for modern platforms. But going live on a new system is only half the battle. What happens to the years of historical data left behind in the old one?

For one county council, this was a very real challenge. Having moved from SAP ECC6 to Oracle ERP as part of a broader IT modernisation programme, the council was left with 16 years of historical financial and HR data sitting in a system it no longer needed to run. Switching it off without a plan wasn’t an option. Keeping it running indefinitely wasn’t either.

The real cost of keeping legacy systems alive

It’s easy to underestimate the ongoing burden of a decommissioned-in-all-but-name system. Even in read-only mode, a legacy SAP ECC6 environment demands real resources:

• Infrastructure costs across production and test environments, including ageing hardware that becomes increasingly expensive to maintain and support
• Software licensing and support fees for a platform that’s no longer being actively used
• Staff time diverted from strategic work to keep an outdated system ticking over
• Compliance and security risk from running unsupported software, with potential exposure under GDPR and internal audit requirements
• Environmental impact, as older hardware is typically far less energy-efficient than modern alternatives

For local authorities facing ongoing budget pressure, these costs are hard to justify. Decommissioning properly, rather than simply leaving a system dormant, is almost always the more practical and cost-effective path.

Cloud-first decommissioning for local government

The county council’s approach was shaped by two requirements that will be familiar to many public sector IT teams: alignment with the UK government’s cloud-first policy, and compliance with their own internal ICT architecture standards.

This ruled out on-premise archiving options and pointed clearly towards a cloud-based solution. The council worked with Proceed Group to deploy Proceed Cella Cloud, an all-in-one decommissioning platform designed specifically for this purpose.

The project involved extracting and migrating approximately 2TB of historical SAP ECC6 data, including financial records and HR data, into Proceed Cella Cloud. The data was reconciled for accuracy and completeness before migration, and user acceptance testing was completed before go-live.

The full project followed a structured six-stage approach:

1. Scope and planning during the blueprint phase
2. Data extraction from the legacy SAP ECC6 system
3. Reconciliation to validate accuracy and completeness
4. Migration to Proceed Cella Cloud
5. User acceptance testing
6. Ongoing support for reporting needs

What the council ended up with

Within three months, the legacy ECC6 system was fully decommissioned. The council now has:

• Secure, searchable historical data hosted in the cloud
• Five pre-configured standard reports covering the most common data access requirements
• Retention rules in place to ensure data is deleted compliantly as retention periods expire
• Access to Proceed’s team for any additional reporting requirements that arise over time

Critically, the council’s team is now free to focus on getting the most from their new Oracle ERP system, rather than keeping one eye on a system they’ve already moved on from.

Why decommissioning matters beyond cost savings

The financial case for decommissioning is well established. Organisations that go through a structured decommissioning project typically reduce their total cost of ownership for legacy systems by up to 80%. But for local government in particular, there are broader considerations.

Retained data that sits in an unmaintained system is a liability, not just a cost. GDPR obligations don’t disappear because a system is old; if anything, the risk increases when personal data is held in environments that can no longer be properly secured or audited. Retention management, the ability to define how long different categories of data must be kept and to enforce deletion at the right time, is increasingly important for councils navigating both their statutory obligations and the Information Commissioner’s expectations.

A properly decommissioned system, with structured retention rules in place, is a much cleaner position than a dormant legacy environment where data lingers indefinitely.

Taking the first step

If your organisation is carrying a legacy SAP ECC6 system, or any other end-of-life platform with historical data attached to it, a structured decommissioning project is likely more achievable than you think.

Our complete guide to system decommissioning covers the full process in detail, from initial scoping through to post-migration support, and is a good starting point if you’re building the case internally.

For SAP systems, we offer a free initial assessment that identifies active modules, evaluates customisation levels, and produces a cost estimate and project scope. For non-SAP systems, we carry out a streamlined review to index your environment, understand the technologies involved, and map out reporting requirements.

If you’d like to talk through your situation, get in touch with the Proceed team.