How to move my small business server to the cloud
Summary
This guide helps you troubleshoot and resolve: How to move my small business server to the cloud. Follow the steps below to fix the issue.
Common Causes
How to move my small business server to the cloud
Category: Cloud Migration & Modern Workplace
Many Australian small businesses still rely on a physical server located in an office cupboard or a corner rack to store files and manage network access. While these systems may have served the business well for years, they introduce significant operational costs and risks. Common overheads include continuous power consumption, cooling requirements, Uninterruptible Power Supply (UPS) battery replacement, hardware warranty renewals, and the risk of a single point of failure.
Migrating your server workloads to Microsoft 365 and Azure cloud services allows you to retire your physical hardware, reduce maintenance overhead, and enable your team to work from anywhere with a secure internet connection.
Assessing your current environment
Before beginning the migration, you must understand exactly what your on-premises server is doing. Most small business servers handle one or more of the following:
- File storage and shared folders for staff
- User account management and network logins
- Line-of-business applications, such as accounting or practice management software
- Printer management and local network services
- Domain controller services for the local network
Create an inventory of all data stored on the server, identify which applications are critical to daily operations, and document current user permissions. This inventory will guide your migration plan and help you determine the appropriate cloud licensing.
Planning the migration
A successful cloud migration requires a structured plan to minimise disruption to your business. Follow these steps during the planning phase:
- Audit your data: Identify redundant, obsolete, or trivial files that do not need to be migrated. This reduces storage costs and migration time.
- Review application compatibility: Determine if your line-of-business applications have cloud versions or can be hosted on Azure Virtual Machines.
- Evaluate internet connectivity: Confirm your business has a reliable business-grade internet connection with sufficient upload speed to support cloud access and initial data sync.
- Establish a timeline: Schedule the migration outside of peak business hours to avoid impacting staff productivity.
- Communicate with staff: Inform employees about the migration date, expected changes to how they access files, and any temporary downtime.
Migrating file storage to Microsoft 365
File servers are typically replaced by a combination of OneDrive and SharePoint within Microsoft 365. OneDrive is ideal for personal file storage, while SharePoint provides team sites and shared document libraries that replicate traditional shared folders.
Steps to migrate your files
- Go to the Microsoft 365 admin centre
https://admin.microsoft.com, sign in with your Global Administrator account, and select Billing from the left-hand menu. Click Purchase services, select the appropriate Microsoft 365 plan for your users, and complete the checkout process to provision licences. - In the Microsoft 365 admin centre, go to Users > Active users. Click Add a user, enter the user details, assign the appropriate product licence, and click Finish adding user.
- Go to the SharePoint admin centre
https://admin.microsoft.com/sharepoint. In the left navigation, select Active sites and click Create. Enter a site name and description that mirrors your existing departmental folders, set the privacy settings, and click Finish. - Download and install the SharePoint Migration Tool from the Microsoft Download Centre. Launch the tool, select File share as the source, enter the path to your on-premises server folder, select SharePoint or OneDrive as the destination, and click Add followed by Migrate.
- Once migration completes, open the destination SharePoint library or OneDrive folder in a web browser. Verify that folder structures, file names, and NTFS permissions have transferred correctly.
- Install the OneDrive sync client on staff workstations. Instruct users to sign in with their Microsoft 365 credentials and select the folders they wish to sync locally.
Moving user identity to the cloud
If your server currently manages user accounts through Active Directory, you can transition to Microsoft Entra ID (formerly Azure Active Directory). This allows staff to sign in to devices and cloud services using a single set of credentials.
Creating cloud-only user accounts
- Go to the Microsoft 365 admin centre
https://admin.microsoft.com. - Navigate to Users > Active users.
- Click Add a user.
- Enter the user's name, username, and domain.
- Assign a product licence and select the appropriate role.
- Click Finish adding user and provide the temporary password to the user.
Synchronising on-premises Active Directory with Microsoft Entra Connect
- Download Microsoft Entra Connect from the Microsoft Download Centre.
- Run the installer on a domain-joined server with network access to your on-premises Active Directory.
- Select Express settings for a standard password hash synchronisation deployment.
- Enter your Enterprise Administrator credentials for the on-premises Active Directory forest.
- Enter your Global Administrator credentials for your Microsoft 365 tenant.
- Click Install to begin synchronising identities to Microsoft Entra ID.
Email and DNS considerations
If your on-premises server also handles email services, you must plan your DNS migration carefully to avoid mail flow interruptions.
- MX records: Update your public DNS MX records to point to Microsoft 365 Exchange Online. Typical values are provided in the Microsoft 365 admin centre under Settings > Domains > [your domain] > DNS records.
- Autodiscover: Create an Autodiscover CNAME record in your public DNS pointing to
autodiscover.outlook.comso that Outlook clients can automatically locate mailbox settings. - SPF, DKIM, and DMARC: Configure these DNS records to help prevent email spoofing and improve deliverability for your domain.
- Mailbox migration: Use the Exchange admin centre
https://admin.exchange.microsoft.comto create migration batches for moving mailboxes from an on-premises Exchange server to Exchange Online.
Migrating line-of-business applications
Many small businesses run specialised software on their local server. You have two primary options for moving these applications to the cloud:
- Cloud-native alternatives: Check if your software vendor offers a Software as a Service (SaaS) version that runs in a browser.
- Azure Virtual Machines: If no cloud version exists, you can migrate the application server to an Azure VM. This replicates your existing server environment in Microsoft's data centres without requiring changes to the application itself.
Provisioning an Azure Virtual Machine
- Sign in to the Azure portal
https://portal.azure.com. - Click Create a resource, search for Windows Server, and select the appropriate image.
- Click Create and configure the VM settings, including resource group, VM size, administrator username, and authentication type.
- Under Networking, configure the virtual network and inbound port rules required for your application.
- Review and click Create to deploy the virtual machine.
Ensure you test application performance and data access thoroughly before decommissioning your physical server.
Testing and cutover
Before retiring your on-premises server, conduct a parallel run where both the cloud environment and the physical server remain operational. Ask a small group of staff to perform their daily tasks using the new cloud setup.
Once you are confident that all data, permissions, and applications are working correctly, schedule a final synchronisation of any remaining data changes. Update DNS records and network settings as needed, then direct all users to the cloud environment.
Troubleshooting common migration issues
Permission migration errors
If files appear in SharePoint or OneDrive but users cannot access them, verify that NTFS permissions were mapped correctly during migration. The SharePoint Migration Tool does not always translate complex on-premises ACLs to SharePoint permission levels. You may need to manually reassign permissions in the SharePoint library by selecting Manage access from the library toolbar.
OneDrive sync conflicts
Sync conflicts occur when the same file is edited in two locations before synchronisation completes. Instruct staff to check the OneDrive sync client status icon in the Windows system tray. Right-click the OneDrive icon and select View sync issues to resolve conflicting copies manually.
Azure VM connectivity
If you cannot connect to an Azure Virtual Machine via Remote Desktop, check the following:
- Ensure the VM is in a Running state in the Azure portal.
- Verify that port 3389 is open in the Network Security Group (NSG) associated with the VM's network interface.
- Confirm that the public IP address is correctly assigned and not blocked by your office firewall.
Retiring your physical server
After confirming that the cloud environment is fully functional, you can power down and remove your physical server. Arrange for secure disposal of hard drives to protect sensitive business data. Remember to cancel any associated maintenance contracts, UPS service agreements, and hardware warranties to avoid unnecessary ongoing costs.
Moving your small business server to the cloud removes the burden of hardware maintenance, reduces power and cooling costs, and gives your team flexible access to business data. If you need assistance planning or executing your migration, Open a Ticket.
Still Having Issues?
💻 Open a Ticket