Home › Knowledgebase › KB-1542

Migrating Allied Health Clinic Server To Cloud Without Downtime

Summary

This guide helps you troubleshoot and resolve: Migrating Allied Health Clinic Server To Cloud Without Downtime. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Moving patient records, imaging data, and practice management databases from a physical server in your clinic to Microsoft 365 and Azure cloud services removes the burden of maintaining on-premise hardware while keeping clinicians connected to critical files from consult rooms, home offices, or between Brisbane and Gold Coast sites. This guide focuses on retiring the physical server and eliminating the ongoing costs and risks associated with keeping a server box in the office.

Understanding the Real Cost of Your Physical Server

Many allied health clinics underestimate the true running cost of an on-premise server. Beyond the initial purchase price, you are paying for:

By moving files, identity, and applications to Microsoft 365 and Azure cloud tiers, you shift from unpredictable capital expenses to a predictable operational subscription model. Microsoft manages the hardware, power, cooling, and physical security in Australian-based data centres, while your clinic retains secure access to patient data.

Preparing for Server Retirement

Audit Your Current Environment

  1. Document every application and service currently running on your physical server, including practice management software, imaging databases, and shared network drives.
  2. Identify which services must remain on-premise during the transition and which can move to the cloud. Consult your practice management software vendor to confirm supported cloud deployment options.
  3. Review current user access permissions on shared folders so they can be replicated in SharePoint Online.
  4. Confirm your internet connection has sufficient upload bandwidth to move imaging data and large patient files to Azure.

Plan Identity Synchronisation

Set up Microsoft Entra ID (formerly Azure Active Directory) to synchronise user identities from your local Active Directory to the cloud. This allows clinicians to use the same credentials to access files in SharePoint Online and applications in Microsoft 365 without managing separate passwords.

  1. Download and install Microsoft Entra Connect on a domain-joined server within your clinic network.
  2. Launch the Microsoft Entra Connect wizard and select Express Settings for a standard single-forest deployment.
  3. Enter your Global Administrator credentials for your Microsoft 365 tenant.
  4. Enter your on-premise Active Directory Enterprise Administrator credentials.
  5. Select Password hash synchronisation as the sign-in method.
  6. Complete the installation and verify synchronisation status in the Synchronisation Service Manager.
Schedule identity synchronisation testing well before your cut-over date. Verify that staff can log in to cloud services using their existing clinic credentials before you retire the physical server.

Migrating Files to SharePoint Online

  1. Sign in to the SharePoint admin centre at https://yourtenant-admin.sharepoint.com.
  2. Select Active sites from the left navigation pane.
  3. Click Create, enter a site name such as Clinic Patient Records, and select Team site as the template.
  4. Click Finish to provision the site.
  5. Navigate to the new site, select Documents, and recreate your shared drive folder structure using the New > Folder menu.
  6. Select a folder, click Manage access, and add SharePoint groups matching your clinic roles, such as Clinicians, Reception, Billing, and Practice Managers.
  7. Download and install the SharePoint Migration Tool from the Microsoft Download Centre.
  8. Launch the tool, select SharePoint Online as the destination, and sign in with your Global Administrator account.
  9. Select your on-premise file server as the source and map the shared folders to the corresponding SharePoint document libraries.
  10. Run the migration for patient record files and general documents first, verifying that folder permissions carry over correctly.
  11. Move imaging data and large files in batches during evenings or weekends to avoid saturating your internet connection during clinic hours.
  12. Install the OneDrive sync client on clinic workstations to sync cloud libraries locally, minimising disruption to staff workflows. Note: practice management databases should not be stored in synced folders; consult your vendor for supported database hosting.
Do not delete data from the physical server until you have verified file integrity, opened sample patient files from cloud locations, and confirmed backups are in place.

Scheduling Cut-Over Outside Clinic Hours

To protect patient bookings and billing cycles, perform the final server cut-over outside normal clinic operating hours. This typically means evenings or weekends when appointments are not scheduled. Some downtime is expected during the final cut-over to switch over services.

  1. Notify all staff of the planned cut-over date and expected downtime window.
  2. Perform a final incremental sync of any files changed since the initial migration.
  3. Point workstations and applications to the cloud-based file locations.
  4. Test practice management software connectivity and verify that clinicians can open patient records from consult rooms.
  5. Confirm that billing and appointment systems are functioning before staff arrive the next morning.

Verifying Data Integrity and Privacy Compliance

Australian allied health clinics must meet privacy obligations under the Privacy Act 1988 and the Australian Privacy Principles, including the Notifiable Data Breaches (NDB) scheme. Under the NDB scheme, your clinic must assess any suspected eligible data breach and notify the Office of the Australian Information Commissioner (OAIC) and affected individuals if the breach is likely to result in serious harm. Before retiring your server, complete the following verification steps:

Retiring the Physical Server

  1. Keep the physical server powered on and accessible for at least 30 days after cut-over as a rollback option.
  2. Monitor clinic operations during this period to ensure no critical data was missed during migration.
  3. Once you are confident the cloud environment is stable, decommission the server by securely wiping all hard drives.
  4. Arrange for responsible e-waste recycling of the server hardware.
  5. Cancel service contracts, warranty renewals, and UPS maintenance agreements associated with the retired hardware.
Retiring the server removes the risk of local hardware failure, eliminates air conditioning and UPS battery costs, and gives your team secure access to files from any location with an internet connection.

Troubleshooting Common Migration Issues

Permission Errors in SharePoint Online

Microsoft Entra ID Synchronisation Failures

File Sync Conflicts

Practice Management Database Connectivity

Slow Migration Performance

If you encounter issues during migration or need assistance decommissioning your on-premise server, Open a Ticket and our Brisbane and Gold Coast support team will assist.

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