Cloud migration checklist for small businesses

For most small businesses, yes, at least for email, files and line-of-business apps. The cloud removes the need to buy, patch and replace servers. It makes remote work easier and usually improves backup and recovery. But it is not automatically cheaper. You swap a capital cost every few years for an ongoing monthly bill, and that bill grows if nobody watches it.

Some workloads may be better left where they are, at least for now. Old software that only runs on a specific server, or equipment that must stay on site, can be kept and connected to the cloud later. A good migration plan is honest about this.

Before touching any system, gather the basics. Use this checklist as your preparation stage.

Follow these steps in order. Tick each one off before moving to the next.

1. Set clear goals. Write down why you are migrating: retiring an ageing server, enabling remote work, improving backup, or cutting maintenance time. Goals help you decide what "done" looks like.
2. Complete the inventory. Fill in the table above. Talk to each team, because shadow IT, such as a spreadsheet on someone's desktop that runs payroll, is common.
3. Choose a strategy for each workload. Use the common migration options below. Most small businesses use a mix.
4. Pick a provider and region. Choose based on the tools you already use, your team's skills and where your data needs to sit. Choose a region close to your users and compliant with any residency rules.
5. Set up identity and security first. Before moving any data, turn on multi-factor authentication (MFA) for all admin and user accounts, remove unused accounts, and give people the least access they need.
6. Configure backups. Cloud does not mean backed up. Set up backups for cloud data, and keep at least one copy separate from your main account.
7. Set budgets and alerts. Create spending alerts before resources start running. In AWS, this is under Billing and Cost Management, then Budgets. In Microsoft Azure, use Cost Management + Billing, then Budgets. Google Cloud has budgets and alerts under Billing.
8. Run a pilot. Move one low-risk workload first, such as a file share for one team. Check performance, access and backups, and note what went wrong.
9. Plan the cutover. Pick a quiet period. Tell staff what will change and when. If DNS records will change, lower their TTL (time to live) a day or two before, so changes take effect quickly.
10. Migrate in batches. Move workloads in small groups. Verify each batch: files open, apps work, permissions are correct and integrations still connect.
11. Keep a rollback option. Do not wipe old systems straight away. Keep them read-only for an agreed period in case you need to roll back.
12. Decommission and tidy up. Once stable, securely wipe old servers, cancel unused licences and update your documentation.
13. Review costs after the first month. Compare the bill with your estimate. Resize or switch off anything that is oversized or idle.

Cloud providers describe several standard approaches, often called the "Rs" of migration. You do not need all of them, but it helps to label each workload.

• Rehost (lift and shift): move a server as it is to a cloud virtual machine. Fast, but you keep the old app's limitations.
• Replatform: make small changes, such as moving a database to a managed database service. A good balance for many small businesses.
• Refactor: rebuild the app to use cloud-native services. Gives the most benefit but takes the most time.
• Repurchase: replace the app with a software-as-a-service product, such as moving an on-site mail server to Microsoft 365 or Google Workspace.
• Retain: keep it where it is for now.
• Retire: switch it off because nobody needs it.

For small businesses, "repurchase" is often the biggest win. Email, file storage, accounting and CRM are usually better as SaaS than as servers you manage. If email and files are your starting point, our Microsoft 365 setup service covers that route.

Data transfer is where most delays happen. Plan for it.

• Clean first. Delete duplicates and archive old files. Less data means a faster, cheaper move.
• Check bandwidth. Large volumes over a slow office connection can take days. Run an initial sync early and a final "delta" sync at cutover.
• Use official tools. Providers offer migration tools for file shares, mailboxes and databases. They handle retries and permissions better than manual copying.
• Encrypt in transit and at rest. Major cloud providers encrypt stored data by default, but confirm the setting and use secure connections for transfer.
• Verify. Compare file counts and spot-check important records after each batch.

• No inventory. A forgotten app or scheduled task breaks after cutover.
• Oversized resources. Copying on-site server specs into the cloud usually means paying for capacity you do not use.
• Security as an afterthought. Public storage buckets and admin accounts without MFA are common causes of breaches.
• Skipping training. Staff who do not know where files now live will save them locally again.
• No owner. Someone must own the cloud account, the bill and the access reviews after the project ends.

Our cybersecurity service covers the controls to put in place alongside a migration.

It depends on the number of systems, the amount of data and how much needs to change. Moving email and files for a small team can take a few weeks including planning and training. Migrating several business apps, databases and integrations can take a few months. Refactoring custom software takes longer still. The main cost drivers are data volume, the number of integrations, licence changes and how much testing is needed.

Treat the first three months as a settling-in period.

1. Review access monthly and remove leavers promptly.
2. Test restoring from backup at least once, not just that backups run.
3. Check cost reports and switch off idle resources.
4. Apply updates to any virtual machines you still manage.
5. Document the new setup so someone else could support it.

We plan and run cloud migrations for small teams, from the first inventory to post-move cost reviews, and we can stay on for ongoing support if you need it. See our cloud migration service or contact us to talk through your current setup.