CLOUD & INFRASTRUCTURE
Keep important services available.
Teaching and operations depend on identity, storage, applications and backup. Modernisation works best when dependencies and recovery requirements are understood before moving services.
Discuss this priority ↗
A dependency map, recovery priorities, a migration sequence and a documented fallback.
WHAT THE WORK COVERS
Three connected decisions.
Map dependencies
Document key systems, integrations, data locations and service owners.
Test recovery
Agree backup frequency, restore priorities and realistic recovery exercises.
Sequence change
Pilot migrations, retain rollback options and schedule around critical teaching periods.
PRACTICAL DELIVERY
Start with the evidence.
The output should be a phased roadmap with ownership and recovery priorities, not just a list of replacement servers.
Recovery matters
A tested route back to service is as important as the systems that run each day.
See the relevant Department for Education guidance for England. Fortem can help turn the requirements and your local priorities into a workable brief.
COMMON QUESTIONS
Before you decide.
Cloud or on-site?
The appropriate choice depends on applications, connectivity, data, support and recovery needs. A review should make these trade-offs explicit.
How do we reduce migration risk?
Map dependencies, pilot, agree rollback steps and test access before the change reaches all users.