Replatforming
Targeted changes that capture operational wins without a rewrite.
3 to work through
-
intermediate
A marketplace replatforms a service from a self-managed database to a managed one. What benefits are real, what constraints appear, and what must be verified first?
2 min answer -
intermediate
A team replatforms a self-managed database onto a managed service in six weeks and the project lands on time. Eighteen months later they are running an unplanned major-version upgrade over a weekend because the provider's standard support for their engine version ends. What did the replatform actually trade away, and when does that bill arrive?
3 min answer -
advanced
You have twelve weeks and a large estate. Which replatforming changes do you make and why those?
2 min answer
3 terms in this topic
Managed Service Substitution
Replacing a self-managed component with a managed equivalent during migration, without changing the application's architecture.
conceptManaged Service Upgrade Calendar
The obligation, transferred to the provider at replatform time, to upgrade before a published end-of-standard-support date, which converts an indefin…
practiceReplatform
Moving a workload with targeted changes that capture most of the platform's benefit without redesigning the application.
Neighbouring topics
Legacy Modernization
General material on modernising existing systems.
Legacy Assessment
Understanding what a system does before deciding what to do with it.
The Six Rs
Rehost, replatform, refactor, repurchase, retire, retain — per application.
Rehosting
Lift and shift: fastest, cheapest, and capturing none of the benefits.
Refactoring & Re-architecting
Changing structure incrementally while the system keeps running.
Rebuild vs Re-architect
Why greenfield replacement fails, and the narrow cases where it does not.
Strangler Fig
Routing capabilities to new implementations behind a facade, one at a time.
Application Decomposition
Finding seams in a monolith, starting from the data.
Database Migration
Moving engines, versions and schemas without losing data or uptime.
Data Migration Strategies
Backfill, dual-write, reconciliation and verification.
Zero-Downtime Migration
Expand, migrate, contract — and the contract phase that never happens.
Parallel Run
Shadowing the old system to discover the rules nobody documented.
Cutover Planning
Rehearsals, go/no-go criteria and a rollback that has been executed.
Legacy Integration Patterns
Anti-corruption layers, adapters and CDC against systems that cannot change.
Mainframe Modernization
Batch windows, COBOL, and the risk profile of core banking systems.
Migration Risk
Bounding blast radius, staging by cohort, and honest readiness reporting.
Modernisation Business Case
Pricing tail risk so deferred maintenance becomes fundable.
Coexistence Patterns
Running old and new together for years without corrupting either.
Decommissioning
Actually switching the old system off, and proving nothing depended on it.