"Should we move to the cloud?" is one of the questions Perth business owners ask most often — and also one of the most inconsistently answered. Some IT providers will tell you to move everything immediately. Others will say your current server setup is fine. The reality is more specific than either answer: the right time to migrate depends on what's sitting in your server room, what your business actually needs, and what cloud infrastructure genuinely offers you compared to where you are now.
This guide cuts through the noise. We cover what cloud migration actually means for a typical Perth SMB, the warning signs that your on-premises server has passed its useful life, what can and can't realistically move to the cloud, what a proper migration looks like, the common mistakes that turn migrations into disasters, and why Managed ICT Solutions is the right first call for Perth businesses considering the move — whether you're in Cannington, Joondalup, Fremantle, Malaga, Canning Vale, Rockingham, Midland, Belmont, Balcatta, Subiaco or anywhere else across the Perth metro area.
What Cloud Migration Actually Means for a Perth SMB
When an IT provider says "move to the cloud," they can mean quite different things. The term covers a broad spectrum — from something as straightforward as replacing a local email server with Microsoft 365 Exchange Online, right through to a full infrastructure migration where every server, application and service moves to hosted cloud environments.
For most Perth small and medium businesses, cloud migration in practice means one or more of the following:
- Email migration — moving from an on-premises Exchange server (or a third-party hosted email service) to Microsoft 365 Exchange Online. Staff get the same Outlook experience, but the server infrastructure is Microsoft's problem, not yours.
- File server migration — replacing a physical file server (or NAS device) with SharePoint document libraries and OneDrive for Business. Staff access files through File Explorer (mapped drive-style) or via the web, from any device, anywhere.
- Active Directory to Azure AD — moving user account management from an on-premises Windows Server domain controller to Azure Active Directory (now called Microsoft Entra ID). This is the foundation for cloud identity and Single Sign-On across cloud applications.
- Line-of-business application migration — moving accounting software, ERP systems, CRM platforms or industry-specific tools from locally installed (on a server) versions to cloud-hosted or SaaS equivalents.
- Server workloads to Azure — lifting specific server functions (databases, web servers, custom applications) to Microsoft Azure virtual machines or Platform-as-a-Service environments rather than replacing the functionality entirely.
Most Perth SMBs don't do all of these at once. A typical migration is phased — email first (lowest risk, fastest payoff), then file storage, then other services as their on-premises equivalents reach end of life. A well-planned phased migration is far less disruptive than trying to move everything in a single project.
Many Perth businesses end up with a hybrid IT environment — some workloads in the cloud, some remaining on-premises — and that's a perfectly reasonable place to be. Not everything belongs in the cloud. Specialist manufacturing software, legal practice management systems with specific database requirements, and applications with high latency sensitivity sometimes run better locally. A good IT provider will tell you what should move and what genuinely shouldn't, rather than pushing a one-size-fits-all answer.
Signs Your Perth Business Is Ready to Move to the Cloud
Most Perth businesses don't decide to migrate to the cloud proactively — they get pushed toward it by a combination of circumstances that make continuing with on-premises infrastructure increasingly costly and risky. Here are the clearest signals that it's time to have the conversation.
Your server is approaching end of life — or already past it
Windows Server 2016 reaches end of support in January 2027. Windows Server 2012 and 2012 R2 have been unsupported since October 2023. If your business is running either of these, you're either already past the point where Microsoft will provide security patches (2012), or rapidly approaching it (2016). An unsupported server running internet-connected services is a significant security liability. For many Perth businesses in this situation, migrating to Microsoft 365 and Azure is a better investment than purchasing new server hardware and a Windows Server 2022 licence for another seven-year cycle.
Your server hardware is failing or ageing badly
A server that's generating SMART warnings on its drives, running out of RAM, struggling to handle the number of concurrent users it used to handle without issue, or requiring increasingly frequent repairs is telling you something. Hardware repairs on ageing server equipment are often false economy — you're spending money to extend the life of something that's still going to need replacing within 12-18 months, and it carries an elevated risk of total failure in the meantime.
Your team works across multiple locations or remotely
A traditional on-premises file server works well when everyone is in the same office. When staff work from home, across multiple Perth sites, or on FIFO rosters, VPN access to an on-premises server introduces latency, reliability issues and security complexity. Cloud file storage (SharePoint, OneDrive) and cloud applications are designed from the ground up for distributed access. If your team's mobility has outgrown your infrastructure, the cloud often solves the problem cleanly.
You've had a backup or data loss event
A backup failure, a ransomware attack, or any incident that put your data at risk should prompt a serious review of your infrastructure resilience. Cloud-hosted data with geo-redundant replication and Microsoft's 99.99% uptime SLA is inherently more resilient than a single on-premises server in a storeroom. If the prospect of that server room flooding, burning or simply dying has kept you up at night, it's worth looking at what the cloud alternative actually costs.
Your IT costs are unpredictable and increasing
On-premises servers carry hardware refresh costs every 5-7 years, ongoing maintenance, power costs, physical security, and the opportunity cost of your IT provider's time keeping them running. Cloud subscriptions (Microsoft 365, Azure) replace these with predictable monthly costs that scale with your headcount. When you add up the full cost of your current on-premises setup over three years, the comparison with cloud alternatives is often much more favourable than it appears on a monthly basis.
What Can (and Cannot) Move to the Cloud
Typically moves well to the cloud
- Business email (Exchange → Microsoft 365)
- File storage and document management (file server → SharePoint/OneDrive)
- User identity and authentication (Active Directory → Azure AD)
- Microsoft Office applications (local install → Microsoft 365)
- Business phone systems (PBX → Teams Phone / 3CX Cloud)
- Video conferencing and collaboration (Teams)
- Backup and disaster recovery (Azure Backup, Veeam Cloud)
- Accounting and ERP SaaS platforms (MYOB Business, Xero)
- CRM systems (Salesforce, HubSpot, Dynamics 365)
- Basic web server and database workloads (to Azure VMs)
May need careful assessment before migrating
- Specialist on-premises ERP systems (Pronto Xi, SAP B1 with heavy customisation)
- Applications with real-time local hardware dependencies (CNC machines, lab equipment)
- High-volume local file servers with very large datasets (>10TB) — cost assessment required
- Applications requiring sub-10ms latency for local processing
- Legacy Windows desktop applications without cloud equivalents
- CCTV and on-premises physical security servers
- Applications where data sovereignty has specific on-premises requirements
What a Proper Cloud Migration Actually Looks Like
A professionally managed cloud migration is a structured project, not a single event. For a Perth SMB migrating email and file storage, the process typically takes 4-10 weeks from assessment to full go-live. Here's what that looks like in practice.
Discovery and Assessment
Before anything moves, we document what's there — every server, every service running on it, every application that connects to it, every user account, every shared mailbox, every mapped drive and every third-party integration. This is the step most rushed migrations skip, and it's where most migration problems originate. An undocumented dependency discovered mid-migration is a bad day for everyone involved.
Cloud Environment Setup and Security Configuration
Before any data moves, the destination is configured and secured. For a Microsoft 365 migration, this means setting up the tenant, verifying and configuring the custom domain, enabling MFA and security defaults, configuring SPF/DKIM/DMARC for email authentication, setting up SharePoint site structures, and establishing the administrative roles and permissions framework. Getting this right before migration prevents security gaps and reconfiguration work post-migration.
Pilot Migration and Testing
A small group of non-critical users migrates first. Mailboxes, OneDrive, shared files and application access are all tested in the real cloud environment before the rest of the business makes the move. Issues are identified and resolved while the blast radius is small. Pilot users provide feedback, and the migration plan is adjusted if needed. This step is not optional for a professional migration.
Full Migration and DNS Cutover
The remaining users migrate. For email, this includes mailbox data, calendar items, contacts and any shared mailboxes (info@, accounts@, reception@). File server data moves to SharePoint document libraries, with mapped drives reconfigured to point at the new cloud locations. The DNS MX record change (which tells the internet to deliver email to Microsoft 365 rather than the old server) is timed carefully to coincide with completed mailbox migrations — not before.
Device Configuration and Mobile Enrolment
Staff computers and mobile devices need to be configured for the new environment. On managed computers, this is automated via Microsoft Intune or Group Policy. Mobile devices (phones and tablets used for email and Teams) need to be either manually reconfigured or enrolled in mobile device management. This is the step most business owners forget to plan for and then discover on go-live day when half the team's phones aren't receiving email.
Decommission, Documentation and Handover
Once the cloud environment is stable and confirmed fully functional, the on-premises server can be decommissioned — but not immediately. A 2-4 week parallel running period gives everyone confidence before the old server is switched off. Full documentation of the new environment is produced. Staff receive training on any changed workflows. The old server hardware can then be securely wiped and disposed of or repurposed.
Cloud vs On-Premises: The Real Cost Comparison for Perth SMBs
| Cost Factor | On-Premises Server | Microsoft 365 + Azure Cloud |
|---|---|---|
| Hardware purchase (server) | $5,000–$15,000 every 5-7 years | ✔ Eliminated |
| Windows Server licence | $800–$3,000+ per cycle | ✔ Eliminated |
| CAL licences (per user) | $100–$300 per user | ✔ Eliminated (included in M365) |
| Monthly email & files cost | Included in server cost | $18–$34 per user/month (M365 Standard/Premium) |
| Backup costs | $50–$200/month (software + storage) | $10–$30/month (Microsoft 365 Backup) |
| Power and cooling | $40–$150/month | ✔ Eliminated |
| Hardware maintenance | $500–$2,000/year | ✔ Microsoft's responsibility |
| Security patching | Manual, requires IT time | ✔ Automatic, included |
| Uptime SLA | Best-effort (your hardware) | ✔ 99.9–99.99% Microsoft SLA |
| Disaster recovery | Requires separate DR setup | ✔ Built-in geo-redundancy |
| Remote access | VPN required (cost + complexity) | ✔ Native, any device |
| Scalability | ✗ Hardware constraints | ✔ Instant, pay-as-you-go |
For a 20-person Perth business replacing a single file and email server with Microsoft 365 Business Standard, the rough three-year comparison looks like this: on-premises hardware refresh + licencing + maintenance runs approximately $25,000–$35,000 over three years. Microsoft 365 Business Standard at ~$18 per user per month for 20 users comes to $12,960 over three years — plus a one-time migration cost of $5,000–$12,000. The cloud option is typically equal to or lower in total cost, with better resilience, built-in security and no hardware to manage.
Common Cloud Migration Mistakes Perth Businesses Make
Starting the migration before the destination is secured
A new Microsoft 365 tenant that hasn't had MFA enabled, security defaults configured, SPF/DKIM/DMARC set up, or admin account separation applied is a security risk from day one. We regularly see Perth businesses that migrated to Microsoft 365 years ago but never went through a proper security hardening process. Their data is in the cloud, but it's not as protected as it should be. Security configuration should happen before any mailboxes migrate, not as an afterthought months later.
Cutting over the MX record before mailboxes are ready
The MX record is the DNS entry that tells the internet where to deliver email for your domain. If you change it before the destination mailboxes are fully provisioned and tested, incoming email either bounces or goes missing. This is one of the most common migration errors and one of the most disruptive. The sequence is non-negotiable: provision mailboxes, migrate data, test, then change the MX record — never the other way around.
Migrating during business hours without a rollback plan
Email and file system cutovers should happen outside business hours — typically a Friday evening, with a tested rollback plan if something goes wrong before Monday morning. Attempting a cutover on a Tuesday afternoon with the whole team watching their inboxes is a recipe for a very stressful afternoon. A proper migration plan specifies not only what happens when things go right, but exactly what the steps are if they don't.
Forgetting shared mailboxes, distribution lists, and room calendars
Individual user mailboxes get migrated. The info@ mailbox, the accounts@ mailbox, the shared calendar for the meeting room, and the distribution group for the whole company often don't — until someone notices they're missing two days after go-live. Auditing every mail object, calendar resource and group in the current environment is a prerequisite for a complete migration, not an optional extra.
Not training staff on changed workflows
Moving from a mapped network drive to SharePoint is a meaningful workflow change for staff who've been using the same folder structure for ten years. Even if the technical migration is flawless, helpdesk tickets will spike in the first week if staff haven't had a proper orientation to how file access, sharing and collaboration work in the new environment. A 30-minute staff session before go-live is worth three days of post-migration support calls.
Cloud Migration in the Perth Context
A few things matter specifically to Perth businesses considering cloud migration that don't always feature in generic cloud migration guides.
NBN reliability and internet dependency
Cloud infrastructure depends on internet connectivity. If your Perth business location has unreliable NBN (a more common situation in parts of the metro area than many assume), moving your file server to SharePoint means your team can't access files when the internet drops. This is solvable — a 4G/5G backup connection provides failover for most scenarios — but it's a dependency that needs to be planned for, not discovered after migration.
Australian data sovereignty
Perth businesses in legal, medical, financial and government-adjacent sectors often have data residency requirements. Microsoft Azure and Microsoft 365 both offer Australian data centres (Australia East in NSW, Australia Southeast in Victoria), and Australian tenant data for core services is stored in-country by default. This satisfies Australian Privacy Act requirements and most industry-specific obligations. If your IT provider is recommending a cloud solution that stores data outside Australia without a specific compliance reason, ask why.
ERP systems common in Perth industries
Perth has a strong concentration of businesses in mining services, construction, engineering, agriculture, and resources — sectors that often run industry-specific ERP platforms. Pronto Xi, SAP Business One, Sage, and various specialist mining and civil construction software packages have cloud versions, hosted versions, and sometimes no cloud equivalent at all. Understanding how your core business software will work in a cloud environment is a non-negotiable part of the pre-migration assessment — not something to figure out after you've moved everything else.
Why Managed ICT Solutions Is Your First Call for Cloud Migration in Perth
Cloud migration is not a product — it's a professional service. How it goes depends almost entirely on the experience and thoroughness of whoever plans and executes it. Getting it wrong costs real money: lost email, inaccessible files, confused staff, delayed business operations, and sometimes data that requires expensive recovery to restore.
Managed ICT Solutions has been delivering IT services to Perth businesses from our local offices for over 15 years. We've migrated businesses from on-premises Exchange to Microsoft 365, from file servers to SharePoint and OneDrive, from on-premises Active Directory to Azure AD, and from on-premises server workloads to Azure virtual machines. Our clients include businesses across Cannington, Osborne Park, Joondalup, Fremantle, Malaga, Wangara, Canning Vale, Rockingham, Midland, Belmont, Balcatta, Subiaco, Welshpool, Kewdale and all surrounding Perth suburbs.
We are a Microsoft partner. We handle the full migration lifecycle — cloud readiness assessment, environment setup, security hardening, phased migration, device configuration, staff training and post-migration managed IT support. We don't hand you a migrated environment and disappear; we can continue managing it as your ongoing IT provider under a managed services agreement.
Not sure whether your business is ready to migrate, or what a migration would involve for your specific environment? Call us on (08) 9242 4511 or contact us online and we'll conduct a free cloud readiness assessment — covering your current infrastructure, any application dependencies, your internet connectivity, your compliance obligations and a realistic cost comparison. No obligation, no sales pressure. Just a clear picture of where you are and what your options look like.
Frequently Asked Questions
What does cloud migration mean for a Perth small business?
For most Perth SMBs, it means moving email, files and applications from an on-premises server to cloud-hosted services — typically Microsoft 365 and Azure. In practice, this usually means replacing a local file server with SharePoint and OneDrive, and an on-premises Exchange server with Microsoft 365 Exchange Online. Most Perth businesses do this in phases, not all at once, and many end up in a hybrid model where some things stay on-premises.
How much does cloud migration cost for a Perth SMB?
An email migration for a 15-person Perth business typically costs $2,000–$5,000 in professional services, plus ongoing Microsoft 365 licencing ($18–$34 per user per month). A full migration including files, email and Active Directory for a 20-30 person business might cost $8,000–$25,000 in migration services. Over three years, the total cost of ownership is typically comparable to or lower than continuing with on-premises infrastructure once hardware refresh, licencing and maintenance costs are included.
Does Microsoft store Australian data in Australia?
Yes. Microsoft's Australia East and Australia Southeast data centres store core Microsoft 365 data (email, files, Teams, SharePoint) in-country by default for Australian tenants. This satisfies Australian Privacy Act requirements and most industry compliance obligations for Perth businesses in regulated sectors.
Can a Perth business migrate to the cloud without significant downtime?
Yes, with proper planning. Email migrations run old and new systems in parallel with a single cutover outside business hours. File server migrations can be staged with data pre-synced before the final switch. The key is planning — a well-structured migration with a tested rollback plan is a very different experience from an ad hoc migration done under time pressure.
Ready to Move Your Perth Business to the Cloud?
Managed ICT Solutions is Perth's local Microsoft partner for cloud migration. Call us first — before you sign a cloud contract, buy new server hardware, or start a migration project. We'll give you an honest assessment of your options and a clear plan that fits your business, your budget and your timeline.
Book Free Cloud Assessment Call (08) 9242 4511