Home › Knowledgebase › KB-1248

How to move from on-premise servers to the cloud for small business

Summary

This guide helps you troubleshoot and resolve: How to move from on-premise servers to the cloud for small business. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

How to move from on-premise servers to the cloud for small business

Many small businesses continue to operate physical servers in office cupboards or corner racks. This approach incurs ongoing costs for electricity, cooling, UPS battery replacement, and hardware warranties. This article outlines the process of retiring physical servers by migrating files, identity, and applications to Microsoft 365 and Azure cloud tiers.

Prerequisites

Before beginning your migration, ensure you have the following in place:

  • Admin roles: Global Administrator in Microsoft Entra ID and Exchange Administrator in the Microsoft 365 admin center.
  • Licensing: Microsoft 365 Business Premium or Microsoft 365 E3 licenses assigned to all migrating users.
  • Bandwidth: Calculate your total data volume and divide by your available upload speed. We recommend a minimum of 50 Mbps upload for small business file migrations.
  • Tools: Download the SharePoint Migration Tool from the Microsoft Download Center and install it on a domain-joined workstation with access to your file shares.
  • Identity: Download Microsoft Entra Connect (formerly Azure AD Connect) from the Microsoft Entra admin center if you plan to synchronize on-premise Active Directory.

Why move away from on-premise servers

Maintaining physical hardware on-site creates several challenges for small businesses:

  • Upfront capital expenditure for server hardware and software licenses
  • Ongoing electricity and cooling costs
  • UPS battery replacement and hardware warranty renewals
  • Risk of hardware failure causing unplanned downtime
  • Limited remote access for staff working from home or on the road
  • Manual backup management and offsite storage requirements

Moving to Microsoft 365 and Azure shifts these costs to a predictable monthly operational expense while improving security, reliability, and accessibility.

Total cost of ownership comparison

When comparing on-premise servers to cloud infrastructure, consider the full five-year total cost of ownership:

Cost factor On-premise server Microsoft 365 and Azure
Hardware purchase Upfront capital cost Included in subscription
Electricity and cooling Ongoing office expense None
UPS and battery maintenance Periodic replacement required None
Hardware warranty and support Annual renewal fees Included
Software licenses Upfront and upgrade costs Monthly per-user fee
Backup and disaster recovery Manual and offsite storage Built-in cloud redundancy

Warnings and compliance considerations

Internet dependency: Cloud services require a reliable business-grade internet connection. If your office internet fails, staff will lose access to files, email, and hosted applications. We recommend a secondary connection or 4G/5G failover for Brisbane-based small businesses.
Data sovereignty and the Australian Privacy Act: Ensure your Microsoft 365 tenant data residency is set to Australia. Under the Australian Privacy Act 1988 (APPs), you remain responsible for how personal information is stored, accessed, and protected. Review Microsoft's compliance documentation and confirm where your data is physically hosted before migrating sensitive customer records.
Application compatibility: Not all line-of-business applications run natively in the cloud. Test legacy software on Azure virtual machines or Azure App Service before decommissioning your on-premise server. Some applications may require code changes, updated database drivers, or continued on-premise hosting.

Step 1: Audit your current environment

Before migrating, document what is running on your on-premise server:

  1. Open File Server Resource Manager on your on-premise server and generate a storage report to list all file shares and total data volume.
  2. List all line-of-business applications and verify whether cloud equivalents exist or if they must be hosted on Azure virtual machines.
  3. Open Active Directory Users and Computers, export all user accounts, groups, and nested group memberships, and document current NTFS permissions on file shares.
  4. Log in to your DNS registrar or hosting control panel and record existing MX, CNAME, TXT, and SPF records for email hosting.
  5. Run a speed test from your office during peak hours to assess upload and download speeds for cloud workloads.

Step 2: Plan identity and access

Move user identities to Microsoft Entra ID (formerly Azure Active Directory) so staff can sign in to cloud services with a single set of credentials:

  1. Sign in to the Microsoft 365 admin center at https://admin.microsoft.com as a Global Administrator and create or verify your tenant.
  2. Navigate to Settings > Domains > Add domain, enter your business domain name, and complete the TXT record verification step.
  3. Go to Users > Active users > Add a user, create accounts for all staff, and assign Microsoft 365 Business Premium or E3 licenses.
  4. Navigate to Users > Active users > Multi-factor authentication and enable MFA for every user account.
  5. Decide whether to synchronize on-premise Active Directory or create cloud-only identities. For hybrid identity, install Microsoft Entra Connect:
    1. Download Microsoft Entra Connect from the Microsoft Entra admin center at https://entra.microsoft.com.
    2. Run the installer and select Express settings.
    3. Enter your Enterprise Administrator credentials for the on-premise Active Directory forest.
    4. Enter your Global Administrator credentials for Microsoft Entra ID.
    5. Select Password hash synchronization as the sign-in method and complete the configuration.

Step 3: Migrate files to SharePoint and OneDrive

Replace on-premise file servers with cloud storage:

  1. Open the SharePoint admin center at https://admin.microsoft.com/sharepoint, navigate to Active sites, and create team sites that match your existing departmental folder structure.
  2. Run the SharePoint Migration Tool, select File share > OneDrive or SharePoint, map your on-premise source paths to destination URLs, and schedule the transfer.
  3. Before migration, delete redundant, obsolete, or trivial data to reduce transfer time and storage costs.
  4. In SharePoint, navigate to the target site, select Settings > Site permissions, and assign access groups that match previous NTFS permission levels.
  5. Train staff on accessing files through the SharePoint web interface, OneDrive sync client, or mobile apps.

Step 4: Migrate email and collaboration

Move email, calendars, and contacts to Microsoft 365:

  1. In the Microsoft 365 admin center, navigate to Users > Active users, select each user, and assign an Exchange Online license under Licenses and apps.
  2. Navigate to Setup > Email migration, choose cutover, staged, or hybrid migration based on your mailbox count, and follow the wizard to migrate existing email data.
  3. Log in to your DNS provider and update the MX record to point to yourdomain-com.mail.protection.outlook.com, then add the required SPF, DKIM, and DMARC TXT records.
  4. In the Exchange admin center at https://admin.exchange.microsoft.com, configure email signatures, retention policies, and spam filtering rules.
  5. Assign Microsoft Teams licenses and roll out Teams for chat and meetings.

Step 5: Move applications to Azure

For applications that cannot be replaced by SaaS alternatives, consider hosting them in Azure:

  • Sign in to the Azure portal at https://portal.azure.com and assess whether the application is suitable for an Azure virtual machine or Azure App Service.
  • Navigate to Virtual networks > Create, set up an Azure virtual network, and configure a site-to-site VPN or ExpressRoute connection to your office.
  • Migrate databases to Azure SQL Database or deploy them on an Azure virtual machine.
  • Test application performance, user access, and backup schedules in Azure before cutting over production users.

Step 6: Disaster recovery testing

Before decommissioning any hardware, validate that your cloud environment can survive a failure:

  1. Perform a test restore of critical files from SharePoint and OneDrive version history or a third-party backup solution.
  2. Simulate an internet outage and confirm staff can access cloud resources via a secondary connection or mobile hotspot.
  3. Restore an application database from Azure Backup to a separate test virtual machine and verify data integrity.
  4. Document recovery time objectives (RTO) and recovery point objectives (RPO) for each workload.

Step 7: Decommission the on-premise server

Once all workloads are verified in the cloud and disaster recovery testing is complete:

  1. Run a final synchronization of any remaining data using the SharePoint Migration Tool or Entra Connect delta sync.
  2. Confirm that cloud backups are configured and recent restore points exist.
  3. Power down the physical server and keep it offline for a short retention period.
  4. Securely wipe or destroy hard drives before disposal or return to vendor.
  5. Cancel maintenance contracts, warranties, and colocation services if applicable.

Troubleshooting common migration issues

Use the following guidance if you encounter problems during migration:

Failed migration: If the SharePoint Migration Tool fails, check the log files in the installation directory, verify network connectivity to *.sharepoint.com, and ensure the source account has Read permissions on the on-premise folders. Restart the migration from the last successful checkpoint rather than re-transferring all data.
Slow transfers: Throttle the SharePoint Migration Tool during business hours to avoid saturating your office internet, or schedule large transfers overnight. If speeds remain slow, contact your ISP to confirm upload speeds and consider upgrading to a business fiber plan.
Permission issues: After migration, verify that NTFS permissions mapped correctly to SharePoint site groups. In the SharePoint admin center, go to Active sites > [site name] > Permissions and compare access levels against your original audit. Reassign any missing groups manually.
Rollback procedures: If a critical application fails in Azure, keep the on-premise server powered on (but disconnected from users) for at least 14 days. To roll back, reconfigure DNS records to point to the on-premise IP address, restore the most recent local backup, and notify staff of the temporary return to on-premise access.

Minimizing downtime and disruption

A phased migration approach allows staff to continue working while workloads move incrementally. Email and file migrations can often be completed outside business hours, and user training can begin before the cutover date. This reduces the impact on daily operations for Brisbane-based small businesses.

Need help with your migration? If you require assistance planning or executing your move to the cloud, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket