How CPS and Microsoft Are Supporting UK Local Government Through Reform
How CPS and Microsoft support UK local government through reform, helping councils manage change, integrate technology, protect services and build confidence during transition.
Published 15/01/2026
Author: The CPS Team

Data migration is often treated as a technical exercise: lift the data, shift it to a new platform, and carry on. But anyone who has been through a major migration knows it is far more complex. It’s not just about moving files, it’s about preserving organisational memory, protecting compliance, and ensuring teams can still access the information they need to deliver projects with confidence.
This challenge is becoming particularly urgent with the end of life for Microsoft Project Online (POL). Organisations that have managed projects in POL for years now face critical questions: What happens to all our historical data? How do we retain lessons learned, maintain compliance, and still transition smoothly to new tools like Planner Premium or Microsoft Project?
In this blog, we’ll explore why historical project data matters so much, the risks of getting migration wrong, and the strategies you can adopt to make your migration not just seamless, but strategic.
Project data is more than lines on a Gantt chart, it’s the collective memory of your organisation. Every milestone, budget line, and risk log represents experience that can inform future decisions. Losing that information is more than an inconvenience; it’s a risk.
Preserve critical knowledge
Reduce risk of data loss
Maintain business continuity
In short: your historical project data isn’t just “old information”, it’s an asset that underpins resilience, compliance, and growth.
Drawing from our webinar, here are the core strategies to ensure migration is smooth, accurate, and future-proof.
Plan Thoroughly Before Migration
Protect Data Integrity
Archive with Structure
Test Before Going Live
Support Your Teams
| Step | Action |
|---|---|
| Audit | List all legacy systems, file formats, and storage locations. |
| Define | Identify which historical records must be migrated, archived, or retired. |
| Test | Conduct pilot runs on small datasets to refine methods. |
| Migrate | Use secure, monitored processes with logging and validation. |
| Archive | Apply metadata and retention policies to ensure accessibility. |
| Verify | Check data integrity and compliance after transfer. |
| Train | Provide user training and documentation for ongoing support. |
Too often, data migration is viewed as a burden, something to “get through” before business can continue as usual. But done well, migration and archiving can deliver real benefits:
Microsoft’s decision to retire Project Online means organisations can’t delay planning their migration strategy. Without proactive steps:
By taking a structured approach now, you not only protect your history but also set up your teams for success with Planner Premium, Microsoft Project, or a hybrid model that meets the needs of your organisation.
A successful migration is about more than moving files, it’s about preserving the integrity of your organisation’s history while positioning yourself for the future.
At CPS, we specialise in helping organisations not only migrate data securely but also rethink how they manage and retain project information in a world beyond Project Online.
Contact us today to learn how we can help you design a tailored migration and data retention strategy that protects your past while preparing for your future.