Most cloud migration surprises appear on cut-over night: a scheduled job nobody documented, a bank API that only accepts your old server's IP address, a licence tied to physical hardware, or a database far larger than anyone thought. Each one is easy to handle a month earlier and painful at 2 a.m.
This readiness checklist covers twelve things to have in place before any server, database or file share moves. Use it to judge whether you are ready yourself, or to brief a migration partner so the plan starts from facts.
Quick answer: You are ready to migrate when you have a complete inventory, a dependency map, performance baselines, a data transfer plan, licence clearance, a strategy and owner for each workload, a secure landing zone, agreed cut-over windows, lowered DNS TTLs and a rehearsed rollback plan. Each missing item is a risk you will otherwise meet during the cut-over itself.
Part 1: Know exactly what you have
- A complete inventory. Every server, virtual machine, database, file share and scheduled task (cron jobs, Windows Task Scheduler), with operating system version, size, owner and purpose. Include the “temporary” server under someone's desk.
- A dependency map. Which application talks to which database, mail relay, SMS gateway, payment gateway, biometric device or Tally connector, and over which ports. Search configuration files for hard-coded IP addresses. Many bank and payment APIs only accept calls from whitelisted IPs, so the new cloud IP must be approved before cut-over.
- Performance baselines. CPU, memory, disk and network usage over a normal week and a busy one, such as month-end closing or a sale. Without this you cannot size the new servers or prove the cloud is performing at least as well.
- A data transfer plan. Measure how much data needs to move and check your upload bandwidth. As a rough example, 1 TB over a 100 Mbps line takes about a day even at full speed, and real throughput is lower. Plan an initial copy well in advance and a small final sync during cut-over.
Part 2: Decide what happens to each workload
Not everything should move the same way, and some things should not move at all. Agree a strategy per application before you plan the waves.
| Strategy | What it means | Suits | Watch out for |
|---|---|---|---|
| Rehost (lift and shift) | Move the server as it is to a cloud VM | Quick exits from ageing hardware, Tally or desktop ERP servers | Old problems move with it; rightsize after the move |
| Re-platform | Small changes, such as moving MySQL to a managed database service | Databases and web apps where managed services cut admin work | Version compatibility and features you rely on |
| Refactor | Redesign parts of the application for cloud services | Products that need to scale or carry heavy technical debt | Takes longest; usually better after the move |
| Retire | Switch it off | Old apps nobody uses, duplicate file shares | Archive the data and confirm with the owner first |
| Retain | Keep it where it is for now | Systems tied to local hardware, such as attendance devices or plant machines | Plan secure connectivity to the cloud |
- A licence review. Windows Server, SQL Server, Oracle and many ERP or accounting licences have specific terms for cloud or virtual use. Ask each vendor whether you can bring your existing licence or need a cloud-included one.
- Owners and acceptance tests. Every application needs a business owner who defines what “working” means, such as raising an invoice, running payroll or printing a delivery challan, and who signs off after migration.
If you want a second opinion on these choices, a cloud migration assessment produces a per-workload plan and a cost comparison that includes hardware refresh, power, licences and staff time.
Part 3: Build the landing zone before moving anything
- Accounts you own. Cloud accounts or projects registered to your company and billed to you, with multi-factor authentication on every admin login and least-privilege roles for staff and vendors.
- A network design. Plan IP ranges that do not overlap with your office LAN. A cloud network that uses the same range as your office, such as 192.168.1.0/24, makes a site-to-site VPN difficult later. Decide how offices, branches and remote staff will connect.
- Security and backups in place first. Encryption, logging, firewall rules and automated backups should be configured and tested before real data arrives, not added afterwards.
Part 4: Plan the cut-over and the way back
- Cut-over windows. Pick low-traffic times and avoid month-end, payroll, GST return deadlines and sale days. Tell users in advance what will be unavailable and for how long.
- Lower DNS TTLs early. Reduce the TTL on the records you will change, for example to five minutes, at least as long before cut-over as the current TTL. Otherwise some users keep reaching the old server for hours after the switch.
- A rehearsed rollback plan. Define go and no-go checks, freeze writes on the old database during the final sync, and keep the old environment intact until the new one has run cleanly for an agreed period. Rehearse both the cut-over and the rollback once in a test run.
After go-live: the first 30 days
- Watch the bill weekly: compare actual cloud spend with the estimate, and rightsize servers that were sized generously for safety.
- Run a restore test: prove the new backups work by restoring one database and one file share.
- Update documentation: architecture diagrams, IP addresses, access lists and runbooks should describe the new setup, not the old one.
- Raise the DNS TTL again: return it to a normal value once traffic is stable on the new servers.
- Decommission carefully: after the agreed period, take a final backup of the old servers, securely wipe the disks and update your asset register.
How EthicsComputer can help
Our cloud migration service starts with discovery and a wave plan, builds a secure landing zone first, and moves workloads with validation testing and a rollback plan for every wave. Small migrations typically complete in two to six weeks, while larger estates move in waves over a few months. Depending on your target platform, our AWS consulting or Google Cloud consulting teams design the environment, and your cloud bill stays in your own account.
How many servers and applications are you planning to move?
Share a rough list of what you run today, and we will help you check readiness and plan the waves.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.