Home › Knowledgebase › KB-1215

How to reduce server room costs for small business

Summary

This guide helps you troubleshoot and resolve: How to reduce server room costs for small business. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Many small businesses in Australia continue to rely on a physical server located in an office cupboard or dedicated server room for file storage and basic application hosting. While this setup may have been necessary in the past, modern cloud services now provide a more cost-effective and secure alternative. Retiring your on-premises hardware removes recurring expenses related to power consumption, air conditioning, UPS battery replacement, hardware warranties, and refresh cycles. Migrating your data and identity services to Microsoft 365 and Azure allows your team to work securely from anywhere while reducing the burden of manual patching and on-site maintenance.

Understanding the True Cost of a Physical Server

Before beginning a migration, it is helpful to analyse the total cost of ownership for your current server infrastructure. Many organisations focus only on the initial purchase price of the hardware, overlooking the ongoing operational expenses that accumulate over time.

Tip: Review your last 12 months of electricity bills and IT invoices to calculate the actual annual cost of running your on-premises server. This baseline makes it easier to justify the migration to stakeholders.

Australian Data Residency and Privacy Considerations

When migrating to the cloud, Australian small businesses must consider where their data is physically stored. Microsoft Azure operates data centre regions in Australia, including Australia East and Australia Southeast. Selecting an Australian region helps satisfy data residency requirements and supports compliance with the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs).

When retiring physical hardware, ensure hard drives undergo secure data destruction through a certified e-waste recycler to meet privacy obligations for the disposal of personal information.

Planning Your Migration to Microsoft 365 and Azure

A successful migration requires careful planning to ensure that critical business files, user identities, and applications are moved securely without disrupting daily operations. The goal is to move workloads from a physical box in your office to enterprise-grade cloud tiers managed by Microsoft.

Caution: Cloud services depend on a stable internet connection. Assess your ongoing bandwidth requirements, not just for the initial migration, but for daily staff access to files and applications. Poor connectivity will impact productivity after the server is decommissioned.

Step 1: Audit Your Current Environment

  1. Create an inventory of all data stored on your physical server, including shared folders, application databases, and user profiles.
  2. Identify which applications are hosted locally and determine if cloud-based equivalents exist within Microsoft 365 or Azure.
  3. Document your current user accounts, group memberships, and permission structures so they can be replicated in the cloud.
  4. Assess your internet connection speed and reliability, as cloud migration depends on sufficient upload bandwidth for initial data transfer.

Step 2: Set Up Microsoft 365 and Microsoft Entra ID

  1. Provision a Microsoft 365 tenant for your organisation and verify your custom domain name.
  2. Navigate to the Microsoft 365 admin centre > Users > Active users to create user accounts, matching existing email addresses and display names.
  3. Navigate to the Microsoft 365 admin centre > Billing > Licences to assign appropriate licences to each user based on their role, such as Microsoft 365 Business Premium for access to Intune and Microsoft Entra ID features.
  4. Configure Microsoft Entra ID (formerly Azure Active Directory) to manage cloud identities and enable single sign-on for connected applications.

Step 3: Migrate Files and Data

  1. Map your existing on-premises folder structure to SharePoint Online document libraries or OneDrive for Business locations.
  2. Use the SharePoint Migration Tool or a third-party migration utility to transfer files from your local server to the cloud.
  3. Set up permissions and sharing links in SharePoint to replicate the access controls previously managed on your file server.
  4. Train staff on accessing files via the SharePoint web browser interface, the OneDrive sync client, or the SharePoint mobile app. Do not use UNC paths such as \\tenant.sharepoint.com, as these are not supported for SharePoint Online.

Step 4: Move Applications and Services

  1. Identify line-of-business applications that can be replaced with Software as a Service (SaaS) offerings available through Microsoft 365 or Azure Marketplace.
  2. For applications that must remain on a server, consider provisioning an Azure Virtual Machine or Azure Virtual Desktop environment rather than maintaining physical hardware on-site.
  3. Configure Azure Backup or Microsoft 365 backup solutions to protect cloud data against accidental deletion or ransomware.
  4. If you maintain a hybrid environment, retain a local domain controller and DNS server to support ongoing authentication and directory services.
Caution: Do not decommission your physical server until you have verified that all critical data has been successfully migrated, tested, and backed up in the cloud. Maintain a read-only copy of the old server for at least 30 days after migration as a safety net.

Retiring the Physical Server

Once your workloads are running in Microsoft 365 and Azure, you can begin the process of retiring your on-premises hardware. This step eliminates the daily headaches associated with server room management.

  1. Schedule a decommissioning date outside of peak business hours to minimise disruption.
  2. Notify all staff that the physical server will be taken offline and confirm they can access all required files and applications from the cloud.
  3. Power down the server gracefully and disconnect it from your network.
  4. Arrange for secure data destruction of hard drives through a certified e-waste recycler to comply with Australian privacy obligations.
  5. Cancel or allow to expire any remaining hardware warranty contracts, UPS maintenance agreements, and colocation fees if applicable.
Tip: Consider keeping your internet connection and firewall in place, as these are still required to access cloud services. You can, however, remove the dedicated server room air conditioning and rack infrastructure if no other equipment requires it.

Benefits of Cloud Migration

Moving away from a physical server provides several immediate and long-term advantages for small businesses and home offices:

Troubleshooting Common Migration Issues

Permission Errors After Migration

If users cannot access migrated files, verify that SharePoint site permissions and library-level access controls were correctly mapped from the source file server. Check that user accounts exist in Microsoft Entra ID and have been assigned the appropriate licences through the Microsoft 365 admin centre.

Large File Upload Failures

OneDrive and SharePoint have file size limits that may cause large files to fail during upload or sync. Encourage users to split large datasets into smaller folders or use the SharePoint Migration Tool for bulk transfers rather than dragging and dropping through the browser.

Client Sync and Connectivity Problems

If the OneDrive sync client is not connecting or files are not updating, confirm that the device has a stable internet connection and that the user is signed in with their organisational Microsoft 365 account. Reset the OneDrive client or check for pending Windows updates that may affect the sync engine.

For further assistance with your migration, Open a Ticket.

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