Since 2015, InsmartTech has been Surrey’s trusted managed IT and cybersecurity partner — real people, fast support, and security that fits how small businesses actually operate.

 

Contacts

sales@insmarttech.ca

(604) 449-2327

IT Tips
Moving to Microsoft 365: A Migration Guide for BC Businesses

Moving to Microsoft 365: A Migration Guide for BC Businesses

A Microsoft 365 migration is the process of moving a business’s email, files and collaboration tools from an existing system — an on-premise Exchange server, Google Workspace, or a collection of local drives — into Microsoft’s cloud platform. Done properly it takes days of planning and a few hours of cutover. Done badly it produces weeks of missing email and staff who quietly go back to their old habits.

This guide covers what actually matters when moving a small or mid-sized business in British Columbia onto Microsoft 365.

Decide what you are actually moving

“Moving to Microsoft 365” means different things depending on where you are starting from. The three common situations:

  • From an on-premise Exchange server. Mailboxes, calendars and contacts move to Exchange Online. This is the most involved scenario and usually the most worthwhile, because it removes a server you are maintaining.
  • From Google Workspace. Mail and calendar migrate reasonably cleanly. Shared Drives need more planning, because the permission models are genuinely different.
  • From local drives and a mix of consumer accounts. The most common situation in smaller businesses, and the one where the real benefit is structure rather than technology.

Choose your licences before you start, not after

Microsoft’s licensing is the part most businesses get wrong, and it is expensive to fix later. The practical difference for most BC businesses comes down to Business Basic, Business Standard and Business Premium.

Business Basic gives you cloud services without desktop Office applications. Business Standard adds the installed Office apps. Business Premium adds the security and device management layer — and for any business handling client or patient data, that layer is usually the reason to be on Microsoft 365 at all.

Mixing licence types across a team is normal and often sensible. A warehouse user who needs email but not Excel does not need the same licence as your accountant.

Plan the migration in this order

1. Audit what exists

Before touching anything, document every mailbox, every shared folder, how much data each holds, and who actually uses what. Businesses routinely discover mailboxes belonging to people who left years ago, and shared folders nobody has opened since 2019. Migrating that is wasted effort.

2. Sort out your domain and DNS

Your domain needs to be verified in Microsoft 365 before mail can flow. This is also the point to get SPF, DKIM and DMARC records right. Skipping these is the single most common reason a business’s email starts landing in spam folders after a migration.

3. Migrate data before cutover

Mail and files should be copied across while the old system is still live. Staff keep working normally, and the final cutover moves only what changed since the copy. A migration that requires everyone to stop working for a weekend has usually been planned badly.

4. Cut over at a sensible time

DNS changes take time to propagate. Plan the switch for a Friday evening or a quiet period, not Monday morning, and keep the old system running in parallel for a short period rather than deleting it immediately.

5. Secure it before you hand it over

A new Microsoft 365 tenant is not secure by default. Multi-factor authentication should be enforced on every account, not offered as an option. Conditional access rules, audit logging and Microsoft security configuration belong in the migration project, not on a list for later.

What usually goes wrong

  • Shared mailboxes converted to user accounts. A shared mailbox does not need a licence. Businesses often end up paying for several that should have cost nothing.
  • Files moved without deciding where they belong. OneDrive is for individual work. SharePoint is for shared company files. Dumping everything into OneDrive means the data leaves with the employee.
  • Permissions rebuilt by guesswork. Old folder permissions are rarely documented. Recreating them from memory usually means someone ends up with access they should not have.
  • No training. Staff who are not shown how Microsoft Teams and SharePoint are meant to work will email attachments to each other exactly as before, and you will have paid for nothing.
  • Email authentication left incomplete. Without correct SPF, DKIM and DMARC, your outbound mail deliverability suffers and your domain becomes easier to spoof.

How long it takes

For a business of ten to thirty staff with a straightforward setup, expect roughly one to two weeks end to end: a few days of audit and planning, several days of data copying in the background, a cutover evening, and a week of settling in afterwards.

The variables that extend it are data volume, the number of shared folders with complicated permissions, and any line-of-business software that connects to email. That last one is worth checking early — accounting packages, CRMs and scanning devices often need reconfiguring, and discovering that on cutover night is unpleasant.

After the migration

Microsoft 365 is not a system you configure once. Licences drift as people join and leave, guest accounts accumulate, and security settings that were correct at launch fall behind Microsoft’s own recommendations within a year.

A quarterly review of licence assignment, guest access and security configuration keeps the platform doing what you are paying for. Most businesses either build that into their managed IT services arrangement or find that nobody does it at all.

Is it worth it?

For most BC businesses still running an on-premise mail server, yes — largely because you stop maintaining hardware, and because the security tooling available in Microsoft 365 is considerably better than what a small business can build alone.

For businesses already using cloud email informally, the value is structure: knowing where files live, who can reach them, and what happens when someone leaves.

Insmart Technology handles Microsoft 365 migrations for businesses across Surrey and Vancouver, including licensing review, data migration and security configuration. If you are considering a move, a free IT assessment will tell you what is involved for your specific setup.

About the author: Naqash Bin Iqbal is an SEO Specialist at Insmart Technology, a Surrey-based managed IT and cybersecurity provider.

Naqash Bin Iqbal - Insmart Technology

Author

Naqash Bin Iqbal