Loading content
Replatforming is the migration of an application to a different platform with minimal code changes to improve operational characteristics or scalability. The method targets platform-level optimizations (e.g., containers, PaaS, or cloud services) rather than full re-engineering. It typically reduces migration risk and time compared with a complete rewrite.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Replatforming moves an existing application to a different technical platform with limited business change, often as a step toward cloud or modern operations.
The term belongs to cloud-migration practice and spread through models such as the six Rs; it has no verified single author. Microsoft’s Cloud Adoption Framework treats migration as a planable, assessable transition of workloads.
Picture a move that adapts to new connections: the business house remains mostly the same, but runtime, database, infrastructure, or managed services change. Map dependencies and operating needs, migrate in small waves, compare behaviour and cost, and keep a reversal path.
Runtime or operating services change while the business purpose remains stable.
Application, data, interfaces, and operations must work together on the target platform.
Small waves keep risk, learning, and rollback decisions manageable.
Replatforming can improve operations, scaling, or security without demanding a full rebuild. The apparently modest move can affect data, performance, cost, and ownership, so target architecture and measurement matter.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.