Cloud migration for small business has stopped being a “someday” project. If your office still relies on an ageing server in a cupboard, an on-premises Exchange mailbox or a shared drive that only works over the VPN, support dates, security risks and staff patience are all running out. However, most small businesses don’t need a complex multi-cloud programme. For many, the move is mainly Microsoft 365 for email, files and collaboration, plus Azure for the few systems that still need a server.
This guide explains what moves where, how to choose an approach for each system, and the nine steps we follow to migrate safely, from the first inventory to switching off the old server.
Updated 7 November 2026
What's changed for cloud migration in 2026
- Exchange Server 2016 and 2019 out of support (14 Oct 2025). Microsoft now points customers to Exchange Online or its subscription edition. See "Why move now".
- Windows Server 2016 support ends (12 Jan 2027). Its last security update arrives in January 2027, so servers still on it need a plan now. See "Why move now".
- ASD Essentials published (15 Oct 2026). It succeeds the Essential Eight over about two years. Step 5 explains where it fits in a migration.
- Seven migration strategies, not five. The widely used AWS framework now lists seven "Rs", adding relocate, retain and retire. Our updated table shows how each applies to a small business.
Why move now: cloud migration deadlines for small business
For most small businesses, the trigger for a cloud migration isn’t a strategy paper. Instead, it’s a support date. When Microsoft ends support for a product, it stops releasing security fixes, so every new vulnerability stays open for good. Three dates affect many Perth offices.
Old servers keep running after these dates, which is exactly why they get forgotten. Meanwhile, an unsupported server holding your files, email or accounting data becomes one of the easiest ways into your business. You could replace it with another on-site server. For many small teams, though, cloud migration for small business means moving those workloads to Microsoft 365 and Azure, and leaving the hardware refresh cycle behind.
Microsoft 365 or Azure: what goes where
Microsoft 365 and Azure solve different problems, and a typical small business migration uses both. In short, Microsoft 365 replaces the services your server used to provide, while Azure hosts the software that still needs a server.
| Microsoft 365 | Azure | |
|---|---|---|
| What it is | Software as a service: ready-made apps for email, files, chat and meetings | Infrastructure and platform services: virtual servers, storage, databases and networking |
| What it replaces | An Exchange server, file server shares, an on-site intranet and older Office installs | Application servers, line-of-business databases and remote desktop servers |
| Who manages what | Microsoft runs the service; you manage users, settings, security and data | Microsoft runs the hardware; you or your IT partner manage the operating system, apps, patching and backups |
| How you pay | Per user, per month | For what you run, mainly compute time plus storage |
| Best for | Almost every small business | Software that needs a Windows server and has no cloud version yet |
Where small business systems land in a cloud migration
Every business is different, but these six moves cover most small offices.
Email to Exchange Online
Mailboxes, calendars and shared mailboxes move across, and the on-site Exchange server is retired.
Shared files to SharePoint and Teams
Department shares become SharePoint sites or Teams, and personal folders move to OneDrive.
Logins to Microsoft Entra ID
One identity for email, files and apps, protected by multi-factor authentication and conditional access.
Business apps to the cloud
Accounting, job or practice software moves to the vendor's cloud version, or to an Azure virtual server.
Backups to a separate service
Microsoft 365 data and Azure servers are backed up outside Microsoft's own copies, with restores tested.
Devices managed from the cloud
Laptops are enrolled for central management, so updates, settings and encryption no longer depend on the office network.
The 7 Rs: choosing a cloud migration approach for small business
Not every system should move the same way. AWS’s widely used framework describes seven migration strategies, known as the 7 Rs. The names come from AWS, but the thinking applies just as well to Microsoft 365 and Azure. In a small business, most systems end up as repurchase, rehost or retire.
| Strategy | What it means | Small-business example |
|---|---|---|
| Retire | Switch it off because nobody needs it | An old intranet, or a second file server full of duplicates |
| Retain | Leave it where it is for now, with a review date | A PC that runs workshop machinery or lab equipment |
| Rehost | Move it as-is to a cloud server ("lift and shift") | Accounting software moved to an Azure virtual machine |
| Relocate | Move a whole virtual environment without changing it | Rare in small business; suits larger virtualised setups |
| Replatform | Move it with small changes to use managed services | A SQL database moved to a managed Azure database |
| Repurchase | Replace it with a cloud (SaaS) product | Exchange server replaced by Exchange Online |
| Refactor | Rebuild the application to be cloud-native | Usually only for software you have built yourself |
Above all, giving every system one of these labels early stops scope creep and makes costs easier to estimate.
Nine steps to a smooth cloud migration for small business
This is the process we use with clients. Select a step to jump to the detail.
Set clear goals
Decide what success looks like before anyone touches a server.
Take a full inventory
List systems, data, users, licences and the links between them.
Clean up first
Retire old data and fix messy permissions before they move.
Pick a home for each system
Map every workload to Microsoft 365, Azure or retirement.
Secure the tenant
Turn on MFA, protect admin accounts and check data location.
Plan backup and recovery
Microsoft keeps the service running; your data is still your job.
Run a pilot
Move a small group first and fix what they find.
Migrate in waves
Cut over out of hours with a written rollback plan.
Train, switch off, optimise
Support staff, retire old kit securely and review costs.
1. Set clear goals
Start with the business reason. Common ones include an unsupported server, staff who need reliable remote access, ageing hardware or a security review that flagged gaps. Next, write down two or three outcomes you can check later, such as “everyone can reach their files securely from home” or “no on-site server by June”.
Watch out for: goals that are really wish lists. If a feature doesn’t support one of your outcomes, park it for a second phase.
2. Take a full inventory
List every server, shared folder, mailbox and application, plus the people who use each one. Then note how systems connect: a scanner that emails to a local address, a report that reads from the accounting database, or a spreadsheet macro pointing at a mapped drive. In practice, these hidden links cause most cutover surprises.
Watch out for: software licences tied to a physical server, and vendors that only support certain cloud setups. Therefore, check with each vendor before you commit to a plan.
3. Clean up before your small business cloud migration
A cloud migration is the best chance a small business gets to tidy up. First, archive or delete data nobody needs, remove accounts for staff who have left, and simplify folder permissions that have grown over the years. After all, moving clutter costs time and storage, and old permission mistakes follow you into the cloud.
Watch out for: record-keeping rules. Some records must be kept for set periods, while the Privacy Act expects personal information to be destroyed or de-identified once you no longer need it. So agree what stays and what goes before deleting anything.
4. Pick a home for each system
Use your inventory and the 7 Rs table above to give each system a destination. For example, email and files almost always go to Microsoft 365. Line-of-business software goes to the vendor’s cloud version where one exists, or to an Azure virtual server where it doesn’t. Finally, anything nobody uses is retired.
Watch out for: rebuilding the old server in the cloud by default. A virtual machine running around the clock is billed for every hour it runs, so keep only the servers you genuinely need.
5. Secure the tenant before you move data
Set up security before the first mailbox moves, not after. First, turn on multi-factor authentication for everyone, keep separate accounts for administrators, block legacy sign-in methods and apply conditional access. Next, check where your data will live. A Microsoft 365 tenant’s data location is set when the tenant is created, and for tenants in the Australian geography Microsoft stores core data such as mailboxes and SharePoint, OneDrive and Teams content at rest in Australia. For Azure, choose an Australian region such as Australia East (New South Wales) or Australia Southeast (Victoria).
Watch out for: assuming the cloud is secure by default. Microsoft secures the platform, but you are responsible for configuration, accounts and data. ASD’s Essential Eight, and its successor ASD Essentials, give you a practical list of controls to aim for.
6. Plan backup and recovery
Microsoft keeps its services running and protects against failures in its own data centres. That isn’t the same as a backup you control. A deleted folder, a compromised account or ransomware that encrypts synced files can all damage your data, and built-in retention has limits. For that reason, back up Microsoft 365 and any Azure servers to a separate service, and test a restore before go-live.
Watch out for: backups that only cover email. Instead, include SharePoint, OneDrive and Teams, and write down who restores what, and how quickly.
7. Run a pilot
Move a small, willing group first, ideally including someone who uses every system. Then let them work normally for a week or two and note what breaks: shortcuts, printers, scanners, shared calendars, or apps that expected a mapped drive.
Watch out for: piloting only with confident users. Instead, include a typical staff member so you hear the questions the whole team will ask.
8. Migrate in waves and cut over carefully
Group the remaining users and systems into waves, then move each one out of hours. Copy data ahead of time so the final sync is small, update email (MX) and other DNS records at the planned moment, and keep the old system read-only until users confirm everything has arrived. In addition, write a rollback plan for each wave, even if you never use it.
Watch out for: moving everything in one weekend. By contrast, smaller waves make problems easier to spot and fix.
9. Train, switch off and optimise
Give staff short, practical training on where files now live and how to share them safely. Then decommission old hardware properly: wipe or destroy its drives, cancel licences you no longer need and update your IT documentation. After a month, review Azure usage, resize or shut down servers that are bigger than necessary, and set budget alerts.
Watch out for: treating go-live as the finish line. A quick review after one and three months usually finds settings worth tightening.
What drives the cost of cloud migration for small business
Every business is different, so there’s no single price. Instead, these factors move the number most.
- Users and mailboxes. Microsoft 365 is licensed per user, and large mailboxes take longer to move.
- The amount and state of your data. Big, cluttered file shares take longer to clean up and migrate.
- Line-of-business software. Each application needs its own plan, vendor checks and testing.
- Servers that stay running. Azure virtual machines are billed for the time they run, plus storage.
- Security and backup. Proper configuration, backup and restore testing are part of the job, not optional extras.
- Your internet connection. Upload speed affects how fast data moves, and matters more once everything lives in the cloud.
As a result, the most affordable migration is usually the one with the least to move. Steps 3 and 4 do more to control cost than anything else.
Planning for Microsoft 365 Copilot?
Copilot can surface anything a user already has access to in Microsoft 365. That makes a migration the right moment to fix permissions, because files that were hard to find on an old server become easy to find with AI.
- Copilot readiness. We review permissions before Microsoft 365 Copilot goes live, so it only finds what each person should see.
- AI use policy. We help you set clear rules on approved tools and what data staff can share.
- AI assistants and automations. We build workflow automations and assistants for clients, with access controls in place.
Read more about our AI consulting and automation services or compare Copilot vs ChatGPT.
How CAG helps with cloud migration for small business
Our Perth team in Belmont has 21 years of IT experience, and we’re a Microsoft partner. For cloud projects we handle Microsoft 365 setup and migration, Azure and cloud servers, and cloud backup and recovery. We document each client site’s systems and processes, so your inventory and cutover plan are written down rather than kept in someone’s head.
After the move, our managed IT services include 24/7 monitoring, endpoint detection and response with automatic containment, and Essential Eight assessments, plus help mapping your existing controls to ASD Essentials. Learn more about our cloud computing services, disaster recovery and Microsoft 365 for business.
Perth cloud migration
Still running an old server?
Talk to our team about moving to Microsoft 365 and Azure. We'll review what you have, give each system the right home and set out a plain-English plan.
Your questions answered
Cloud migration for small business: the basics
How long does a small business cloud migration take?
It depends on the number of users, the amount of data and the business software involved. Moving email and files for a small office is often a matter of weeks, including planning and a pilot. Line-of-business software and large, messy file shares add time. A proper inventory gives you a realistic timeline.
Do we still need a server after moving to the cloud?
Often not. Email and files move to Microsoft 365, and many business apps now have a cloud version. Some businesses keep one Azure server for software that still needs Windows, or a small device on site for equipment that has to stay local.
Will our data be stored in Australia?
For Microsoft 365 tenants in the Australian geography, Microsoft stores core data such as mailboxes and SharePoint, OneDrive and Teams content at rest in Australia, although some features handle data differently. For Azure, you choose the region, so pick an Australian one. Your Microsoft 365 admin centre shows where your tenant's data is stored.
Microsoft 365 and Azure questions
Does Microsoft back up our Microsoft 365 data?
Microsoft protects its service against hardware and data-centre failures, and offers some retention and recovery features. However, that isn't a substitute for an independent backup you control. We recommend backing up mailboxes, SharePoint, OneDrive and Teams to a separate service.
Can we keep our existing email addresses?
Yes. Your domain name moves with you. During cutover, your email (MX) records are updated so new mail flows to Exchange Online, and existing mail is copied across beforehand.
What should we do with the old server afterwards?
Keep it read-only for a short period until everyone confirms their data is in place. Then wipe or destroy its drives securely, cancel any licences tied to it and update your documentation. Don't leave it switched on and unpatched.
Sources and further reading
- Microsoft Exchange Team — Support for Exchange Server 2016 and Exchange Server 2019 ends today
- Microsoft — Planning ahead for Windows Server 2016 end of support
- Microsoft Learn — Windows 10 Extended Security Updates
- AWS Prescriptive Guidance — About the migration strategies (7 Rs)
- ASD Blueprint for Secure Cloud — Microsoft 365 tenant residency
- Microsoft Learn — Azure regions list
- Australian Signals Directorate — ASD Essentials
- OAIC — Australian Privacy Principles guidelines (APP 11)
This article is general information, not legal advice. Talk to your IT partner and, where needed, a lawyer about how these points apply to your business. Last reviewed 7 November 2026.

About the author
Blake Parry
Technical Services Manager, The Computing Australia Group
Blake leads the technicians who deliver CAG’s IT services, looking after clients in mining, oil and gas, manufacturing, government and corporate sectors. Because no two environments are alike, he insists every client site is documented to a high standard. His goal is simple: systems that are configured properly, less downtime, and staff who can keep working.