What & Why We Move
Before you pack a single box, it helps to know what "migration" actually means and why anyone bothers. In this opening lesson we define IT migration in plain words, walk through the real reasons organizations move, weigh the benefits against the risks, and map out the different directions a move can take. By the end you'll speak the vocabulary the rest of the course builds on.
Imagine your family lives in a creaky old house (Fort Rusty). The roof leaks, the rooms are too small, and repairs cost a fortune. So you decide to move to a bright new apartment in Cloudville. Migration is the whole job of carefully packing your boxes (data), your family and pets (apps), and your furniture (servers) and settling into the new place — without losing anything or leaving the lights off too long.
What is IT migration?
☺ Like you’re 10: It's moving your computer stuff from one home to another — same family, new house.
IT migration is the process of moving digital things — applications, data, databases, virtual machines, and whole workloads — from one computing environment to another. The "environment" you move from is often an on-premises data center (your own servers, sitting in a room or building you own or rent — we nickname it Fort Rusty). The environment you move to is frequently the cloud (computing power you rent over the internet from a provider — our Cloudville).
Let's define the four things that actually get moved, because the whole course keeps referring to them:
- Applications — the programs that do useful work: your email system, your online store, your payroll software. (In our world: the family and pets.)
- Data & databases — the information itself. A database is an organized store of that information, like a giant, searchable filing cabinet. (The boxes — and Ellie the Elephant never drops one.)
- Virtual machines (VMs) — a VM is a whole computer that exists as software: it acts like a physical PC or server but runs as a file on top of shared hardware. (The furniture you pick up and carry.)
- Workloads — a catch-all word for "a chunk of computing work," usually an app plus the data and machines it needs to run. When people say "we migrated 40 workloads," they mean 40 self-contained bundles of work.
Why move at all? The drivers
☺ Like you’re 10: Nobody moves house for fun. There's always a reason — cheaper rent, more space, or the old place is falling apart.
A driver is simply the business reason pushing the move. Real migrations usually have several at once. Here are the common ones:
| Driver | What it means in plain words |
|---|---|
| Cost reduction | Stop buying and maintaining expensive hardware; pay only for what you use. |
| Scalability & elasticity | Scalability is the ability to grow; elasticity means shrinking back down automatically when demand drops — like a room that expands on busy days and shrinks on quiet ones. |
| Agility & speed | Launch new ideas in minutes instead of waiting months for hardware to arrive. |
| Innovation & managed services | Rent ready-made building blocks (AI, analytics, databases) instead of building them yourself. |
| Security & compliance | Tap into strong built-in protections and certifications to meet legal rules. |
| Aging / end-of-life hardware | Old servers stop getting support and repairs; replacing them is a natural moment to move. |
| Data-center exit / lease expiry | The building lease is ending, so the servers need a new home anyway. |
| Mergers & acquisitions (M&A) | Two companies join and must combine their computer systems. |
| Disaster recovery (DR) | Keep a safe copy elsewhere so a fire or flood doesn't erase the business. |
| Sustainability | Shared, efficient data centers often use less energy than one company's own. |
| Talent gaps | Hard to hire people to babysit old hardware; the cloud handles more of that for you. |
Migration is never done "just because." Every good move traces back to one or more business drivers. If you can't name the driver, you're not ready to move yet — a lesson we return to in best practices.
Benefits versus risks
☺ Like you’re 10: The new apartment is great, but moving day can still go wrong. Smart movers plan for both.
The upside is real: lower upfront cost, room to grow instantly, faster experiments, and access to shiny new tools. But moving is genuinely risky, and pretending otherwise is how projects fail. Weigh both sides:
| Benefits ✓ | Risks ⚠ |
|---|---|
| Pay-as-you-go costs, less wasted hardware | Cost overruns — clouds can get pricey if left unwatched |
| Grow or shrink capacity on demand | Downtime — the service being unavailable during the move |
| Faster delivery of new features | Data loss — boxes going missing if the move is sloppy |
| Access to managed, cutting-edge services | Skills gap — the team not yet knowing the new tools |
| Stronger built-in security options | Vendor lock-in — getting stuck with one provider and finding it hard to leave |
| Global reach and reliability | Complexity — more moving parts to understand and manage |
Vendor lock-in is the sneaky one. The more you use a provider's unique features, the more convenient life gets — but the harder it becomes to move away later. It's a trade-off, not automatically bad. We dig into the traps in anti-patterns.
Which direction? The kinds of moves
☺ Like you’re 10: You can move to a new house, redo your current one, switch apartments, or even move back to the old place. Same idea for computers.
"Migration" isn't only "old building to cloud." There are several directions, and knowing the words keeps conversations clear:
- On-prem → cloud — the classic move from your own data center to a provider like AWS, Azure, or Google Cloud.
- On-prem → on-prem (hardware refresh) — staying in your own building but swapping tired old servers for new ones.
- Cloud → cloud — moving from one provider to another (covered in cloud-to-cloud).
- Hybrid — deliberately keeping some things on-prem and some in the cloud, connected together, as a permanent setup.
- Multi-cloud — using two or more cloud providers at once, on purpose.
- Cloud repatriation (the reverse) — moving a workload back from the cloud to on-prem, usually for cost or control reasons. Yes, sometimes the right answer is to move home.
IaaS, PaaS, SaaS — and who's responsible
☺ Like you’re 10: Renting a bare apartment, renting a furnished one, or paying for a hotel room — different amounts of "do it yourself."
Cloud comes in three service styles, sorted by how much the provider handles for you:
- IaaS (Infrastructure as a Service) — the provider rents you raw building blocks: virtual servers, storage, and networking. You install and manage everything on top. Like a bare apartment: walls and plumbing provided, you bring the furniture. (Example: AWS EC2.)
- PaaS (Platform as a Service) — the provider also handles the operating system and runtime, so you just bring your app and data. Like a furnished apartment: move in and start living. (Example: Azure App Service.)
- SaaS (Software as a Service) — the provider runs the whole finished application; you just log in and use it. Like a hotel: everything's handled, you just enjoy the room. (Example: Gmail or Salesforce.)
This connects to a crucial safety concept called the shared responsibility model. The rule of thumb: the provider secures the cloud itself (the buildings, hardware, and core services), and you secure what you put in it (your data, your accounts and passwords, your settings). The line between "their job" and "your job" slides depending on whether you chose IaaS, PaaS, or SaaS — which is exactly what the schematic above shows.
Foxy: Wait — if I move to the cloud, does the provider keep everything safe for me? I can stop worrying, right?
Professor Owl: Half right, Foxy. They secure the building and the hardware. But your data, your passwords, and your settings? Still your job. That's the shared responsibility model.
Gizmo: Pfft. Just leave the front door unlocked and pick SaaS for everything — the provider handles it ALL!
Master Panda: Slow down, little gremlin. Even in a hotel you still lock your own suitcase. A leaky password sinks you no matter who owns the walls.
Timmy: Fact-check: correct. In every cloud model, the customer always stays responsible for their own data and access. Provider secures of the cloud; you secure in the cloud.
Building the business case: TCO and ROI
☺ Like you’re 10: Before you move, add up ALL the costs — not just the rent — and check whether the new place is actually worth it.
Leaders won't approve a move on vibes. They want two numbers:
- TCO (Total Cost of Ownership) — the full cost of running something, including the hidden bits: hardware, electricity, cooling, staff time, licenses, and repairs. Old data centers hide a lot of cost in "we already own it."
- ROI (Return on Investment) — what you get back compared to what you spend. If moving costs $1 and saves or earns $3, that's a strong ROI.
A solid business case compares the TCO of staying put against the TCO of moving, then shows the ROI over time. Sol the Sloth handles this careful math throughout the course; the counting groundwork begins in the migration journey.
Pick one app you use every day (say, your photo storage). Write down: (1) one driver that might push it to the cloud, (2) one risk of moving it, and (3) which model it feels like — IaaS, PaaS, or SaaS. No wrong answers — you're practicing the vocabulary, not building anything yet.
1. In one sentence, what is IT migration? 2. Name three drivers that push an organization to migrate. 3. Under the shared responsibility model, who secures your data and passwords — you or the provider? 4. Order IaaS, PaaS, and SaaS from "you manage the most" to "you manage the least."
Check your answers
- IT migration is moving apps, data, databases, VMs, and workloads from one computing environment to another (for example, from an on-premises data center to the cloud).
- Any three of: cost reduction, scalability/elasticity, agility/speed, innovation & managed services, security & compliance, aging hardware, data-center exit, mergers & acquisitions, disaster recovery, sustainability, talent gaps.
- You do. The provider secures the cloud itself (hardware and buildings), but securing your data, accounts, and passwords is always your responsibility.
- IaaS (you manage the most) → PaaS → SaaS (you manage the least).