Azure Migration Checklist for Small Businesses

Moving to Microsoft Azure is less about the technology than about sequencing. The organizations that struggle usually skipped the inventory, built production workloads in a hurry with no landing zone, or never revisited sizing after cutover. This checklist is the order we recommend for small businesses and nonprofits, and it maps to the process described on our Azure consulting page.

What should you do before migrating to Azure?

Before you move anything, know exactly what you have, why it matters and what it depends on. Discovery and a clear business case prevent most migration failures.

Discovery and assessment checklist

• ☐List every server, virtual machine, application, database and file share, with a business owner for each.
• ☐Deploy the Azure Migrate appliance to collect configuration, performance and dependency data for at least two weeks, ideally including a month-end cycle.
• ☐Record operating system and database versions, and flag anything out of support.
• ☐Note licensing you already own, such as Windows Server and SQL Server with Software Assurance, which may qualify for Azure Hybrid Benefit.
• ☐Document network requirements: site-to-site VPN, public endpoints, DNS and firewall rules.
• ☐Identify compliance needs such as HIPAA, PCI DSS or data residency, and choose an Azure region accordingly.
• ☐Define success criteria, acceptable downtime per application and a target budget.

If you are not yet sure Azure is the right destination, a broader cloud readiness assessment is a good starting point.

How do you prepare the Azure environment?

Build a governed landing zone before the first production workload arrives. Retrofitting identity, networking and policy later is slower and riskier than doing it first.

Landing zone checklist

• ☐Create a management group hierarchy and separate subscriptions for production and non-production.
• ☐Configure Microsoft Entra ID with MFA, Conditional Access and role-based access control (RBAC) using groups, not individual users.
• ☐Design a hub-and-spoke virtual network with a VPN gateway or Azure ExpressRoute connection to your offices.
• ☐Apply Azure Policy for allowed regions, required tags and denied public IPs where appropriate.
• ☐Send activity logs and diagnostics to a Log Analytics workspace.
• ☐Enable Microsoft Defender for Cloud and Azure Backup.
• ☐Set budgets and cost alerts on every subscription.
• ☐Define the environment with Bicep or Terraform so it is repeatable.

Our Azure governance framework covers naming, tagging and policy design in more detail.

Which migration approach should you use for each workload?

Choose per workload, not per project. Most small business migrations mix rehosting for speed with replatforming where a managed service removes real maintenance work.

The full framework is described in our guide to the 7 Rs of cloud migration.

How do you run a safe pilot and migration waves?

Start with one low-risk workload, refine the runbook, then migrate the rest in small, dependency-aware groups. Each wave should be reversible until users sign off.

Pilot checklist

• ☐Choose a workload that is real but not critical, such as an internal web app or a reporting server.
• ☐Replicate it with Azure Migrate server migration and run a test migration into an isolated network.
• ☐Validate application function, authentication, printing, performance and backup.
• ☐Time each cutover step and write it into a runbook with a rollback plan.

Wave migration checklist

• ☐Group servers that talk to each other into the same wave using dependency data.
• ☐Communicate the cutover window and freeze changes on affected systems.
• ☐Run a final replication, shut down the source, and cut over DNS and connections.
• ☐Have application owners test and formally sign off.
• ☐Keep the source system powered off but intact for a defined rollback period.

For large databases or file sets, plan data transfer separately. Our data migration guide covers online replication versus offline options such as Azure Data Box.

What should you do after migrating to Azure?

After cutover, secure, optimize and decommission. The first 30-60 days are when most cost waste and configuration drift can be caught cheaply.

Post-migration checklist

• ☐Confirm backups run and perform a test restore of at least one VM and one database.
• ☐Review Microsoft Defender for Cloud recommendations and remediate high-severity items.
• ☐Set Azure Monitor alerts for CPU, disk, availability and backup failures.
• ☐After the first full billing cycle, right-size VMs using Azure Advisor and actual utilization.
• ☐Buy reservations or savings plans only for workloads with stable, predictable usage.
• ☐Shut down development and test VMs outside business hours.
• ☐Securely wipe and retire on-premises hardware, and update asset and license records.
• ☐Update documentation and train the people who will operate the environment.

See the Azure cost optimization guide for a full cost review process, and post-migration optimization for a cross-cloud view.

Common Azure migration mistakes to avoid

Most problems come from skipping preparation rather than from Azure itself.

• Sizing VMs from on-premises specs. On-premises servers are often heavily over-provisioned. Use performance-based sizing from Azure Migrate instead.
• Forgetting identity. Applications that rely on on-premises Active Directory need domain controllers or Microsoft Entra Domain Services reachable from Azure.
• Ignoring bandwidth. A slow office connection can make replication and post-migration access painful. Test throughput early.
• No rollback plan. Every cutover should have a documented way back.
• Leaving test resources running. Replication and test-migration resources quietly add to the bill.

How Desai InfoTech helps with Azure migrations

Desai InfoTech runs Azure migrations for small businesses and nonprofits using this checklist, starting with an assessment and a pilot so you see real results before committing to the full move. If you want a second opinion on your plan, request a free cloud assessment.