Home › Knowledgebase › KB-1293

How to move server to cloud australia

Summary

This guide helps you troubleshoot and resolve: How to move server to cloud australia. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Why consider moving away from a physical server

Keeping a server on-site involves more than the initial purchase price. Ongoing costs typically include:

When a component fails outside of business hours, your staff lose access to files and line-of-business applications until someone can attend site. Cloud migration shifts infrastructure responsibility to the service provider, reducing your day-to-day IT burden and improving reliability for staff working from home, the office, or while travelling around Australia.

What moves to the cloud

A typical server migration for a small business involves three main areas:

Australian context and data residency

When moving your server to the cloud, consider where your data is stored and how it is accessed:

Pre-migration checklist

  1. Audit your current environment: List every application and service running on your physical server. Identify actively used folders and files, and decide what can be archived. Record user accounts and devices that need cloud identities.
  2. Evaluate migration scope: Determine whether a full cloud migration is appropriate or whether a hybrid approach is needed for legacy applications with hardcoded server paths or UNC dependencies.
  3. Check internet bandwidth: Run a speed test during business hours. For small business migrations, a minimum recommended upload speed of 10 Mbps is advised for initial bulk transfers; higher speeds will significantly reduce migration time.
  4. Plan DNS and email changes: If moving email to Exchange Online, document existing DNS and MX records. Schedule the MX record cutover outside business hours to minimise email downtime. Communicate the cutover window to all staff.
  5. Map legacy application dependencies: Identify line-of-business apps that reference local server paths (for example, \\Server\Share). Plan to update shortcuts, drive mappings, and application configuration files before cutover.
  6. Schedule bulk data transfer: Perform large file migrations outside of business hours. Initial synchronisation can take several days depending on your upload speed and data volume.

Step-by-step migration

Step 1: Set up Microsoft 365 and Azure

  1. Go to admin.microsoft.com and sign in with your administrator account.
  2. Add your organisation's domain and verify DNS ownership.
  3. Create user accounts in the Microsoft 365 admin centre under Users > Active users.
  4. Assign licences that include Microsoft Entra ID and the required Office applications.
  5. Configure multi-factor authentication (MFA) for every account in the Microsoft Entra admin centre at entra.microsoft.com.
  6. Join Windows devices to Microsoft Entra ID, or hybrid join them if you still maintain some local resources.

Step 2: Migrate files to SharePoint and OneDrive

  1. Create SharePoint team sites for departments and OneDrive locations for individual users.
  2. Download and run the SharePoint Migration Tool or use a third-party migration utility to copy data from your on-premises server to the cloud.
  3. Verify permissions and folder structures after the transfer completes.
  4. Retire the old file shares once staff confirm they can access everything they need.
Schedule the bulk data transfer outside of business hours to avoid slowing down daily operations. Large file migrations can take several days depending on your upload speed.

Step 3: Move applications to Azure or Microsoft 365

  1. Identify applications that can be replaced with Microsoft 365 services, such as moving email to Exchange Online.
  2. For applications that must remain on a server, sign in to the Azure portal at portal.azure.com and provision an Azure Virtual Machine sized appropriately for the workload. Select an Australian region such as Australia East or Australia Southeast.
  3. Install and configure the application on the Azure VM, then test connectivity from office and remote devices.
  4. Set up Azure Backup or Azure Site Recovery to protect the virtual machine.
Do not disconnect or wipe your physical server until you have completed at least one full backup of all data and verified that users can access critical files and applications from the cloud.

After the migration

  1. Decommission the physical server by powering it down securely and arranging responsible e-waste recycling.
  2. Cancel any remaining hardware warranties, UPS maintenance contracts, and on-site backup subscriptions.
  3. Train staff on saving files to OneDrive and SharePoint rather than local desktop folders.
  4. Review cloud usage and costs monthly to ensure you are on the correct licence tier.

Troubleshooting common migration issues

Slow upload speeds

Permission errors

MFA lockouts

Legacy application UNC path dependencies

Moving from an office server to Microsoft 365 and Azure removes the hidden costs of on-premises hardware and gives your team reliable access to their work from anywhere in Australia. If you need assistance planning or executing your migration, Open a Ticket and our team will help you get started.

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