Replatforming (also known as Lift-Tinker-and-Shift) is a cloud migration strategy that involves making targeted optimizations to applications during migration—such as adopting managed database services or containerization—without fundamentally changing the application's core architecture.
Context for Technology Leaders
For CIOs and enterprise architects, replatforming represents a pragmatic middle ground between the speed of lift-and-shift and the full benefits of refactoring. It allows organizations to capture meaningful cloud benefits like managed services, improved scalability, and reduced operational overhead while avoiding the cost and risk of a complete re-architecture. Typical replatforming changes include migrating from self-managed databases to managed services (RDS, Cloud SQL), moving to managed container platforms, or adopting cloud-native monitoring and logging.
Key Principles
- 1Targeted Optimization: Specific components are modified to leverage cloud-native services while the overall application architecture remains unchanged, balancing improvement with risk.
- 2Managed Service Adoption: Replacing self-managed infrastructure components (databases, caches, queues) with cloud-managed equivalents reduces operational burden while maintaining application compatibility.
- 3Incremental Improvement: Changes are scoped to deliver measurable benefits without requiring full application redesign, enabling predictable timelines and resource requirements.
- 4Operational Efficiency: Replatforming reduces the operational burden of running applications in the cloud by leveraging provider-managed services for common infrastructure components.
Strategic Implications for CIOs
Replatforming is often the optimal strategy for the majority of enterprise applications that don't justify full refactoring but would suffer from pure lift-and-shift economics. CIOs should develop assessment criteria that identify replatforming opportunities across their application portfolio. Enterprise architects should catalog approved replatforming patterns (e.g., database-to-managed-service migrations) and ensure standardization across migration waves.
Common Misconception
A common misconception is that replatforming requires significant application changes. In reality, most replatforming changes involve infrastructure and configuration modifications rather than application code changes, making it a relatively low-risk approach that delivers meaningful cloud benefits.