Cloud migration is one of the most consequential infrastructure decisions a Canadian small business makes. Done well, it reduces costs, improves reliability, and gives your team flexibility to work from anywhere. Done poorly, it causes weeks of disruption, data loss risk, and IT costs that exceed the on-premise setup you were trying to escape.
We've migrated dozens of Alberta businesses from on-premise infrastructure to cloud environments. Here's the complete process — including the steps most guides skip.
Before You Migrate: The Three Questions You Must Answer
1. What are you actually migrating to?
"The cloud" is not a destination. It's a category. Azure, AWS, Microsoft 365, Google Workspace, a hosted server with a Canadian data centre — these are all "cloud" in some sense. Before planning a migration, define exactly what services will run where.
For most Alberta SMBs, cloud migration means some combination of:
- Moving email and collaboration to Microsoft 365 or Google Workspace
- Moving file storage to OneDrive/SharePoint or Google Drive
- Moving on-premise business applications (accounting, ERP, CRM) to SaaS equivalents
- Moving servers to Azure, AWS, or a Canadian cloud provider
2. What are your data residency requirements?
Canadian businesses handling personal information have obligations under PIPEDA regarding where data is stored. Healthcare, legal, and government-adjacent organizations often have additional requirements stipulating that data must remain in Canada.
Major cloud providers have Canadian data centres (Microsoft Azure Canada Central in Toronto, Canada East in Quebec; AWS Canada Central in Calgary). Ensure your chosen solution stores data in Canada if that's a requirement.
3. What's your connectivity situation?
Moving everything to the cloud makes you dependent on your internet connection. If your office internet is unreliable or bandwidth-constrained, cloud applications will underperform. Before migrating, assess your connectivity and upgrade if necessary. A 100Mbps symmetrical fibre connection is the minimum for a 20+ person office running cloud applications.
Phase 1: Discovery and Assessment
Before touching anything, document everything.
Infrastructure inventory: Every server (physical and virtual), every network device, every application, every service. What version is it? Who manages it? Who depends on it? What data does it store?
Application dependency mapping: Applications rarely operate in isolation. Your accounting software queries your customer database. Your file server is referenced by your email system. Moving one component without understanding its dependencies breaks others.
Data classification: Not all data should be treated the same. Client contracts require different handling than marketing collateral. Classify your data before migration — this affects how you structure access controls and retention policies in the cloud.
Connectivity assessment: Current bandwidth utilization, peak usage periods, current ISP contract terms, and whether your internet connection is resilient enough for cloud dependency.
Cost modelling: Cloud isn't always cheaper than on-premise, particularly at scale. Build a total cost model comparing current on-premise costs (hardware depreciation, power, cooling, IT management time, software licensing) against projected cloud costs.
Phase 2: Design the Target Architecture
Based on your assessment, design what your cloud environment will look like:
Identity and access management: How will users authenticate? Azure Active Directory (Entra ID) is the standard for Microsoft environments. Single sign-on across applications saves time and reduces security risk from password proliferation.
Network architecture: Will you use Azure Virtual Network? AWS VPC? How will on-premise systems that you're keeping connect to cloud resources? A site-to-site VPN or ExpressRoute connection maintains secure connectivity between your office and cloud environment.
Security controls: Define your security baseline before migration, not after. Conditional access policies, multi-factor authentication enforcement, data loss prevention policies, and endpoint management configuration all need to be established in the target environment before data moves in.
Backup and recovery: Where will cloud data be backed up? At what frequency? What's the retention period? Test the restore process before you need it.
Phase 3: Pilot Migration
Never migrate everything at once. Start with a pilot group of 5–10 non-critical users and validate the migration process before committing the organization.
Pilot selection: Choose users who are technically comfortable and whose work is not on a critical deadline during the migration window. Avoid the CEO for the pilot.
Pilot scope: Migrate email, calendar, contacts, and a defined set of files. Validate that everything works as expected over 1–2 weeks of real usage.
Issue identification: Document every issue the pilot group encounters. Distinguish between configuration issues (solvable before full migration) and platform limitations (require a different approach or user acceptance).
Phase 4: Full Migration
With a validated process and resolved pilot issues, proceed to full migration in waves:
Wave structure: Migrate teams or departments together rather than random individuals. An entire accounting team migrating together means they can help each other through the transition.
Migration windows: Schedule migrations during low-activity periods. Friday evening migrations allow the weekend for settling before Monday's workload.
Communication: Over-communicate the migration timeline. Users who know what's changing and when are far less disrupted than those who arrive Monday morning to a different system.
Cutover approach: Dual-run critical systems where possible — keeping old and new environments available simultaneously for a defined period reduces the risk of a hard cutover.
Phase 5: Decommission and Optimize
After a successful migration, the on-premise environment doesn't immediately disappear:
Validation period: Run both environments in parallel for 30–60 days. Validate that nothing critical is missing or broken. Confirm that data is complete and accessible.
Decommission planning: Identify the order in which on-premise systems can be safely shut down. Start with the lowest-risk systems.
Cost optimization: Cloud environments have a tendency to drift expensive. Unused resources continue to bill. Oversized virtual machines run 24/7 when they don't need to. A cloud optimization review 90 days post-migration typically identifies 20–35% cost savings.
Ongoing management: Cloud environments require ongoing management — patching, security monitoring, cost management, and governance. This doesn't go away just because you moved off-premise.
Canadian Data Sovereignty: What You Need to Know
Under PIPEDA, organizations must ensure that personal information transferred to third-party processors (including cloud providers) receives equivalent protection. This doesn't prohibit using US cloud providers, but it requires due diligence — reviewed data processing agreements, understanding of where data is actually stored, and vendor security practices.
For organizations with stricter requirements, options include:
- Azure Canada Central/East: Microsoft's Canadian data centres store data in Canada by default for most services
- AWS Canada (Calgary): Amazon's Canadian region
- Canadian cloud providers: Companies like Aptum, Beanfield, and TELUS offer Canadian-only cloud hosting
Cleva IT helps clients navigate data residency requirements as part of every migration engagement.
What Migration Costs
For transparency, here are realistic cost ranges for Alberta SMB migrations:
- Email migration (Microsoft 365, 25 users): $3,000–$6,000 professional services
- File server migration (25 users, 500GB data): $2,500–$5,000
- Server virtualization and lift-and-shift to Azure: $8,000–$25,000 depending on complexity
- Full application stack migration (including SaaS transitions): $15,000–$60,000
These costs are offset by eliminated hardware refresh, reduced on-premise IT management costs, and improved reliability — typically achieving payback within 2–3 years.
Cleva IT provides end-to-end cloud migration services for Alberta businesses, from assessment through decommission. Contact us for a free migration assessment and cost model for your environment.