Home › Knowledgebase › KB-1253

How to migrate from old server to cloud for small business australia

Summary

This guide helps you troubleshoot and resolve: How to migrate from old server to cloud for small business australia. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Migrate from on-premise server to Microsoft 365 and Azure for Australian small business

Category: Cloud Migration & Modern Workplace

Many small businesses continue to rely on physical on-premise servers for file storage and application hosting, which can lead to increased hardware maintenance costs and potential downtime. This article outlines the process of retiring physical servers and migrating core business functions to Microsoft 365 and Azure cloud environments. It covers the assessment of current hardware costs, including power, cooling, and UPS maintenance, against cloud operational expenses. The goal is to provide business owners with a clear path to eliminate on-site hardware headaches while maintaining data accessibility and security.

Australian context and compliance

Before beginning your migration, review the following Australian-specific considerations to ensure your cloud environment meets local regulatory and connectivity requirements.

Data residency

Select Azure Australia regions such as Australia East (New South Wales) or Australia Southeast (Victoria) when provisioning resources. Keeping data within Australian borders helps support compliance with the Privacy Act 1988 and the Australian Privacy Principles (APPs).

Internet bandwidth

Cloud migration depends on your NBN or business broadband connection. Run a speed test during business hours to confirm upload speeds can handle initial data seeding. Schedule large transfers during off-peak hours to minimise impact on daily operations.

Pre-migration checklist

Complete these prerequisites before moving data or users to the cloud.

  • Run an internet speed test and record upload and download speeds.
  • Verify domain ownership and ensure you have access to your DNS hosting portal.
  • Plan email MX record changes, including lowering TTL values in advance to reduce DNS propagation delays.
  • Assess your on-premises Active Directory environment and determine if you will use Azure AD Connect (Microsoft Entra Connect) for identity synchronisation.
  • Document current file share permissions and folder structures.
  • Review current hardware costs, including power, cooling, and UPS maintenance, to compare against cloud operational expenses.

Step 1: Assess your current server environment

Before moving to the cloud, create a complete inventory of what your physical server currently handles. This prevents critical applications or data from being overlooked during the migration.

  • List all applications hosted on the server.
  • Identify which users access which folders and files.
  • Document total storage capacity and current usage.
  • Note any legacy software that requires a specific operating system version.
  • Review current hardware costs, including power, cooling, and UPS maintenance.

Step 2: Choose your cloud destination

For most Australian small businesses, Microsoft 365 and Azure provide the best combination of productivity tools and infrastructure flexibility.

  • Microsoft 365: Use Exchange Online for email, SharePoint Online for team document libraries, and OneDrive for Business for individual file storage.
  • Azure: Use Azure Virtual Machines or Azure File Share if you need to lift-and-shift specific server-based applications.

Step 3: Plan your data migration

Moving files from a local server to the cloud should be done in phases to minimise disruption to daily operations.

  1. Download and install the SharePoint Migration Tool from the Microsoft Download Centre.
  2. Map existing server folders to SharePoint sites or OneDrive accounts.
  3. Set permissions in the cloud environment to match your current on-premise access levels.
  4. Perform an initial bulk transfer of archival data during off-peak hours.
  5. Schedule a final delta sync to capture changes made since the initial transfer.
  6. Verify data integrity by opening a sample of files from different departments.

Step 4: Migrate user accounts and email

Transitioning email and user identities is often the most visible part of the migration for staff.

  1. Sign in to the Microsoft 365 admin center.
  2. Navigate to Users > Active users > Add a user to create Microsoft 365 user accounts for all employees.
  3. Configure DNS records (MX, SPF, DKIM) to route email to Exchange Online.
  4. Lower your MX record TTL in advance to reduce mail flow disruption during DNS propagation.
  5. Migrate mailboxes, calendars, and contacts from your existing mail server.
  6. Test email sending and receiving internally and externally before decommissioning the old server.

Step 5: Test applications and access

Ensure that your team can actually work in the new environment before you switch off the physical hardware.

  • Confirm that staff can log in using their new cloud credentials.
  • Test access to shared files from office computers, laptops, and mobile devices.
  • Verify that any line-of-business applications run correctly on Azure or via web browsers.
  • Check that printing and scanning workflows still function as expected.

Step 6: Decommission the old server

Once you have verified that all data and applications are functioning in the cloud, you can retire the physical server.

  1. Retain the server in a powered-on state for a defined 30-day rollback period.
  2. Verify that all backups are complete and restorable before proceeding.
  3. Export any remaining configuration settings or logs for record-keeping.
  4. Securely wipe all hard drives to protect sensitive business data.
  5. Arrange for responsible e-waste recycling of the hardware.

Ongoing cloud management

Moving to the cloud removes the need for physical server maintenance, but it introduces new administrative responsibilities.

  • Review Microsoft 365 licensing regularly to ensure you are not paying for unused seats.
  • Enable multi-factor authentication (MFA) for all user accounts.
  • Schedule regular cloud backups in addition to Microsoft's native retention policies.
  • Monitor Azure spending to avoid unexpected operational expenses.

Troubleshooting common migration issues

DNS propagation delays

After updating MX, SPF, or DKIM records, email routing may take several hours to update globally. Lower TTL values before making changes to reduce propagation time.

Mail flow failures

If email is not flowing to Exchange Online, verify that your MX record points to the correct Microsoft 365 endpoint and that SPF/DKIM records are published correctly in your DNS portal.

SharePoint sync errors

If the OneDrive sync client reports errors, check file path lengths and invalid characters in file names. Re-run the SharePoint Migration Tool for failed items and confirm user permissions in the SharePoint admin center.

Permission mismatches

If users cannot access migrated folders, compare SharePoint site permissions against your original on-premises NTFS permissions. Inheritance issues often occur when folder-level permissions were modified directly on the source server.

Tip for small businesses: Consider running the old server and the cloud environment in parallel for two to four weeks. This provides a safety net if any data was missed during the initial migration.
Security warning: Do not decommission your on-premise server until you have confirmed that all critical data has been successfully migrated and tested in the cloud. Data loss can occur if the local hardware is wiped prematurely.

Need assistance with your server-to-cloud migration? 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