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.
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:
- Uninterruptible Power Supply (UPS) units and regular battery replacement
- Replacement parts such as hard drives, power supplies, and fans
- Hardware warranty renewals and extended support contracts
- Physical security, including locked cabinets and access control
- Electricity to run the server 24 hours a day, 7 days a week
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:
- File storage: Shared folders and department drives move to Microsoft OneDrive and SharePoint document libraries.
- Identity and sign-in: Local user accounts move to Microsoft Entra ID (formerly Azure Active Directory), allowing staff to sign in with one set of credentials across devices.
- Applications: Email, calendars, and collaboration tools move to Microsoft 365, while custom or legacy line-of-business applications can be hosted on Azure Virtual Machines or migrated to SaaS equivalents.
Australian context and data residency
When moving your server to the cloud, consider where your data is stored and how it is accessed:
- Data residency: Microsoft Azure offers Australian regions including Australia East and Australia Southeast. Storing data in these regions can help your organisation meet Australian Privacy Act and Australian Privacy Principles (APP) obligations.
- NBN and business broadband: Cloud access depends on stable internet. Confirm your NBN tier or business broadband plan provides sufficient upload speed for initial data synchronisation and ongoing daily use.
- Small business constraints: If you have limited IT staff, prioritise Microsoft 365 services that reduce ongoing management, such as Exchange Online, SharePoint, OneDrive, and Microsoft Entra ID.
Pre-migration checklist
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- Go to
admin.microsoft.comand sign in with your administrator account. - Add your organisation's domain and verify DNS ownership.
- Create user accounts in the Microsoft 365 admin centre under Users > Active users.
- Assign licences that include Microsoft Entra ID and the required Office applications.
- Configure multi-factor authentication (MFA) for every account in the Microsoft Entra admin centre at
entra.microsoft.com. - 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
- Create SharePoint team sites for departments and OneDrive locations for individual users.
- 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.
- Verify permissions and folder structures after the transfer completes.
- Retire the old file shares once staff confirm they can access everything they need.
Step 3: Move applications to Azure or Microsoft 365
- Identify applications that can be replaced with Microsoft 365 services, such as moving email to Exchange Online.
- For applications that must remain on a server, sign in to the Azure portal at
portal.azure.comand provision an Azure Virtual Machine sized appropriately for the workload. Select an Australian region such as Australia East or Australia Southeast. - Install and configure the application on the Azure VM, then test connectivity from office and remote devices.
- Set up Azure Backup or Azure Site Recovery to protect the virtual machine.
After the migration
- Decommission the physical server by powering it down securely and arranging responsible e-waste recycling.
- Cancel any remaining hardware warranties, UPS maintenance contracts, and on-site backup subscriptions.
- Train staff on saving files to OneDrive and SharePoint rather than local desktop folders.
- Review cloud usage and costs monthly to ensure you are on the correct licence tier.
Troubleshooting common migration issues
Slow upload speeds
- Schedule large transfers outside business hours to reduce contention with staff internet use.
- Contact your internet service provider to confirm your NBN or business broadband plan supports the required upload speed.
- Pause non-essential cloud backups or streaming services during the migration window.
Permission errors
- Compare source folder permissions with destination SharePoint or OneDrive permissions after migration.
- Use the SharePoint Migration Tool reports to identify files that failed due to access rights.
- Adjust sharing settings in the SharePoint admin centre at
admin.microsoft.comunder SharePoint > Policies > Sharing.
MFA lockouts
- Ensure users have registered a phone number or authenticator app before enforcing MFA.
- If a user is locked out, an administrator can reset MFA methods in the Microsoft Entra admin centre under Users > All users > Authentication methods.
- Verify that conditional access policies are not inadvertently blocking sign-ins from office IP addresses.
Legacy application UNC path dependencies
- Identify applications that reference local paths such as \\Server\Share before migration.
- Update application configuration files and desktop shortcuts to point to Azure Files, SharePoint, or the Azure VM.
- Test the application from a non-administrator user profile to confirm access works after drive mappings are changed.
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?
💻 Open a Ticket