Choosing where business systems run
Compare cloud and on-site options for each business workload, including dependencies, support, recovery and Canadian privacy requirements.

Email, an accounting application and a system controlling equipment can have very different hosting needs. Decide where each workload should run by examining the work it supports, its dependencies and the people who’ll maintain it.
A hybrid arrangement connects systems running in cloud services with systems on local or private infrastructure. It can be useful when those systems need different locations. It also leaves you responsible for the connections and for operating more than one environment.
Map the complete workload
List the application, database, file storage, identity service, integrations and backup. Record the owner, users, supported versions and licensing restrictions. Ask the supplier which hosting arrangements it supports.
Then trace a normal transaction. Does an on-site application make repeated calls to a database? Does a cloud service need the office directory to sign people in? Which functions stop if the internet connection fails?
Microsoft’s migration-planning guidance uses dependency groups to plan which components move together. Apply that idea before moving one part of a closely connected system. Test the entire transaction, including busy periods and large files.
Compare the costs of operating each option
For on-site infrastructure, include replacement equipment, power, licensing, maintenance, backup and the staff or provider time needed to keep it supported. For cloud hosting, include compute, storage, transfers, support, recovery and management.
Count migration work and any period when both environments must run. Use a comparable service level and recovery requirement for each estimate. An inexpensive server with no tested recovery isn’t equivalent to a service designed to meet a documented recovery target.
Use the cloud-cost review to check current charges. Keep the placement decision separate from cleanup you could perform without moving the application.
Check where information goes
Record primary storage, backup locations, support access and any management or monitoring data sent to another service. Selecting a Canadian region doesn’t answer all of those questions.
Under the OPC’s PIPEDA cross-border guidance, transfers for processing aren’t generally prohibited, and the organization remains accountable for protecting the information. Provincial, sector and contractual requirements can add obligations. Check the rules that apply to your records and customers before committing to a location.
Document the provider’s terms and the safeguards required for the information involved. Hosting on your own premises still requires access controls, protection and recovery.
Test the connections and recovery
For a proposed hybrid arrangement, test interrupted connectivity, identity service failure and restoration of the data the application needs. Record which functions remain available and which require a manual workaround.
Having components in two locations won’t give you failover on its own. Moving work between them needs a supported design, usable data and a tested recovery process. Confirm who owns patching, connection failures, monitoring and incident response across the boundary.
Write down the decision and its review trigger
Keep a short decision record: requirements, options considered, costs, test results, responsibilities and the reason for the chosen placement. Set review triggers such as a vendor support deadline, a major workload change or a hosting renewal.
Before signing, also check whether you can export and use your data independently. Talk to us if you need help comparing hosting options and mapping the dependencies that affect a move.


