Out of the server room,
into something maintainable.
Whether the goal is full cloud, hybrid, or just retiring one aging server, we plan the migration, run the cutover, and operate the result. Azure, M365, hosted SQL, file shares, and line-of-business apps.
Everything you need, none of the upsell.
Real deliverables, with the boundaries written down. So you know what you're paying for and what counts as extra.
VMs as-is, in Azure.
Fastest path for legacy apps that can't be rebuilt. Right-sized, monitored, and budget-capped.
SQL, IIS, file shares.
Move workloads to managed PaaS where it makes sense. Lower ongoing maintenance, better security.
Some on-prem, some cloud.
Not everything belongs in the cloud. We design and operate the hybrid so it doesn't become two messes.
Decommission and document.
Old hardware off the floor, licensing rationalized, secure destruction certificates filed.
The order we work in.
A clear sequence so you can budget time, money, and risk against the work.
Inventory.
Every server, app, file share, integration, and dependency catalogued. Surprises eliminated.
Design.
Target architecture, cost estimate, cutover plan. You see and approve before we order anything.
Migrate.
Phased moves with parallel running where possible. Documented rollback for every step.
Operate.
Hand off to managed service or to your team with full documentation. We don't disappear at go-live.
Get a quote on cloud migration.
Tell us a bit about your environment and we'll come back with a scoped proposal in two business days. No obligation, no pressure.
Request a Quote Back to Cloud & InfraGetting out of the server room without losing what's running in it.
A cloud migration is the process of moving workloads that currently run on physical hardware in your office (or a colocation facility) to cloud infrastructure maintained by Microsoft, Amazon, or Google. The objective is not to move to the cloud because cloud is a trend. The objective is to reduce the operational burden of maintaining on-premises hardware, improve availability and disaster recovery capability, and enable staff to work effectively from anywhere. For most BC and Alberta SMBs, that means moving file shares to SharePoint or Azure Files, moving email to Exchange Online if it is not there already, and retiring one or more ageing Windows Server systems that are consuming IT budget and generating risk.
A Prince George engineering firm running its project files on a physical file server in a back room is also running the risk that the server fails, the drives fail, or the building floods. Moving those files to SharePoint or Azure Files eliminates the hardware risk, adds built-in versioning, and lets staff access files from the field on an iPad without VPN complexity. The migration involves mapping what is on the server, choosing the right cloud destination for each workload, migrating the data with minimal downtime, and decommissioning the hardware once the migration is verified. North Star plans and executes all of that, including the Canadian data residency considerations under BC PIPA and PIPEDA that determine where your data must actually live.
Cloud migration deliverables.
- Discovery and inventory: complete inventory of what is currently running on-premises, including servers, services, applications, databases, and file shares, with dependency mapping.
- Migration strategy: recommendation for each workload: lift-and-shift to Azure IaaS, replatform to PaaS, replace with SaaS (M365, Dropbox Business), or retire. Written rationale for each recommendation.
- Data residency planning: all Canadian data residency requirements assessed under BC PIPA and PIPEDA. Azure Canada regions (Canada Central, Canada East) used by default for data that must stay in Canada.
- Microsoft 365 migration: email migration from Exchange on-premises or Google Workspace to Exchange Online, including calendar and contact migration and cutover coordination.
- File share migration: migration of on-premises file shares to SharePoint document libraries or Azure Files, with permissions mapping and user communication.
- Application migration or lift-and-shift: Windows Server workloads moved to Azure virtual machines or replaced with equivalent cloud services where applicable.
- Cutover planning: staged migration with a defined cutover window, rollback plan, and user communication. Most migrations complete over a weekend to minimize business disruption.
- Post-migration validation: confirmation that all users can access their data and applications, that backup is configured for the new cloud workloads, and that the old hardware is safely decommissioned.
Businesses with ageing on-premises infrastructure or a hardware refresh coming up.
The right time to evaluate a cloud migration is when on-premises hardware is approaching end of life and a hardware refresh is on the horizon. Instead of spending $20,000-$40,000 on a new server with a five-year depreciation schedule, the question is whether the workloads that server runs are better placed in Azure, in Microsoft 365, or in a hybrid configuration where latency-sensitive applications stay local and everything else moves to the cloud. North Star evaluates both options honestly: sometimes the right answer is a hardware refresh, sometimes it is migration, and sometimes it is a hybrid. We do not push cloud migration when on-premises makes more sense for the workload.
BC and Alberta businesses with compliance obligations under BC PIPA or PIPEDA need to understand where their data will be stored before migrating to the cloud. Cloud providers that store data exclusively in the United States subject Canadian personal information to US law, including the CLOUD Act. Microsoft Azure's Canadian regions store data in Canada and are the appropriate choice for BC and AB businesses handling client personal information. North Star configures all migrations to use Canadian Azure regions by default.
Businesses with multiple BC or AB locations that currently rely on site-to-site VPN to reach a central server are often better candidates for cloud migration than single-site businesses, because moving the workload to the cloud eliminates the VPN dependency and typically improves performance for remote and secondary-site staff.
Fixed-price project scoped after discovery.
Cloud migrations are scoped and priced as a fixed-price project after a discovery engagement that assesses what is on-premises and what the cloud destination will be. The discovery is typically a short paid engagement (a few hours of technical review), and the migration project is then quoted with a fixed price and a defined timeline. Ongoing cloud infrastructure costs (Azure subscription, Microsoft 365 licensing) are separate from North Star's project fee and are billed directly by Microsoft. Contact us to schedule a discovery call and receive a migration scoping proposal.
What clients ask before migrating.
Will our line-of-business applications work in Azure?
It depends on the application. Most modern Windows Server applications run correctly on Azure virtual machines. Legacy applications with hardware dependencies (dongles, specific network drivers, serial port devices) may have complications. We assess each application during the discovery phase and identify any that require remediation before migration. Applications that vendors no longer support on cloud infrastructure are flagged and alternatives are recommended before the migration begins, not during it.
Where will our data be stored?
By default, North Star configures all Azure migrations to use Microsoft's Canada Central region in Toronto or Canada East region in Quebec City. These regions store data in Canada, which satisfies the data residency requirements under BC PIPA, AB PIPA, and PIPEDA for personal information. Microsoft 365 data for Canadian tenants is also stored in Canada by default. We document the data residency configuration in writing so you have a record for regulatory or audit purposes.
How much downtime is involved?
We design migrations to minimize downtime. File share migrations run in parallel with your existing server; staff are moved to the new location in waves, not all at once. Email migrations typically have a cutover window of a few hours. Server workloads can often run in parallel (old server and new Azure VM) until validation is complete. We plan a defined rollback procedure so that if anything does not work as expected after cutover, we can revert to the previous state with minimal additional disruption. Most migrations complete over a scheduled weekend.
What happens to the old hardware after migration?
After migration is complete and validated, we coordinate decommissioning of on-premises hardware. This includes secure data wiping of storage drives to NIST 800-88 standards, coordination with a certified electronics recycler for hardware disposal, and documentation confirming that all data has been wiped before the hardware leaves your premises. We do not leave decommissioning as a loose end for you to manage after the migration project closes.
Cloud migrations with Canadian data residency built in from the start.
North Star is headquartered in Prince George and serves BC, Alberta, and the Yukon. We migrate businesses to Azure and Microsoft 365 with Canadian data residency as a default, not an afterthought. We understand that BC PIPA and PIPEDA impose real obligations on how personal information is handled in the cloud, and we configure migrations to satisfy those requirements rather than explaining them after the fact. We use AI-assisted tooling to accelerate the discovery and inventory phases, giving you a faster and more complete picture of what you are migrating before the project starts. After migration, the cloud workloads are managed as part of your ongoing managed IT services agreement.
Cloud migration across BC, Alberta, and Yukon.
Pick your city for local pricing, response windows, and recent project notes.
- Cloud migration in 100 Mile House
- Cloud migration in Abbotsford
- Cloud migration in Airdrie
- Cloud migration in Brooks
- Cloud migration in Burnaby
- Cloud migration in Calgary
- Cloud migration in Campbell River
- Cloud migration in Camrose
- Cloud migration in Canmore
- Cloud migration in Carmacks
- Cloud migration in Chilliwack
- Cloud migration in Cochrane
- Cloud migration in Cold Lake
- Cloud migration in Coquitlam
- Cloud migration in Courtenay
- Cloud migration in Cranbrook
- Cloud migration in Dawson City
- Cloud migration in Dawson Creek
- Cloud migration in Drayton Valley
- Cloud migration in Edmonton
- Cloud migration in Edson
- Cloud migration in Fernie
- Cloud migration in Fort Mcmurray
- Cloud migration in Fort St John
- Cloud migration in Grande Prairie
- Cloud migration in Haines Junction
- Cloud migration in High River
- Cloud migration in Hinton
- Cloud migration in Kamloops
- Cloud migration in Kelowna
- Cloud migration in Kitimat
- Cloud migration in Lacombe
- Cloud migration in Langley
- Cloud migration in Leduc
- Cloud migration in Lethbridge
- Cloud migration in Lloydminster
- Cloud migration in Mayo
- Cloud migration in Medicine Hat
- Cloud migration in Nanaimo
- Cloud migration in Nelson
- Cloud migration in Okotoks
- Cloud migration in Penticton
- Cloud migration in Powell River
- Cloud migration in Prince George
- Cloud migration in Prince Rupert
- Cloud migration in Quesnel
- Cloud migration in Red Deer
- Cloud migration in Richmond
- Cloud migration in Salmon Arm
- Cloud migration in Sherwood Park
- Cloud migration in Smithers
- Cloud migration in Spruce Grove
- Cloud migration in Squamish
- Cloud migration in St Albert
- Cloud migration in Stettler
- Cloud migration in Surrey
- Cloud migration in Terrace
- Cloud migration in Vancouver
- Cloud migration in Vernon
- Cloud migration in Victoria
- Cloud migration in Watson Lake
- Cloud migration in Wetaskiwin
- Cloud migration in Whistler
- Cloud migration in Whitehorse
- Cloud migration in Williams Lake