How To Migrate Old Server To Cloud
Summary
This guide helps you troubleshoot and resolve: How To Migrate Old Server To Cloud. Follow the steps below to fix the issue.
Common Causes
Retiring Your Physical Server and Moving to the Cloud
Retiring your physical server removes the burden of hardware failure, backup management, and office space constraints. Moving identity, files, and line-of-business applications to Microsoft 365 and Azure allows accountancy firms to access practice data securely from any location. This article explains how an MSP-led migration eliminates server cupboards, reduces uninterruptible power supply and air-conditioning costs, and simplifies day-to-day IT operations.
The Hidden Costs of Keeping a Physical Server
Many small accountancy firms keep a server in a cupboard or spare office without realising the total cost of ownership. Beyond the initial purchase price, you are paying for:
- Air conditioning and ventilation to prevent overheating
- Uninterruptible Power Supply (UPS) units and battery replacements
- Replacement parts when hard drives or power supplies fail
- Hardware warranty renewals and extended support contracts
- Electricity to run the server 24 hours a day, seven days a week
- Physical security and insurance for on-site equipment
When hardware fails outside of business hours, your staff cannot access client files, practice management software, or email. A cloud migration removes these single points of failure.
Australian Compliance and Data Residency Requirements
Before beginning your migration, accountancy practices must confirm that the cloud environment meets Australian regulatory obligations. The Australian Taxation Office (ATO) requires businesses to keep records for five years or more, and those records must remain accessible, complete, and unaltered. During migration, you must maintain audit trails that prove who accessed or modified client data and when those changes occurred.
Under the Australian Privacy Principles (APPs), your organisation is responsible for protecting client personal information. You must ensure that data is stored in an Azure region located within Australia, such as Australia East or Australia Southeast, to satisfy data sovereignty requirements. Avoid storing practice data in regions outside Australia unless you have documented client consent and a legal basis for doing so.
Confirm that your practice management and tax software are compatible with Azure Virtual Machines or Azure Virtual Desktop before migrating. Some Australian tax software vendors require specific Windows versions, .NET frameworks, or local printer redirection that must be tested in the cloud environment before go-live.
Planning Your Migration
Audit Your Current Environment
Before moving anything, document what is currently running on your server:
- User accounts and group memberships in on-premises Active Directory
- File shares, folder structures, and NTFS permissions
- Line-of-business applications, including practice management and tax software
- Database servers and SQL instances
- Printers and shared devices mapped to the server
- Backup schedules and retention policies
Choose Your Cloud Destination
For most accountancy practices, the migration path involves:
- Identity: Move from on-premises Active Directory to Microsoft Entra ID (formerly Azure Active Directory) via Microsoft 365
- Files: Migrate file shares to OneDrive for Business and SharePoint Online
- Applications: Host line-of-business applications on Azure Virtual Machines or Azure Virtual Desktop
- Email: Move to Exchange Online as part of Microsoft 365
Migration Steps
- Assess internet connectivity. Confirm your office has a stable business-grade connection. For a small accountancy practice, a minimum of 50 Mbps upload speed is recommended for initial file synchronisation to SharePoint Online and OneDrive for Business. Use a speed test tool to verify upload performance during business hours.
- Set up Microsoft 365. Sign in to the Microsoft 365 admin centre. Go to Users > Active users and select Add a user to create tenant accounts for all staff. Go to Billing > Licences and assign Microsoft 365 Business Premium licences, which include Exchange Online, OneDrive for Business, SharePoint Online, and Microsoft Entra ID P1.
- Configure identity synchronisation. Download Microsoft Entra Connect from the Microsoft Entra admin centre. Run the installer on a domain-joined server and select Express settings. When prompted, enter your on-premises Active Directory enterprise administrator credentials and your Microsoft 365 global administrator credentials. Choose Password hash synchronisation as the sign-in method. Complete the wizard and verify synchronisation status in the Microsoft Entra admin centre under Identity > Overview > Microsoft Entra Connect sync.
- Migrate file data. Download the SharePoint Migration Tool (SPMT) from the Microsoft Download Centre. Install SPMT on a workstation with access to the file server. Launch the tool, select Upload > File share, and browse to your on-premises file share. Select SharePoint Online or OneDrive for Business as the destination. Map each source folder to a target document library. Select Preserve permissions if you want to carry over NTFS access control lists. Click Migrate and monitor progress in the SPMT dashboard.
- Deploy applications. Sign in to the Azure portal. Select Virtual machines > Create. Choose an Australian region such as Australia East. For practice management and tax software workloads, select a Standard_D4s_v3 or Standard_D8s_v3 VM size. Select Windows Server 2022 Datacenter as the image. Configure managed disks with SSD storage. After deployment, install your line-of-business applications and configure printer redirection through Remote Desktop Services if staff need to print to office devices.
- Test access. Have staff log in from outside the office using their Microsoft 365 credentials. Verify they can open files in SharePoint Online, send and receive email in Outlook, and launch practice management applications hosted on Azure Virtual Machines or Azure Virtual Desktop.
- Establish rollback and business continuity plans. Before decommissioning the server, create a full system image backup of the physical server and store it on an external drive kept on-site for at least 30 days. Document the server IP addresses, local administrator credentials, and application licence keys. If a critical failure occurs during migration, you must be able to restore the on-premises environment within one business day.
- Decommission the server. Only after data is verified in the cloud, backups are confirmed, and the rollback period has passed, power down the physical server. Arrange for secure disposal of hard drives through a certified e-waste provider that issues a destruction certificate.
Warning: Do not delete data from your physical server until you have verified that all files are accessible in the cloud and a recent cloud backup has been completed. Maintain audit logs throughout the migration to satisfy ATO record-keeping requirements.
Tip: Run the migration in stages. Move non-critical data first, then migrate active client files once you have confirmed the process works.
Post-Migration Checklist
- Confirm all users can log in with their Microsoft 365 credentials
- Verify file permissions match the previous server configuration
- Test printing from cloud desktops to office printers
- Update any hard-coded server paths in application settings
- Schedule regular cloud backups and test a file restore
- Confirm audit logs are capturing user access and file modification events
- Remove old server hardware from the network
Troubleshooting Common Migration Issues
Permission Errors After File Migration
If users cannot access migrated files, the NTFS permissions may not have mapped correctly to SharePoint Online or OneDrive for Business. Sign in to the Microsoft 365 admin centre, go to SharePoint, and open the affected document library. Select Settings > Library settings > Permissions for this document library. Review the permission levels and re-grant access to the appropriate Microsoft 365 groups or individual users.
OneDrive Sync Conflicts
If users receive sync conflict errors, multiple staff members may have edited the same file during migration. Instruct users to open OneDrive, select the conflicting file, and choose Keep both versions or Resolve conflict from the sync client menu. Advise staff to co-author documents in SharePoint Online rather than editing local copies after migration.
Application Compatibility Issues
If practice management or tax software fails to launch on an Azure Virtual Machine, confirm that the VM meets the vendor’s minimum requirements for CPU, RAM, and Windows version. Connect to the VM using Remote Desktop, open Control Panel > Programs and Features, and reinstall the application if required. Check the Azure portal under Virtual machines > [VM name] > Networking to ensure required ports are open.
Microsoft Entra Connect Synchronisation Failures
If user accounts do not appear in Microsoft Entra ID, open the Synchronisation Service Manager on the server running Microsoft Entra Connect. Select Operations and review the most recent run profile for errors. Common causes include expired service account passwords or duplicate user principal names. Resolve the error, then select Run profiles > Run Delta synchronisation.
If you need assistance planning or executing your server migration, Open a Ticket.
Still Having Issues?
💻 Open a Ticket