Microsoft 365 Migrations for Perth Businesses: What to Expect

Every week, we talk to Perth business owners who know they need to move to Microsoft 365 but are putting it off because the idea of migrating email and files sounds like a nightmare.

We get it. You've heard the horror stories. Emails going missing, three days of downtime, staff who can't log in, contacts that vanished. Those things happen when migrations are done badly. They don't have to happen at all.

Here's an honest breakdown of what a Microsoft 365 migration actually involves, how long it takes, what it costs, and the mistakes that cause problems.

What are you migrating from?

The migration process depends entirely on where you're starting. Here's what we see most often with Perth businesses:

Google Workspace to Microsoft 365

Effort level: Medium

This is one of the most common migrations we do. Google Workspace is solid, but many Perth businesses switch because their clients and partners are on Microsoft, or because they need features like Intune device management, Conditional Access, or Defender for Business.

What moves: email, contacts, calendars, Google Drive files into OneDrive/SharePoint.

The tricky bit: Google Drive folder structures don't always translate cleanly to SharePoint. We map the structure beforehand and clean it up during migration, not after.

GoDaddy / cPanel / Telstra email to Microsoft 365

Effort level: Low to Medium

Basic email hosting with no collaboration tools. The migration itself is straightforward. IMAP migration pulls across email history. The bigger value is what you gain: professional email, Teams, file sharing, and security features you didn't have before.

The tricky bit: Some older hosts limit the size of email that can be migrated in one batch, so large mailboxes need to be handled carefully to avoid timeouts.

On-premises Exchange to Microsoft 365

Effort level: High

Still have a physical server running Exchange in your office or server room? This is the most complex migration type, but also the most impactful. You're eliminating hardware, reducing risk, and moving to a platform that Microsoft manages and secures.

The tricky bit: Hybrid configurations, legacy applications that depend on on-premises Exchange (fax servers, CRM integrations, legacy LOB apps), and decommissioning the old server properly.

Another M365 tenant to your own M365 tenant

Effort level: Medium

This happens when a business was set up under a previous IT provider's tenant, a franchise arrangement, or a parent company. You need your own tenant that you control.

The tricky bit: Tenant-to-tenant migrations require careful planning around domain ownership, licence timing, and user communication.

The migration timeline

Here's what a typical migration looks like for a 10-30 user Perth business:

Week 1: Discovery and planning

• Audit your current email setup. How many mailboxes, how much data, any shared mailboxes or distribution lists.
• Map your file structure. What moves to OneDrive (personal files), what moves to SharePoint (shared team files).
• Choose the right M365 licence plan.
• Set up the new M365 tenant and verify your domain.
• Create user accounts and configure security baseline (MFA, admin separation).

Week 2: Pre-migration

• Begin background email sync. A tool copies your email history to the new mailboxes while your old system stays live. Your team keeps working normally.
• Migrate files to OneDrive and SharePoint.
• Set up Teams channels and configure policies.
• Prepare DNS records for cutover.

Week 3: Cutover weekend

• Friday evening or Saturday morning: switch DNS (MX records) to point to Microsoft 365.
• Complete final email sync. Any emails received since the background sync are brought across.
• Test send/receive from external addresses.
• Configure Outlook, Teams, and OneDrive on all devices.
• Quick staff briefing on Monday morning: "Here's what's changed, here's how to access everything."

Week 4: Stabilisation and cleanup

• Monitor for any delivery issues, calendar sync problems, or missing contacts.
• Decommission old email hosting.
• Configure Defender, DLP, and Conditional Access.
• Staff training session (1-2 hours).
• Handover documentation.

Total calendar time: 3-4 weeks. Total disruption to your team: close to zero if done properly.

What a migration costs in Perth

These are fixed-price project quotes, not hourly estimates that blow out. The cost includes planning, migration, device setup, basic training, and a stabilisation period after cutover.

Microsoft 365 licences are separate and ongoing. Business Basic from ~$9/user/month, Business Standard from ~$19/user/month, Business Premium from ~$33/user/month.

The mistakes that cause pain

1. Cutting over on a Monday morning

Never. Always cut over on a Friday evening or Saturday. This gives you the entire weekend to resolve any DNS propagation delays, test mail flow, and sort out device configurations before your team starts work on Monday.

2. Not doing a background pre-sync

If you try to move 50GB of email in one hit on cutover night, you'll be waiting until Sunday. A background sync running for a week beforehand means the final cutover only needs to move 24-48 hours of new email, which takes minutes, not hours.

3. Forgetting about shared mailboxes and distribution lists

The personal mailboxes get migrated but nobody thought about info@, accounts@, or the six distribution lists that route emails to different teams. These need to be recreated in M365 and tested before cutover.

4. Not updating app passwords

Staff who use email on their phone, in a desktop app, or in an accounting package will need to re-authenticate after migration. If you don't communicate this clearly, you'll get 20 phone calls on Monday morning from people who can't send email.

5. Leaving the old system running

After migration, the old hosting account needs to be cancelled. We've seen businesses paying for both their old email hosting and Microsoft 365 for over a year because nobody remembered to cancel the old one.

6. Skipping security hardening

The migration is done, everyone can send and receive email, and the project is "complete." Except MFA isn't on, sharing is wide open, there's no backup, and the admin account has the same password as the business owner's LinkedIn. The migration is the beginning, not the end.

What about our files?

File migration is often the part businesses worry about most, and for good reason. Messy file structures have a way of multiplying when they move to a new platform.

Our approach:

1. Audit first. We look at what you have (local drives, network shares, Dropbox, Google Drive, USB sticks) and map out the current state.
2. Design the structure. We propose a SharePoint and OneDrive structure that makes sense for your business. Team files go to SharePoint. Personal work-in-progress goes to OneDrive.
3. Clean as you go. Migration is the perfect time to archive old files, delete duplicates, and establish naming conventions. Moving the mess to a new location just gives you the same mess in a different place.
4. Set permissions. Not everyone needs access to everything. We set up SharePoint libraries with appropriate permissions. Finance files for the finance team, HR files for HR, project files for project teams.

Should you do it yourself?

If you have fewer than 5 users, no existing email history to migrate, and you're comfortable with DNS configuration, you can set up Microsoft 365 yourself. Microsoft's setup wizard is reasonably good.

For anything involving email migration, file migration, device setup, or security configuration, it's worth engaging a specialist. The cost of a properly managed migration is a fraction of the cost of fixing a botched one, and the productivity loss from even a single day of email disruption is significant.

How we can help

We've done Microsoft 365 migrations for businesses across Perth, from 3-person startups to 150-person professional services firms. Every migration gets:

• A dedicated project manager
• A fixed-price quote before we start
• Weekend cutover with near-zero disruption
• Post-migration support and training
• Full documentation of your new setup

Book a free migration consultation →

Or start with our free IT Health Check quiz to see where your current technology setup stands.

Learn more about our Microsoft 365 services →

A Dark Cloud Creative is a Perth-based technology consultancy specialising in Microsoft 365 migrations, security hardening, and managed M365 support for small businesses and growing teams across the Perth metro area.