IT Infrastructure & Cloud
What Is Lift-and-Shift in Cloud Migration?
Lift-and-shift, or rehost, moves a system to the cloud as it is. It is the fastest and lowest-risk approach, but the savings only come after tuning.
SEO and Content Specialist
2 min read
Short answer: lift-and-shift (also called rehost) means moving a system from your own server to a server in the cloud without changing how the application is built. It is the fastest and lowest-risk way to move to the cloud, but the bill is often not lower yet because the server sizes still mirror the old servers. Savings usually come from tuning after the system has moved.
When lift-and-shift fits
| Situation | Why lift-and-shift fits |
|---|---|
| The old server must be retired soon | The shortest move, with no waiting for the application to be changed |
| The application is hard to change or nobody understands its code | The code does not need to be touched |
| Many systems are moving at once | The pattern is uniform and easy to repeat |
| You want gradual modernization | Move the system first, then restructure it once it runs in the cloud |
Risks to anticipate
The most common problem is not technical but the bill. Old servers are usually bought with spare capacity for several years, and if that size is copied to the cloud as is, you pay every month for capacity you do not use. Another issue: the operating system and its updates still have to be managed by you, just as on the old server.
Lift-and-shift does not mean no preparation
Even though the application is not changed, the move still needs preparation: mapping the system’s dependencies (databases, shared files, other services it calls), setting up the network and access rights in the cloud, testing the system in the new environment before switching over, and choosing the cutover window that disrupts users the least. A rollback plan to the old server should also exist, in case something goes wrong after the switch.
When lift-and-shift fits less well
Lift-and-shift is a poor fit for systems whose usage rises and falls sharply, because the biggest benefit of the cloud (adjusting capacity to load) is only felt after the architecture has been adapted. It also does not solve problems in the application itself: an application that is slow or hard to maintain on the old server will stay that way in the cloud.
Steps after the system has moved
- Monitor real usage for a few weeks, then adjust the server sizes.
- Set budget limits and usage alerts, so a rise in the bill is noticed before the end of the month.
- Consider replatforming the components that are hardest to maintain, such as the database, once the system is stable.
- Shut down the old server only after the system in the cloud has proven stable and its backups have been tested.
A comparison of lift-and-shift with replatform and refactor is in the article Rehost, Replatform, or Refactor. At Legia, the migration path is chosen per system during the readiness assessment and ends with cost tuning, as part of the Cloud Migration & Architecture service.
Sources
Does your office server or network need to be set up and looked after? See Legia IT infrastructure and cloud services, or schedule a consultation through the contact page.


