Retiring Your Office Server: How to Eliminate Hardware Headaches and Move to the Cloud
Summary
This guide helps you troubleshoot and resolve: Retiring Your Office Server: How to Eliminate Hardware Headaches and Move to the Cloud. Follow the steps below to fix the issue.
Common Causes
Retiring an on-premises office server removes the burden of hardware maintenance, power costs, and physical security risks. By migrating your files and applications to Microsoft 365 and Azure, your organisation gains secure access to data from any location while reducing the risk of local hardware failure. This guide is written for small business owners with limited internal IT resources and addresses NBN bandwidth considerations when moving from an office server to the cloud.
Pre-Migration Checklist
Before beginning the migration, complete these steps to avoid downtime and ensure your cloud environment supports your business operations.
- Assess NBN bandwidth: Run a speed test during business hours. Large file migrations can saturate your connection. Schedule bulk data transfers outside of business hours to minimise disruption to staff.
- Inventory applications: List every application installed on the server. Identify legacy line-of-business apps, SQL databases, and accounting software such as QuickBooks that may not run natively in SharePoint or OneDrive.
- Review email hosting: Confirm whether email is hosted on the local server (Exchange on-premises) or with a third party. Plan DNS MX record changes if moving email to Microsoft 365 Exchange Online.
- Map Active Directory dependencies: Document whether the server acts as a domain controller, DNS server, or DHCP server. Do not decommission until these services are moved or no longer required.
- Plan data retention: Australian Taxation Office (ATO) record-keeping requirements generally mandate keeping financial records for a minimum of five years. Retain server backups for this period before disposal.
Step 1: Audit Your Office Server
Log into your server and document which folders contain business-critical data. Note which applications rely on local server storage and which users have access to specific shares. This inventory ensures nothing is overlooked during migration.
Step 2: Perform a Full Backup
Before migrating any data, create a complete backup of your server to an external hard drive or secondary cloud location. Verify the backup by restoring a few sample files to confirm integrity.
Step 3: Set Up Microsoft 365 and Azure
Sign in to the Microsoft 365 admin centre at admin.microsoft.com. Navigate to Billing > Your products and select a plan:
- Microsoft 365 Business Basic: Includes Exchange Online, SharePoint, OneDrive, and Teams for web and mobile.
- Microsoft 365 Business Standard: Adds desktop Office applications and business bookings.
- Microsoft 365 Business Premium: Adds Intune device management, Entra ID conditional access, and advanced threat protection.
Assign licences to users under Users > Active users. In the Microsoft Entra admin centre at entra.microsoft.com, configure Entra ID identities. For small businesses without existing Active Directory, create cloud-only user accounts. If you have an on-premises domain, consider Entra Connect for hybrid identity synchronisation.
Step 4: Migrate or Replace Line-of-Business Applications
Identify applications that cannot run in SharePoint or OneDrive, such as legacy SQL databases or desktop accounting software. Options include:
- Moving the application to an Azure virtual machine.
- Subscribing to a cloud-based equivalent (for example, QuickBooks Online).
- Using Azure Files for shared application data that requires SMB access.
Test the application with a small group of users before rolling it out to the entire organisation.
Step 5: Migrate Files with the SharePoint Migration Tool
Download the SharePoint Migration Tool from the Microsoft Download Centre. Open the tool and sign in with a global administrator account.
- Select Upload.
- Choose your source folder on the office server.
- Select the destination as a SharePoint document library or OneDrive account.
- Review the mapping and select Migrate to begin the transfer.
Step 6: Recreate Folder Structures and Permissions
In SharePoint or OneDrive, recreate the folder hierarchy from your old server. Assign permissions to the appropriate Microsoft 365 groups or individual users. Avoid giving Full Control to everyone; use the principle of least privilege.
Step 7: Update Workstation Connections
On each office computer, disconnect any mapped network drives pointing to the old server. Install the OneDrive sync client and sync the relevant SharePoint or OneDrive folders. Users can then access files through File Explorer or Finder without connecting to a local server.
Step 8: User Communication and Training
Inform your team before retiring the server. Send a communication that explains:
- Where files are now stored.
- How to access SharePoint and OneDrive from File Explorer.
- How to request access to folders.
- Who to contact for help.
Schedule a short training session to demonstrate syncing files, restoring previous versions, and sharing documents securely.
Step 9: Decommission the Server
Only power down the physical server after confirming:
- No workstations rely on it for DNS or DHCP.
- No printers are shared through the server.
- Email and line-of-business applications no longer depend on it.
- All users can access their data in the cloud.
Keep server backups for a minimum of five years to meet ATO record-keeping requirements. When you are ready to dispose of the hardware, use a certified e-waste recycler that provides secure hard drive destruction or data wiping. Do not simply place the server in storage or discard it with general rubbish.
Troubleshooting
Slow Migration Speeds
Check your NBN upload speed. Large migrations can saturate your connection. Schedule transfers outside business hours, migrate smaller folders first, or throttle the SharePoint Migration Tool if network performance is affected.
OneDrive Sync Conflicts
If the same file is edited offline by multiple users, OneDrive creates conflict copies. Train users to save files directly to SharePoint or OneDrive and avoid working on local copies for extended periods.
Permission Inheritance Issues
SharePoint and OneDrive handle permissions differently than traditional Windows file shares. Review site membership and folder permissions under Site permissions in SharePoint. Break inheritance only when necessary and document any exceptions.
Legacy Application Compatibility
If a line-of-business application fails after migration, verify whether it requires a local server path or SQL instance. Consider hosting the application on an Azure virtual machine or migrating to a cloud-native alternative.
If you encounter issues not covered here, Open a Ticket.
Still Having Issues?
💻 Open a Ticket