Replatforming

What Is Replatforming?

Replatforming is moving an application to a new platform while making only targeted changes to take advantage of it. The core code and architecture stay. A self-managed database becomes a managed service. An application server is swapped for a supported runtime. A file store moves to cloud object storage.

It occupies the middle of the modernization spectrum. It delivers more than rehosting, because some operational burden disappears with the managed components. It costs far less than refactoring, because the application is not rewritten. For applications that still earn their keep, it is often the pragmatic option.

It is not always the right one. Replatforming assumes the application is worth keeping. If the business function has been replaced, or the system survives only because its data must be retained, the cheaper and cleaner answer is to archive the data and retire the application rather than invest in moving it.

Key Points

• Targeted change, not a rewrite. Adjustments are limited to what the new platform needs or offers, so timelines stay manageable.
• Reduces some operational burden. Managed databases and runtimes shift patching and maintenance to the platform provider.
• Assumes the application has a future. The business case only holds for applications that remain in active use.
• Compatibility testing is the main effort. Minor platform differences, such as database versions and drivers, cause most of the surprises.
• Retirement is a legitimate alternative. For low-use or data-only systems, archiving and shutdown avoids migration cost entirely.

Common Use Cases

Moving to a managed database

An application keeps its logic and swaps a self-hosted database for a managed cloud service, removing routine patching and backup work.

Containerizing a stable application

A working application is packaged to run on a container platform with minimal code change, easing deployment and scaling.

Deciding between keep and retire

A portfolio review compares the cost of replatforming an aging application with archiving its data and retiring it. For data-only systems, retirement usually wins.

Replatforming vs. Related Concepts

The boundary between these terms is depth of change.

REHOSTING

Moves the application to new infrastructure with no changes at all. Faster and shallower than replatforming.

REFACTORING

Rewrites significant parts of the code or architecture. Replatforming leaves the code largely as is.

REPLACING

Swapping the application for a different product, often SaaS. The old application is then a retirement candidate.