How to move business data to microsoft 365 australia
Summary
This guide helps you troubleshoot and resolve: How to move business data to microsoft 365 australia. Follow the steps below to fix the issue.
Common Causes
How to move business data to Microsoft 365 in Australia
Many small businesses continue to rely on physical servers housed in an office cupboard or corner rack to store company files and manage user access. While these devices have traditionally served as central hubs, they introduce significant ongoing costs and operational risks, including hardware failure, power outages, and the need for manual maintenance. Moving your business data to Microsoft 365 and Azure allows you to retire that hardware, reduce IT overhead, and improve business continuity across your organisation.
Total Cost of Ownership: On-Premises Server vs Microsoft 365
Before beginning the migration, it is helpful to analyse the total cost of ownership of your current physical server. Many businesses focus only on the initial purchase price, but ongoing expenses often exceed the cost of a cloud subscription.
Typical On-Premises Server Running Costs (AUD)
- Electricity to power the server 24 hours a day, 7 days a week: approximately $300–$600 per year
- Air conditioning or ventilation to prevent overheating in a small office space: approximately $200–$400 per year
- Uninterruptible Power Supply (UPS) units and replacement batteries: approximately $150–$300 every 3–5 years
- Hardware replacement parts such as hard drives, power supplies, and cooling fans: approximately $200–$500 per year
- Warranty renewals and extended support contracts: approximately $500–$1,000 per year
- Physical security and office space dedicated to the server rack: variable
For comparison, Microsoft 365 Business Basic and Business Standard licences are billed monthly in AUD. Microsoft manages the underlying hardware, power, cooling, and security in Australian-based data centres, shifting your costs from unpredictable capital expenditure to a predictable operational subscription.
Australian Context for Cloud Migration
Data Residency and Privacy Obligations
Microsoft 365 customer data for Australian tenants can be stored in Australian data centre regions, including Sydney, Melbourne, and Canberra. This helps small businesses meet obligations under the Australian Privacy Act and the Australian Privacy Principles (APPs) by keeping personal information within Australia where required. Before migrating, review the types of data your business holds and confirm that the selected Microsoft 365 geography aligns with your privacy and compliance requirements.
NBN Upload Bandwidth Considerations
Because your files will move from a local network to the cloud, your NBN upload speed affects how quickly the initial migration completes. Many Australian small business NBN plans have asymmetrical speeds, meaning upload is significantly slower than download. Test your connection before starting and schedule large data transfers outside of peak business hours to avoid disrupting daily operations.
Planning Your Migration
A successful move from an on-premises server to the cloud requires careful preparation. Rushing the process can lead to data loss, extended downtime, or user access issues.
1. Audit Your Current Data
- Identify all folders and files stored on your physical server.
- Determine which data is actively used and which can be archived or deleted.
- Note current file permissions and who needs access to each folder.
- Document any applications that rely on the server for data storage or authentication.
- Check whether your server also hosts email (Exchange on-premises), as this will require a separate migration path.
2. Choose the Right Microsoft 365 Plan
Select a plan that includes OneDrive for Business and SharePoint Online. These services replace the file server by providing central cloud storage with granular permission controls. Microsoft Entra ID (formerly Azure Active Directory) handles user identity and access management, replacing the need for an on-premises domain controller.
3. Prepare Your Network and Domain
Ensure your business has a reliable internet connection with sufficient upload bandwidth. If you use a custom email domain such as yourbusiness.com.au, you will need to verify ownership in Microsoft 365 and update DNS records, including MX records, to route email to Exchange Online.
Setting Up Your Microsoft 365 Tenant
- Sign up for a Microsoft 365 business subscription and create your tenant.
- In the Microsoft 365 admin centre, go to Settings > Domains and select Add domain.
- Enter your .com.au domain and follow the prompts to verify ownership by adding a DNS TXT or MX record with your domain registrar.
- Once verified, update your MX records to point to Exchange Online if you are migrating email.
- Go to Users > Active users > Add a user and enter the details for each employee.
- Assign appropriate Microsoft 365 licences to each user.
- Communicate new sign-in credentials to your staff.
Tip: If you already have an on-premises Active Directory, you can use Microsoft Entra Connect to synchronise identities to the cloud. This allows users to keep their existing passwords and simplifies the transition.
Migrating Files to Microsoft 365
There are several methods to move your data, depending on the volume of files and your technical comfort level.
Option A: Manual Migration for Small Amounts of Data
- Sign in to Office.com with your Microsoft 365 administrator account.
- Open SharePoint or OneDrive from the app launcher.
- In SharePoint, create a document library or folder structure that mirrors your existing server shares.
- Open File Explorer on a computer connected to the on-premises server.
- Select the files and folders you want to migrate.
- Drag and drop them into the SharePoint library or OneDrive folder in your web browser.
- Verify that all files uploaded successfully before decommissioning the server.
Option B: Using the SharePoint Migration Tool
For larger volumes of data, Microsoft provides the SharePoint Migration Tool (SPMT), a free utility designed to move file shares to SharePoint and OneDrive.
- Download the SharePoint Migration Tool from the Microsoft Download Centre.
- Install the tool on a Windows computer with access to your on-premises server.
- Launch the tool and sign in with your Microsoft 365 global administrator credentials.
- Select File share as the source.
- Enter the network path to your server folders, for example
\\ServerName\SharedFolder. - Select the destination in SharePoint Online or OneDrive for Business.
- Map the source folders to the appropriate destination libraries.
- Start the migration and monitor progress in the tool dashboard.
- Review the migration report for any failed items and retry as needed.
File Size Limits and Throttling
Be aware of OneDrive for Business and SharePoint Online file size limits before migrating. Very large files may fail to upload, and Microsoft may apply migration throttling if you transfer a high volume of data in a short period. Break large migrations into smaller batches and avoid uploading files that exceed the supported size limit.
Migrating Email from Exchange On-Premises
If your physical server also hosted Microsoft Exchange for business email, you will need to migrate mailboxes to Exchange Online. This process typically involves:
- Verifying your .com.au domain in the Microsoft 365 admin centre.
- Creating mailboxes for each user in Exchange Online.
- Using a cutover, staged, or hybrid migration method depending on the number of mailboxes.
- Updating DNS MX records to point to Exchange Online so new email is delivered to the cloud.
- Testing email flow before decommissioning the on-premises Exchange server.
Troubleshooting Common Migration Issues
Failed Items
Review the SharePoint Migration Tool report for any files that did not transfer. Common causes include insufficient permissions, files open in another application, or network interruptions during transfer. Retry failed items after resolving the underlying issue.
Permission Errors
Ensure the account running the migration has read access to the source folders and appropriate contributor or owner permissions in the destination SharePoint site or OneDrive account.
Long Paths and Special Characters
Windows file paths that are excessively long, or file names containing special characters, may cause migration failures. Shorten folder paths where possible and rename files to remove unsupported characters before retrying the migration.
Sync Conflicts
If users edit files on the server while migration is in progress, sync conflicts can occur. Communicate a cutover date to staff and discourage changes to source data during the final migration window.
Retiring the Physical Server
Once your data, identity, and applications have moved to Microsoft 365 and Azure, you can decommission the on-premises server. Do not power it down until you have verified that all users can access their files and applications in the cloud.
Decommissioning Checklist
- Confirm that all critical data has been migrated and validated.
- Ensure user accounts are active in Microsoft 365.
- Export any remaining configuration settings or legacy application data.
- Retain the physical server for at least 30 days post-migration as a rollback option.
- Securely wipe the server hard drives before disposal or recycling.
- Cancel any maintenance contracts, warranty renewals, or colocation fees associated with the hardware.
- Update your IT documentation to reflect the cloud environment.
Warning: Do not delete data from the physical server until you have completed at least one full backup of the migrated cloud data and confirmed user access.
Benefits of Removing the Office Server
Retiring your physical server provides several immediate advantages for a small business or home office:
- No more hardware failure risks or unexpected replacement costs
- Reduced power and air conditioning expenses
- No UPS battery replacements or warranty renewals
- Improved business continuity, as data is stored in geographically redundant Australian data centres
- Employees can access files securely from anywhere, supporting remote and hybrid work
- Automatic security updates and threat protection managed by Microsoft
Moving from a physical server to Microsoft 365 and Azure is a significant step, but it removes many of the hidden costs and risks associated with on-premises hardware. If you need assistance planning your migration or want help transferring your business data, Open a Ticket.
Still Having Issues?
💻 Open a Ticket