
Quick Summary
- Application migration to the cloud comes down to three decisions: choosing the right one of AWS’s 7 R’s, moving data safely, and cutting over while keeping the business running.
- What breaks after the move is the undocumented layer around the app: hard-coded IP addresses, forgotten cron jobs, credentials without an owner, and missing firewall rules.
- AWS Transform replaced AWS Migration Hub as the main planning tool, and Migration Hub and Application Discovery Service closed to new customers on November 7, 2025.
- Move the data before the app. Wait until replication lag is zero, pause writes for the final sync, and compare checksums in addition to row counts before you switch traffic.
- Costs slip on both sides of cutover. McKinsey’s 2021 survey found migrations ran 14% over budget each year, and Flexera’s 2026 vendor survey put wasted cloud spend at 29%.
Application migration to the cloud means moving one application, with its data, configuration, and integrations, from your own servers or another cloud to cloud infrastructure. The work comes down to three decisions. You choose which of the 7 Rs fits the app, how to move the data without losing anything, and how to switch users over without stopping the business.
These decisions are important because the trouble rarely comes from the app’s own code. What breaks after the move is the layer around it that nobody documented, such as hard-coded addresses, forgotten scheduled jobs, credentials without an owner, and missing network rules.
That is why we wrote this guide. It draws on our own migration work, including Complete Solaria’s move to AWS, and compares the seven strategies side by side, gives you a five-factor R-Selector, and walks through six steps with the tools AWS, Microsoft, and Google offer today.
By the end, you will know which route fits each app, how to plan an application migration to the cloud without losing data, and which security work stays with your team.
What Is Application Migration to the Cloud?
Application migration to the cloud is the process of moving an application from one environment, usually your own data center, to cloud infrastructure such as AWS, Azure, or Google Cloud.
Along with the app itself, you move its data, its configuration, and every connection it has to other systems. The same process applies when you move an app between clouds or migrate an application to a private cloud.
Those connections deserve the most attention because an application usually depends on databases, queues, internal services, and third-party APIs that must all keep working after the move.
Teams that treat migrating applications to the cloud as a simple copy operation often discover these dependencies in production, which is why a proper migration spends most of its time understanding the app before transferring anything.
Application migration vs. cloud migration
These two terms get mixed up constantly among clients, so it’s important to make it clear. Application migration moves a specific app along with its data, configuration, and integrations.
Cloud migration is a company-wide program to move the entire portfolio of applications, shared infrastructure, and all corporate data out of the data center. In other words, a cloud migration consists of many application migrations, plus everything those apps run on.
| Aspect | Application Migration | Cloud Migration |
| Scope | One application and its dependencies | Data, apps, infrastructure |
| Typical Goal | Move a workload safely | Change the whole operating model |
| Timeframe | Weeks to months per app | Quarters to years |
| Team | App owners plus a migration team | Company-wide program |
Timeframes are rough ranges based on our own project experience. Actual timelines depend on scope, connected systems, and data volume.
Reasons to Migrate Applications to the Cloud

Companies usually name four main reasons for moving applications to the cloud:
- Lower total cost of ownership
- The ability to scale on demand
- Better resilience
- Access to modern services such as AI tooling
Each of them solves a specific problem that stays unsolved in a data center, so let’s look at them one by one.
1. Lower total cost of ownership
When an app runs in your own data center, you pay for servers sized for the busiest day of the year, and most of that capacity sits idle the rest of the time.
On top of the servers themselves, you pay for new hardware every few years, for power and cooling, and for the people who maintain the machines.
In the cloud, you pay for the resources you provision, so your bill follows how you configure the app. Instead of large upfront purchases, infrastructure becomes a monthly bill you can track per application. Savings depend on right-sizing and turning off what nobody uses after the move. In IDC’s Cloud Pulse survey, nearly half of cloud buyers spent more on cloud than expected in 2023.
2. Scaling on demand
Your own data center gives you a fixed amount of capacity. When traffic grows, you have two options:
- Let the app slow down.
- Buy extra hardware months in advance and hope you guessed the demand right.
The cloud removes this problem when the app is set up to scale out, with autoscaling configured and no state tied to one server. It gives the app more capacity as demand grows and takes it back as demand drops, so the bill can follow demand.
Apps with seasonal or unpredictable load benefit the most. A retail system during holiday sales is a typical example.
3. Better resilience
Cloud providers operate multiple data centers in each region and give you the building blocks for resilience, but your team has to assemble them. For an infrastructure service such as Amazon EC2, AWS notes that the customer handles all resiliency configuration and management.
Backup and failover stop being projects that take months and become features you configure and test.
4. Access to modern services
Managed databases, analytics platforms, and AI services connect more easily with apps and data that already work in the same cloud. Reaching them from a data center is slower and costs more.
The 7 R’s of Application Migration to the Cloud
AWS lists seven migration strategies for moving applications to the cloud, known as the 7 R’s:
- Rehost.
- Replatform.
- Repurchase.
- Refactor.
- Retire.
- Retain.
- Relocate.
Every application in your portfolio ends up on one of these routes. AWS published its original six strategies in 2016, building on the five options Gartner described in 2011, and added relocate when VMware Cloud on AWS launched in 2017.
Other providers group the same choice differently. Microsoft’s Cloud Adoption Framework uses eight strategies and no relocate, and Google Cloud uses six migration types with its own names. The choice you make for each app stays the same.
The faster the route, the less it changes in the app and the less cloud value you get. The more the route changes, the longer it takes and the more value it unlocks.
1. Rehost (lift and shift)
Rehosting means moving the app to cloud servers exactly as it is. The code, database, and settings stay the same. Only the underlying hardware changes.
When it fits. The app works well, and you need to move out of a data center fast. Google notes that rehost migrations tend to be quicker than refactor or rebuild migrations. The trade-off is that the app is not optimized for the cloud, so the bill can grow unless you right-size it after the move.
2. Replatform
Replatforming means moving the app and changing a few parts of the platform, what AWS calls “lift, tinker, and shift.” The app’s code stays mostly the same. A typical example is moving a database you maintain yourself to a managed cloud database, so the provider handles updates and backups.
When it fits. You want some cloud benefits, such as less maintenance work, without rewriting the app. The move takes longer than a rehost, because each changed part needs testing.
3. Repurchase
Repurchasing means you stop using your own app and switch to a ready SaaS product that does the same job, an approach AWS calls “drop and shop.” Your data moves to the new product, and you switch off the old app.
When it fits. The app covers a standard function such as CRM, HR, or email, and a product on the market covers your needs. The trade-off is that you adapt your processes to the product and pay a subscription.
4. Refactor (rearchitect)
Refactoring means changing the app’s architecture so it uses cloud-native features, for example by splitting a monolith into separate services or moving parts of it to serverless functions. This is the most expensive and slowest route, and it unlocks the most cloud value.
When it fits. The app is core to the business and will keep evolving for years. AWS does not recommend refactoring in large migrations, because it means modernizing the app during the move, so in a big program you move first and modernize after. One AWS enterprise strategist wrote that he had sometimes seen refactoring take 20 times longer than rehosting or replatforming.
5. Retire
Retiring means switching the app off and archiving its data, because nobody needs it anymore. Portfolio assessments often find apps that still cost money but have no users left.
When it fits. Nobody uses the app, or another system already does its job. Retiring is the quickest way to save money in the whole project.
6. Retain
Retaining means leaving the app where it is for now and deciding again later.
When it fits. The app has a compliance restriction, depends on special hardware, or is close to end of life, so moving it now makes no sense. Give every retained app a review date, or it gets forgotten.
7. Relocate
Relocating means moving many servers at once from your own platform to a cloud version of the same platform, without changing the apps on them. AWS also uses this term for moving resources to another virtual private cloud (VPC), AWS Region, or AWS account, and it calls relocate the quickest way to migrate because the architecture stays the same.
When it fits. You have a large VMware estate and want to move it to the cloud with the least change.
Check licensing first, because the VMware market has changed:
- Since April 30, 2024, AWS no longer resells VMware Cloud on AWS, and Broadcom sells it instead.
- AWS offers its own Amazon Elastic VMware Service, which has been generally available since August 5, 2025.
- In November 2025, Microsoft says Broadcom began requiring customers to bring portable VMware Cloud Foundation licenses to all hyperscalers.
- Microsoft is retiring the Azure VMware Solution options that include the license by August 30, 2027.
- Google Cloud VMware Engine offers VMware in Google Cloud as a managed service.
Because of these changes, relocation may cost more than it did a few years ago.
The table compares the seven routes by effort, move cost, risk, and cloud value, and shows when each one fits. The ratings are relative for a typical application and come from our own assessment.
| Strategy | Effort | Cost | Risk | Cloud Value | When to Use |
|---|---|---|---|---|---|
| Rehost | Low | Low | Low | Low | Fast exit from a data center |
| Replatform | Medium | Medium | Low | Medium | Quick wins without code rewrite |
| Repurchase | Low | Medium | Medium | Medium | Standard functions covered by SaaS |
| Refactor | High | High | High | High | Core apps that keep evolving |
| Retire | Low | None | Low | Savings only | Apps without users |
| Retain | None | None | Low | None | Compliance or end-of-life apps |
| Relocate | Low | Medium, depends on VMware licensing | Low | Low | Large VMware estates, moves between VPCs, Regions, or accounts |
In the Cost column, cost means the cost of the move. The monthly bill after the move depends on how you configure the app.
Most portfolios end up using several R’s at once, and the next question is choosing the right application migration approach for each app.
Which R for Which App? The R-Selector
To pick the right application migration strategy, score each application on five factors:
- Business importance. How much the company depends on this app and whether it will keep evolving.
- Cloud fit. How well the current code works on cloud infrastructure without changes.
- Technical debt. How outdated the code is and how hard it is to maintain.
- Connected systems. How many databases, services, and APIs the app talks to.
- Timeline. How much time you have before the migration deadline.
A basic high, medium, or low rating for each factor is enough, and you do not need a complex scoring model. Business importance and technical debt are the most important factors, because together they show whether the app deserves investment or just a transfer.
Cloud fit tells you how expensive that transfer will be. An app on a standard stack moves easily, and an app tied to specific hardware or an old OS version needs work before it can move at all.
Connected systems define the risk. The more integrations the app has, the more things can break during the move, so heavily connected apps need more testing time regardless of which R you choose.
Timeline acts as the final constraint. A strategy you cannot finish before the deadline is the wrong strategy, whatever the other factors say.
Find your combination of ratings in the table. Each row shows five ratings and the route they point to.
| Business Importance | Cloud Fit | Technical Debt | Connected Systems | Timeline | Recommended R |
|---|---|---|---|---|---|
| Low | High | Low | Any | Any | Rehost |
| Low | Medium | Low or medium | Any | Any | Replatform |
| Low | Low | High | Any | Any | Rehost, revisit later |
| High | High | Low | Low or medium | Any | Rehost or replatform |
| High | Medium | Medium | Any | Comfortable | Replatform |
| High | Any | High | Any | Comfortable | Refactor for one core app, move first in a large program |
| High | Low | Any | Any | Comfortable | Refactor for one core app, move first in a large program |
| High | Any | Any | High | Any | Add a testing stage to any R |
| High | Any | High | Any | Tight | Rehost now, refactor later |
Three cases sit outside the table:
- An app nobody uses gets retired.
- An app with a compliance, hardware, or end-of-life blocker gets retained with a review date.
- If the app performs a standard function such as CRM, HR, or email, and a SaaS product meets your requirements, repurchase it.
If speed is the only constraint, relocate (for VMware estates) and rehost are the fastest routes, and neither improves the app.
Tools can also suggest an R. AWS Transform can recommend one of the 7 R’s for every server and application it discovers. Treat that as a starting point, because business importance and your deadline are not part of the inventory data.
The Application Migration Playbook (Step by Step)

These are the application migration to cloud steps we follow on our own projects, whatever R it takes.
Step 1 – Assess the application
We build a list of everything the app consists of and needs to run, including servers, databases, storage, OS versions, licenses, and current load. At this stage, we also collect the facts for the R decision, so by the end of discovery we know what the app is, who uses it, and what it costs to operate.
For example, when we moved Complete Solaria’s residential solar technology platform to AWS, our team first assessed the frontend, backend, architecture, and technical debt. The project also modernized the platform and improved its scalability, resilience, and delivery speed.
Done when. You have an inventory of servers, databases, storage, versions, licenses, and load, plus the facts for the R decision.
Step 2 – Map the dependencies
We find every system the app talks to, including databases, internal services, third-party APIs, scheduled jobs, and file transfers. Discovery tools map many of these connections. AWS says AWS Transform maps application dependencies automatically, Azure Migrate shows network dependencies between servers, and Google Cloud Migration Center identifies which components must migrate together.
Some connections only live in people’s heads, so we interview the engineers who support the app. For example, a nightly file export or a partner system that still calls an old address never shows up in network data.
The undocumented connections are the ones that break after the move.
Done when. Every system the app talks to has an owner and a target, and nothing in the list is marked unknown.
Step 3 – Choose the cloud, the strategy, and the wave
First, we settle the target, the provider, and cloud type (public, private, or hybrid). The choice depends on four things:
- Where the data may live under regulations, contracts, and data residency rules.
- Which managed services the app will use.
- Which platforms your team already uses and knows.
- Which licenses you already have, such as VMware.
Then we check the app against the R-Selector from the previous section and decide when it moves. Apps that share dependencies go in the same wave, so tightly connected systems move together. The schedule starts with low-risk apps and leaves the critical ones for later waves, when the team has practice.
Done when. Each app has a target, an R, and a dated wave.
Step 4 – Test the process on one small app
We migrate one small app end to end before touching anything important. The pilot proves the tooling, shows how long each step takes, and surfaces process gaps when the cost of a mistake is still low.
We treat it as a rehearsal and write down everything that surprised us.
Done when. One noncritical app has gone through every step, and we’ve written down the surprises.
Step 5 – Move the data first, then the app
We move the data before we move the application. Microsoft’s Cloud Adoption Framework says not to proceed to cutover until replication lag is zero, and to pause write operations for the final sync, because skipping the pause increases the risk of data loss.
We sync the data and compare row counts for a quick check and checksums or hashes for a deeper one. Then we move the app and reconnect the integrations one by one, testing each.
Done when. Replication lag is zero, counts and checksums match, and every integration is reconnected and tested.
Step 6 – Switch traffic and optimize
We switch production traffic to the cloud version, keep the old environment on standby as a rollback option, and watch the app closely for the first weeks. The rollback criteria are agreed with the business before the migration starts.
When the app works stably, we start optimization:
- Right-size servers that were sized for the old peak load.
- Remove unused resources.
- Set budgets and cost alerts.
- Set up monitoring and automated deployments for the new environment with our DevOps services.
- Review the bill every month.
This work is important because cloud waste grows fast. In Flexera’s 2026 State of the Cloud research, a vendor survey, respondents estimated wasted cloud spend at 29%, the first increase in five years, and 85% named managing cloud spend a top challenge.
Done when. The old environment is retired or has a retirement date, and the app has an owner for its monthly bill.
Migration tools on AWS, Azure, and Google Cloud
Each major cloud now has one main place to discover and plan a migration. AWS has AWS Transform, Microsoft has Azure Migrate, and Google has Google Cloud Migration Center. On AWS, the older Migration Hub and Application Discovery Service no longer accept new customers.
The table lists the main tools, what each one does, and its current status.
| Tool | What It Does | Status |
|---|---|---|
| AWS Transform | Discovery, dependency mapping, wave planning, and recommendations per app | Launched May 2025, successor to AWS Migration Hub |
| AWS Transform MGN | Moves physical, virtual, and cloud servers, cutover typically takes minutes | Formerly AWS Application Migration Service |
| AWS Database Migration Service | One-time migration or ongoing replication between databases | Available |
| AWS Migration Hub and Application Discovery Service | Earlier tracking and discovery tools | Closed to new customers since November 7, 2025 |
| Azure Migrate | Discovery, assessment, and migration of servers, databases, and web apps | Microsoft’s current migration service |
| Google Cloud Migration Center | Discovery, planning, dependency mapping, quick cost estimate | Current, cost estimate in Preview |
The table reflects AWS, Microsoft, and Google documentation as of October 15, 2026. These are the providers’ own descriptions, and network-based discovery cannot see dependencies that never cross the network, which is why Step 2 still includes interviews.
Security and Compliance During Application Migration
Security and compliance during application migration become a shared job. The cloud provider secures its infrastructure, and your team stays responsible for the data, identities, access, and configuration. Settle your part before the move, because it shapes the target environment and the cutover plan.
Here is what your team handles at each stage:
- What stays yours.
Your team keeps data classification, data protection, encryption decisions, and data governance, along with access controls such as role-based access, multifactor authentication, and conditional access. AWS says your share depends on the services and Regions you choose, how they connect to your IT environment, and the laws that apply to the workload. - Before the move.
List the rules that apply to this app’s data, such as the Health Insurance Portability and Accountability Act (HIPAA), the Payment Card Industry Data Security Standard (PCI DSS), customer contracts, and data residency. Check them against the target Region and services as part of Step 3. - During the move.
Move data over a private connection or an encrypted virtual private network (VPN), because Microsoft’s framework treats the public internet as a path only for less sensitive data. Give migration tools temporary access with the fewest rights they need, and remove that access after cutover. - After the move.
Replace credentials that lived on the old servers with managed identities or roles, as Microsoft’s framework recommends. Turn on audit logging before users arrive.
This guidance covers engineering work and does not replace legal or compliance advice. A provider’s audit reports cover the controls you inherit, and AWS tells customers to review them to see which required controls they still need to implement. Whether your workload meets a rule depends on how you configure it.
What Breaks During Application Migration and a Readiness Checklist
An application migration can succeed technically and still break in production. The app runs, the data is in place, and still the orders stop coming through, because some part of the system around the app never made the trip. After enough projects, the list of usual suspects becomes predictable, so here is what to look for.

1. Hard-coded IP addresses
Somewhere in the code or configuration, the app calls another system by its exact address instead of a name. The old address died with the data center, and the call quietly fails.
2. Scheduled jobs
Cron jobs and scripts that ran on the old servers for years, sending reports, cleaning tables, syncing files. Nobody put them in the migration plan because nobody remembered they existed, and their absence shows up days later.
3. Integration credentials
API keys, certificates, and service passwords that lived on the old machines or, worse, in one engineer’s head. The new environment needs all of them, and finding an owner for a five-year-old certificate takes longer than the whole migration. Where the platform allows, replace stored credentials with managed identities or roles.
4. Firewall and network rules
The old environment accumulated years of allow rules that let systems talk to each other, and the new environment starts from a blank page. Every partner and every internal service that connected to the app needs a working path to its new home.
The pattern behind all four is the same. The undocumented things around the application break far more often than the application’s own code. A pre-flight checklist catches most of them before cutover.
| Check | What to Verify |
| Dependencies | Every connected system found and mapped |
| Hard-coded values | IPs, hostnames, paths replaced with configuration |
| Scheduled jobs | All cron jobs and scripts moved and tested |
| Credentials | Keys, certificates, passwords collected with owners |
| Network rules | Access paths open for every partner and service |
| Data | Counts and integrity verified after sync |
| Rollback | Old environment ready to take traffic back |
| Downtime window | Cutover time agreed with the business |
Run this application migration to the cloud checklist before every cutover, even for small apps.
Why migration projects fail
A migration can work technically and still fail as a project. In McKinsey’s 2021 survey of nearly 450 chief information officers (CIOs) and IT decision makers, the average company spent 14% more on migration than planned each year, and 38% of companies saw migrations delayed by more than a quarter.
Watch for four project problems:
- Dependencies found too late.
A 2021 Gartner article warned that missed interdependencies lead to wrong grouping and ordering of migrations, network performance issues, and cascading delays. Step 2 is there to catch them early. - Budget and dates set before discovery.
Set them after the assessment and the pilot, when you know what the app needs. - A team isn’t ready to support the app.
Plan training, runbooks, and on-call duty for the new environment before cutover. - No owner and no rollback rule.
Name an owner for each app and agree on rollback criteria with the business before the migration starts.
How to Migrate Without Stopping the Business
To migrate an application without stopping the business, keep the old system serving users until the cloud version proves it works on production data. Then switch users over in a short window or in steps, with a tested rollback until the last user moves.
Two main ways get you there: a replication-based cutover and a parallel run, and both often end with a gradual traffic shift. The table compares the three approaches, when each one fits, and how you roll back.
| Approach | How It Works | Fits Best When | Limits | Rollback |
|---|---|---|---|---|
| Replication-based cutover | Data replicates until lag is zero, then a short write pause | The app does not change (rehost, relocate) | Does not test changed behavior, needs a short write pause | Point traffic back to the untouched source |
| Parallel run | New version processes a copy of production traffic, outputs compared | Critical apps whose platform or code changed | Two environments working side by side for weeks | Users have not left the old system |
| Gradual traffic shift | A small share of users moves first, then the share grows | Final step for apps that users work with directly | Data changes must stay backward compatible | Move the share back to the old version |
For server moves, AWS says cutover windows with AWS Transform MGN are typically minutes. If the data cannot be replicated or kept in sync, agree on a planned downtime window with the business, as the readiness checklist suggests.
Parallel run and shadow mode
In shadow mode, the cloud version works on production data and users keep working in the old system. The process has four steps:
- Start the cloud version next to the old one.
- Send it a copy of the production traffic.
- Let it process the traffic and write results to its own side.
- Compare the outputs of both versions daily.
If the cloud version produces the same orders, totals, and reports as the old one, it is ready. Every mismatch points to a bug you caught before it reached a single user.
When the outputs match over a few weeks, you gradually shift production traffic. Start by moving a small share of users (Microsoft’s example starts with 5%), monitor the metrics, and increase the share step by step, keeping the old system ready to take everything back until the last user moves.
Case study: MasterControl identity migration
Challenge. MasterControl needed to move millions of user accounts to a new identity provider without cutting users off from their accounts.
What we did. Three Zoolatech software engineers worked with MasterControl engineers on a joint team. During the early migrations, a hybrid integration kept the old vendor’s multifactor authentication (MFA) working, and rollouts went phase by phase across development, test, and production environments.
Result. The team moved millions of user accounts with zero disruption. About 20% of users moved within the first 90 days, and more than 60% by the six-month mark. Read more about MasterControl’s identity provider migration.
This was an identity migration, and it follows the same pattern as an application move. The old and new systems run side by side, and users move in phases.
For legacy systems, our guide to legacy system migration without downtime covers traffic, data, and user moves in more detail. You can also see how we approach cloud migration and modernization.
Migrate the portfolio in waves
The same thinking applies at the portfolio level. Moving everything in one weekend puts all the risk in one place, so enterprise migrations move in waves.
Each wave is a group of apps that moves together. When migrating enterprise applications to the cloud, group apps that share dependencies, priority, or architecture into the same wave so connected systems never split between the data center and the cloud. AWS recommends keeping each wave within 6 to 10 weeks.
Early waves take low-risk apps, and business-critical systems move last, when the team has tooling and practice. An example wave plan for a mid-size portfolio looks like this:
| Wave | What Moves | Why This Order |
|---|---|---|
| 1 | Pilot app, internal tools | Low risk, team learns the process |
| 2 | Standalone apps with few integrations | Volume without complexity |
| 3 | Connected app groups | Shared dependencies move together |
| 4 | Business-critical systems | Parallel run, full team experience |
Cost, Risk, and Technology-Specific Paths
The cost and risk of a migration grow with the amount of change. Retiring unused apps and rehosting apps with few dependencies brings the fastest savings at the lowest risk. Refactoring costs the most and takes the longest.
The fastest route can cost more later. Gartner warned in 2021 that defaulting too quickly to rehosting and deferring modernization can raise cloud operating costs after migration.
That logic covers most of the portfolio, but some technology paths deserve their own notes because each has its own patterns.
Java application migration to AWS
Java apps are usually the easiest candidates for migration from on-premises to AWS because Java runs the same way on cloud servers as it does in data centers.
A typical Java application migration to AWS starts with a rehost, with quick wins coming right after. Moving the database to a managed AWS database service removes the maintenance burden, and packaging the app in containers simplifies deployments.
Apps on an old version of Java often need an upgrade before cloud services will accept them. The same sequence applies to .NET apps migrating to Azure, where the managed services differ but the order of steps stays the same.
Mainframe application migration to the cloud
Migrating mainframe applications to the cloud is the hardest case of legacy application migration.
In practice, you have three options. You can move the workload to a cloud service that imitates the mainframe, rewrite the old code in a modern language, or replace the function with a ready SaaS product. These projects last for years, so they get planned as legacy modernization programs instead of plain migrations.
Database migration
Teams keep the application online by replicating the database as users keep working, then switching during a short write pause. AWS Database Migration Service, for example, can replicate ongoing changes to keep the source and target databases in sync. Microsoft’s framework adds three rules:
- Wait until replication lag is zero.
- Pause writes for the final sync.
- Validate with checksums or hashes in addition to row counts.
The database deserves separate planning in any migration, because it holds the data that everything else depends on. You can keep the same database type in the cloud, or switch to a different one along the way, for example, to stop paying expensive license fees.
A switch multiplies the work because you have to rewrite and test parts of the code written for the old database. Replication tools copy the data and keep the old and new databases in sync, so the final switch becomes a brief write pause.
The table summarizes the typical strategy, main risk, and time scale for each path.
| Path | Typical Strategy | Main Risk | Time Scale |
|---|---|---|---|
| Java to AWS | Rehost, then improve | Outdated Java version | Weeks to months |
| Mainframe to cloud | Rewrite or replace | Lost knowledge, old formats | Years |
| Database | Managed cloud database | Code rewrite for a new database | Weeks to months |
Time scales are rough ranges based on our own project experience. Actual timelines depend on scope, connected systems, and data volume.
Other legacy applications
Legacy application migration to the cloud starts with checking cloud fit. Old operating systems and runtimes may need an upgrade before the target platform supports them, and undocumented integrations are more likely, so the readiness checklist is most important here.
If the app needs more than a move, plan it as modernization. Our guide to legacy system modernization explains how to approach that work.
Final Word
Application migration to the cloud takes patience. You have to inventory the apps, score each one, chase the owners of forgotten scripts and certificates, and test more than anyone wants to.
But this effort pays off.
A migration done in the right order gives you apps that cost less to operate, scale when the business grows, and connect to the services your roadmap needs. A rushed migration moves the same problems to someone else’s servers and adds a few new outages.
Treat the sequence in this guide as the minimum bar:
- Assess the app before you choose a strategy.
- Pick an R for each app separately.
- Settle security and the target cloud before the move.
- Test the process on a pilot app first.
- Move the data before the app.
- Switch traffic with a rollback ready.
If a step feels skippable, it is usually the step that would have caught the problem. And if you want an experienced team next to yours, Zoolatech is ready to discuss your migration.
Questions You May Have
What is application migration to the cloud?
Application migration to the cloud is the process of moving an application, together with its data, configuration, and integrations, from your own servers or another cloud to cloud infrastructure.
What is the difference between application migration and cloud migration?
Application migration moves one specific app between environments, and cloud migration is the company-wide program that moves the entire portfolio of apps, infrastructure, and data.
What are the 6 R's of migration?
The 6 R’s are six migration strategies AWS described in 2016, namely rehost, replatform, repurchase, refactor, retire, and retain. AWS now lists seven strategies, the 7 R’s, adding relocate, which arrived with VMware Cloud on AWS in 2017. Microsoft and Google group the same choices into different lists.
How do you migrate an application to the cloud?
You assess the app, map its dependencies, choose a migration strategy, test the approach on a pilot, move the data first, and only then switch production traffic to the cloud version.
How do you migrate an application with zero downtime?
Keep the old system serving users as the new one catches up. Replicate the data until the lag is zero, pause writes for the final sync, and then shift users in steps with a rollback ready. If the app changed during the move, keep both versions working in parallel and compare their outputs before anyone moves.
What usually breaks during a migration?
Hard-coded IP addresses, forgotten scheduled jobs, undocumented integration credentials, and missing network rules break far more often than the application itself.
How long does application migration take?
The duration depends on the strategy, the number of connected systems, and how much data has to move. None of the AWS, Microsoft, or Google guides we checked gives a standard duration per strategy. For portfolios, AWS recommends keeping each migration wave within 6 to 10 weeks, and one AWS strategist has seen refactoring sometimes take 20 times longer than rehosting.
Should we rehost or refactor?
Rehost when the app is stable and speed is important, and refactor when the app is core to the business, carries heavy technical debt, and will keep evolving for years. In a large migration program, AWS recommends moving first and refactoring after, because refactoring means modernizing the app during the move.
What are the main application migration to cloud steps?
The main steps are assessment and discovery, dependency mapping, choosing the target cloud and the strategy, wave planning, a pilot, data migration, and cutover with optimization.
When does it make sense to use application migration to cloud consulting?
Consulting pays off when the portfolio is large, the team has no migration experience, or the apps are too critical to learn on, because an outside team brings tested playbooks and tooling.
Is migrating a web application to the cloud easier than other types?
Usually, yes, because most web applications run on standard stacks with few hardware dependencies, making them natural candidates for a rehost or replatform.
Which applications should not be moved to the cloud?
Apps blocked by compliance, hardware, or end of life, and apps nobody uses, should stay where they are or be retired. Steady, large workloads can also cost less on owned hardware. 37signals says leaving the cloud cut its yearly cloud bill from $3.2 million to $1.3 million in 2024, though IDC found that only 8–9% of companies plan to move all workloads back out of the public cloud.
Why is the cloud bill often higher after migration?
One reason is sizing, because a rehosted app keeps the server sizes it had on premises. Google notes that rehosted workloads are not optimized for the cloud, and Gartner warned in 2021 that defaulting to rehosting can raise operating costs after migration. Right-sizing after cutover, described in Step 6, is where the savings start.












