Kyndryl Cloud Uplift Debuts in Canada: Move IBM Power Workloads to Azure Securely

Kyndryl’s new availability of Cloud Uplift inside Microsoft’s Canadian datacentre regions delivers a practical, low‑risk route for Canadian enterprises to lift, run, and begin modernizing mission‑critical IBM Power workloads on Microsoft Azure while keeping data and primary compute inside Canada.

Background / Overview​

Kyndryl announced on March 11, 2026 that Kyndryl Cloud Uplift (the rebranded Skytap offering) is now offered in Microsoft Azure’s Canadian datacentre regions, positioning the service as a fast, self‑serve way to move as‑is IBM Power workloads (AIX, IBM i, Linux) to Azure without the mandatory re‑architecture or code rewrite that typically stalls modernization projects. The company frames the capability as a way to preserve operational continuity while giving organizations a controlled path to modern cloud services and AI.
This launch follows Kyndryl’s acquisition of Skytap in May 2024, a move the company has used to build a managed offering that places Power‑class hardware and partitioning (LPAR) support into hyperscaler datacentres. Kyndryl says Canada is the fifth geographic region to receive Cloud Uplift since the acquisition and the fourteenth Microsoft datacentre region where the solution is available.
Why this matters now: Kyndryl’s recent Readiness Report and associated market messaging highlight two persistent constraints in enterprise cloud adoption—foundational technical debt that delays innovation, and rising concerns about geopolitical and regulatory risk tied to where data and compute live. These pressures make a “sovereign‑region” hybrid option attractive for regulated workloads that are expensive or risky to refactor all at once. That broader context underpins Kyndryl’s Canada push. (kyndryl.com)

---

What Kyndryl Cloud Uplift actually offers​

Core capabilities, in plain terms​

• Run IBM Power workloads on Azure without rewriting: Customers can replicate and run existing AIX, IBM i and Power Linux LPARs inside Azure, preserving binaries, middleware and operational procedures.
• Local data residency in Canada: Primary compute and storage can remain within Microsoft Canadian datacentre regions to meet legal and procurement requirements.
• Self‑service, metered consumption backed by Kyndryl: The offering is presented as a self‑service platform with managed options and a 99.95% availability SLA where supported.
• Bridge to Azure PaaS and AI services: Once workloads are running in Azure regions, teams can incrementally access analytics, AI/ML, and modern database services without wholesale migration of the legacy app stack.

How it compares with the alternatives​

The important distinction is that Cloud Uplift aims to place native Power hardware and PowerVM capabilities into the hyperscaler fabric so that LPARs can be managed in ways that closely resemble on‑prem operations. That is different from full refactors, containerization strategies, or rehosting on non‑Power platforms where significant code changes are usually required. Industry materials and IBM technical guidance indicate that running AIX/IBM i on actual Power hardware preserves expected behavior (PowerVM, LPAR, live mobility, PowerHA), which is central to the Cloud Uplift proposition.

---

Technical mechanics — what’s happening under the hood​

Hardware and virtualization model​

Cloud Uplift places IBM Power servers (Power10 and related platforms in modern deployments) into Azure racks and exposes partitioning and virtualization layers (PowerVM / PHYP) to Kyndryl tenants. That allows:

• familiar LPAR management (creation, sizing, Live Partition Mobility),
• standard Power virtualization features (SPPs, VIOS) and
• binary compatibility for heavyweight workloads that expect Power architecture.

Because these are real Power systems (not emulation), operating systems and middleware that are certified for Power remain functional, which reduces application‑level regressions during migration.

Networking, storage and integration​

Kyndryl integrates Power LPARs with Azure networking fabrics and storage primitives. Expect secure overlay connectivity to tenant VNets, private link or ExpressRoute equivalents for on‑prem connectivity, and block/file storage mapped to Azure storage backends. The success of high‑IO workloads will hinge on careful architecture to guarantee IOPS, throughput and latency comparable to on‑prem designs.

Identity, monitoring and operational tooling​

The managed platform ties legacy admin models into Azure’s monitoring, backup and identity systems, enabling operators to retain established processes while granting product teams gradual access to Azure observability and governance tooling. The degree of integration—how far identity bridges, API mappings, and operational runbooks are automated—will materially affect cutover complexity.

---

Business case for Canadian enterprises​

Immediate benefits​

• Reduced migration risk — moving as‑is minimizes functional regressions, shortens migration timelines and avoids expensive, error‑prone code rewrites.
• Regulatory alignment — keeping compute and primary data inside Canada eases compliance for federal/provincial rules and procurement contracts that require local hosting or restrict foreign data flows.
• Operational continuity — existing OS images, batch jobs and scheduled windows can be preserved, reducing retraining and operational churn.
• Faster access to cloud services — once hosted in Azure Canada, teams can incrementally adopt cloud‑native services and AI capabilities without wholesale refactoring.

Where value compounds over time​

• Decommissioning on‑prem datacentres and related capital/operational costs.
• Phased modernization: technical debt reduction can proceed module by module while production stays stable.
• New analytics and AI opportunities: secure pathways to combine legacy data with Azure ML and analytics in a controlled way.

---

Compliance, data residency and the regulatory calculus​

Canada’s evolving privacy and procurement landscape makes regional hosting attractive for many sectors—financial services, health, utilities and government—where data residency directly impacts legal compliance and vendor selection.

• Data residency reduces one class of regulatory risk (location), but does not eliminate responsibilities around access controls, encryption, audit trails, and cross‑border replication choices. Kyndryl’s messaging emphasizes in‑country hosting as a differentiator but customers must still validate controls and contractual terms.
• For some organizations, secondary copies (backups, DR replicas) or integration points that touch non‑Canadian services may still raise sovereignty questions and require additional mitigations or contractual clauses.

Bottom line: Cloud Uplift materially simplifies the “where” question, but not the broader “how” of compliance.

---

Risks, caveats and the hidden costs​

No single migration path is free from tradeoffs. IT leaders should weigh these practical and strategic risks before committing to Cloud Uplift.

1) Time and cost of running specialized hardware in a hyperscaler​

While lift‑and‑shift avoids immediate refactoring costs, specialized Power hardware in a managed hyperscaler footprint carries a higher unit compute cost than commodity x86 instances. Over time, these operating costs can outpace the benefits if modernization stalls. Organizations should run a multi‑year TCO analysis that explicitly models sustained Power capacity needs versus eventual refactor savings.

2) Licensing complexity and vendor interop​

Running IBM software (AIX, IBM i, DB2, PowerVM features) in a hyperscaler may trigger complex licensing or support conversations with IBM and other ISVs. While many customers rehost to IBM’s own Power Virtual Server on IBM Cloud, third‑party managed arrangements require explicit license compliance and vendor support agreements. This is an area that must be validated contractually before go‑live.

3) Potential vendor lock‑in and migration inertia​

Preserving legacy stacks as‑is is valuable for risk reduction, but it can also entrench legacy architecture and delay long‑term modernization. Success requires a governance model that mandates staged refactor or replacement, not indefinite permanence in the managed Power environment.

4) Performance and operational SLAs​

Mission‑critical workloads demand predictable performance (IOPS, latency) and HA semantics. Kyndryl advertises availability SLAs, but customers must validate performance envelopes with production‑like load tests and ensure runbooks for incident management align with existing RTO/RPO expectations.

5) Security posture and shared responsibility​

A managed service in a hyperscaler still requires careful configuration: network segmentation, identity governance, privileged access controls, and monitoring need to be explicitly documented. Any misalignment between Kyndryl, Microsoft, and the customer on responsibilities creates gaps that adversaries can exploit.

---

How to evaluate Cloud Uplift: a practical checklist for IT leaders​

Use this numbered checklist as a pragmatic decision tool when assessing Cloud Uplift for IBM Power workloads.

• Define the scope: list applications, integrations, data flows, and compliance controls that must remain in‑country.
• Confirm licensing & support: obtain written confirmation from IBM (or relevant ISVs) on support and licensing when running in Kyndryl’s managed environment.
• Run a performance validation: execute production‑scale load tests for CPU, memory, I/O and network from the Azure Canada target region.
• Map backup & DR strategy: confirm RTO/RPO guarantees and the geography of replicas—ensure secondaries don’t violate residency requirements.
• Security review: perform a joint architecture review (customer, Kyndryl, Microsoft) focused on identity, encryption, segmentation and incident response.
• TCO over 3–5 years: model managed Power costs, network egress, modernization staffing and eventual replacement costs.
• Modernization roadmap: establish phased refactor goals (what to replace, when) with measurable milestones to avoid indefinite rehosting.
• Contractual SLAs: codify operational, compliance and support SLAs, with remedies and audit rights.
• Skills & runbooks: ensure administrators retain required Power skills or arrange for Kyndryl‑delivered runbook transitions.
• Pilot: start with a non‑mission‑critical but representative LPAR to validate the entire stack end‑to‑end before broad migration.

---

Market context and competitive landscape​

Kyndryl’s move to localize Cloud Uplift in Canada is part of a wider industry shift where hyperscalers and large integrators respond to sovereign‑region demand. Similar patterns exist across other cloud providers—offering localized instances, hybrid options, or managed infrastructure that preserves sensitive workloads while exposing cloud innovation.
Competitors and adjacent options include:

• IBM Power Virtual Server on IBM Cloud — IBM’s own public offering for Power workloads, often the default for organizations seeking vendor‑native support.
• Custom colocation + Azure connectivity — organizations sometimes co‑locate Power hardware in a Canadian co‑location facility and connect to Azure for PaaS services.
• Full refactor / modernization — to cloud‑native architectures on x86 and containers, which is often highest‑value long term but carries immediate risk and cost.

Kyndryl’s competitive advantage is its combination of managed services scale, a global Microsoft partnership, and the Skytap‑derived platform that specifically targets the pain point of preserving LPAR‑level fidelity in the hyperscaler footprint.

---

Verifications, inconsistencies and cautions on public claims​

• Kyndryl’s press release and corporate materials assert specific survey statistics about readiness and geopolitical concerns. The March 11 press release cites certain percentages (for example, claims about the share of leaders concerned about geopolitical risks and those changing strategies). Readers should note that the underlying Kyndryl Readiness Report PDF and other Kyndryl materials show closely related but not always identical figures, suggesting numbers may differ across summaries or editions. Always verify the exact phrasing and data source before referencing the statistics in procurement or governance materials.
• The acquisition of Skytap in May 2024 and the subsequent evolution of the product into Kyndryl Cloud Uplift is documented in multiple filings and press statements (Kyndryl press materials, Skytap announcement and SEC filings). These provide the provenance for the product and help explain its technical lineage.
• Technical feasibility of running AIX/IBM i on Power hardware in a managed cloud context is supported by IBM technical guidance and Redbooks describing PowerVM, LPAR mobility and Power Virtual Server patterns; these artifacts demonstrate that the architecture Kyndryl describes is feasible and consistent with IBM’s approach to Power modernization. Still, customers must validate specific firmware, OS and VIOS/PowerVM levels for compatibility with hosted platforms.

---

Practical migration pattern: a recommended phased approach​

• Discovery & profiling (2–6 weeks): inventory Power LPARs, CPU/memory/IO profiles, and integration touchpoints.
• Pilot migration (1–2 months): move a representative non‑critical LPAR to Cloud Uplift Canada to validate connectivity, performance and backup.
• Operational run & modernization plan (3–12 months): run production slices in Cloud Uplift while incrementally extracting services to Azure PaaS when safe.
• Optimization & cost review (ongoing): after initial moves, tune capacity, look for rightsizing or subcapacity licensing opportunities, and commit to modernization milestones.
• Long‑term refactor or replacement (multi‑year): define targeted refactor projects driven by business value, not just technical debt remediation.

This approach balances speed with risk mitigation and provides measurable checkpoints to avoid permanent entrenchment.

---

Closing assessment — strengths, risks, and who should care most​

Kyndryl Cloud Uplift’s availability in Canadian Azure regions is a meaningful development for organizations wrestling with the twin problems of legacy dependence and regulatory constraints. The offering’s big strength is pragmatic: it allows organizations to retire datacentre burdens, maintain in‑country residency, and start consuming cloud services without rewriting mission‑critical applications overnight. That pragmatism is precisely why many large enterprises will take notice.
The key risks remain operational cost, licensing complexity, performance validation, and the political‑commercial dance between Kyndryl, Microsoft, IBM and ISVs. Most importantly, the offering shifts the decision‑point from “how to refactor now” to “how to govern modernization over time.” Without disciplined governance, lift‑and‑shift can become an indefinite state rather than a staging ground for true modernization.
Who should care most:

• CIOs and CTOs in regulated industries (financial services, healthcare, public sector) who need in‑country hosting options now.
• Infrastructure and platform teams managing large IBM Power estates who must reduce datacentre costs while avoiding application risk.
• Procurement and legal teams that must validate licensing and vendor support models before contract commitments.

If you run IBM Power workloads and Canada’s residency or procurement rules have been a migration blocker, Cloud Uplift is a credible, engineered option worth evaluating—provided you enter with a clear plan, contractual protections, and a roadmap that avoids indefinite rehosting.

---

Kyndryl’s Canadian Cloud Uplift is not a silver bullet for legacy modernization, but it is a pragmatic engineering pathway that reframes a stubborn enterprise problem: how to unlock cloud innovation while preserving the integrity of decades‑old, business‑critical systems. For many Canadian organizations the decision will come down to governance: use Cloud Uplift as a controlled runway to modernize and innovate, or let it become a comfortable island that delays the hard work of transforming application logic for the cloud era.

---

Source: Morningstar https://www.morningstar.com/news/pr...n-critical-legacy-systems-on-microsoft-azure/

 

[ChatGPT]

Kyndryl’s announcement that Kyndryl Cloud Uplift (the rebranded Skytap platform) is now available inside Microsoft Azure’s Canadian data center regions marks a practical — and politically timely — turning point for enterprises that still run mission‑critical systems on IBM Power platforms but want to modernize on Azure while keeping data and primary compute inside Canada. The March 11, 2026 announcement positions Cloud Uplift as a low‑risk, self‑serve migration path for AIX, IBM i and Linux workloads running on IBM Power, promising “migrate as‑is” capability, in‑country data residency, and a bridge to Azure‑native services and AI innovation.

Background / Overview​

Kyndryl acquired Skytap in 2024 and has since folded Skytap’s technology into a branded offering now called Kyndryl Cloud Uplift. The acquisition completed in mid‑2024 (announced May 2024) and was explicitly framed as a capability play to accelerate hybrid cloud modernization for legacy, mission‑critical workloads. That strategic intent is now visible in this Canada launch, which Kyndryl says is the fifth geographic expansion of Cloud Uplift and the fourteenth Microsoft datacenter region where the service is offered.
The core proposition is straightforward: replicate and run IBM Power workloads (AIX, IBM i, and Linux on Power) inside Microsoft Azure without refactoring or rewriting applications. By keeping the compute and data inside Microsoft’s Canadian regions, Kyndryl pitches a solution that addresses both technical risk and regulatory/political concerns around cross‑border data flows — issues many Canadian CIOs highlight when planning cloud modernization.

---

Why Canada matters: data residency, regulation and enterprise risk​

Canada has been an active market for cloud hyperscalers for years, with Azure operating Canada Central (Toronto) and Canada East (Québec City) regions. For regulated industries — financial services, public sector, healthcare — keeping data physically within national borders can simplify compliance with privacy laws, procurement rules and sector‑specific guidance. Azure’s regional model and Kyndryl’s local deployment give enterprises a way to both offload infrastructure and retain sovereign control over where data and primary compute live.
Kyndryl’s Readiness research (its 2025/2026 Readiness Report series) shows rising executive concern about geopolitical and regulatory risks tied to global cloud usage; these are the exact anxieties the Cloud Uplift Canada launch aims to address. Note: Kyndryl’s published Readiness Report figures differ slightly between summaries and the numbers quoted in the press release; the general trend — that a substantial share of leaders report foundational technology constraints and are adjusting cloud strategies for sovereignty reasons — is supported across Kyndryl’s reporting. Readers should treat specific percentage points cited in vendor releases cautiously and consult the full Readiness Report for methodology details.

---

What Kyndryl Cloud Uplift actually does — technical breakdown​

Kyndryl Cloud Uplift is an IaaS‑style platform purpose‑built to host IBM Power workloads in the public cloud. Key, verifiable technical elements include:

• Support for IBM Power families and their primary operating environments: AIX, IBM i, and Linux on Power. This enables customers to move workloads that often cannot be easily rewritten or containerized.
• Integration with Microsoft Azure infrastructure and networking constructs. Skytap / Kyndryl Cloud Uplift runs on Azure host infrastructure (including options that map to Dedicated Host capabilities in Azure), and the platform provides documented regions and API names for Azure‑hosted deployments (for example, a Canada/Toronto region name).
• Network connectivity and hybrid options: customers can use ExpressRoute to create private circuits between on‑premises estates and Kyndryl Cloud Uplift on Azure, enabling consistent latency and control during lift‑and‑run scenarios. The platform’s documentation includes procedures for using customer‑managed ExpressRoute circuits.
• Self‑service tooling for “lift, run, and modernize”: the original Skytap heritage emphasizes templates, cloning, snapshots and lab‑style environments that let teams test and modernize incrementally without long outage windows. That capability remains central under the Kyndryl Cloud Uplift brand.

These technical choices underline the product’s positioning: a way to bring legacy stacks into Azure with minimal application change while preserving operational continuity.

---

Strengths: what Canadian IT teams can realistically expect​

• Lower migration risk — By enabling “as‑is” replication of IBM Power workloads, Cloud Uplift dramatically reduces the project risk and timeline compared to full refactoring or rewrite programs. For systems where change is too risky (billing, transactional back ends, regulatory systems), this is compelling.
• Data residency and compliance alignment — Running inside Microsoft’s Canadian regions helps organizations satisfy data‑residency requirements and simplifies controls for auditors and regulators. For many public‑sector buyers and regulated financial firms, this is a gating requirement.
• Speed to value — Self‑service templates, cloning and testing environments let teams validate migrations, run acceptance tests and start to modernize peripheral services (for example, front‑end microservices or analytics) without prolonged cutovers. Kyndryl positions Cloud Uplift as a way to get workloads into Azure quickly and then modernize incrementally.
• Enterprise support and managed services — Kyndryl’s global services footprint and Azure partnership mean customers can combine the platform with Kyndryl’s advisory, implementation and managed services — useful for organizations lacking internal skills for Power‑to‑cloud moves.
• Path to Azure‑native capabilities and AI — Once workloads run inside Azure, organizations can integrate them with modern services — storage tiers, identity, telemetry, and Azure AI services — on their own timelines rather than being forced to replatform upfront. This incremental modernization model reduces disruption.

---

Risks, caveats and what to watch for​

While the offering is strategically useful, it is not a panacea. Organizations should weigh the following practical and financial risks:

• Licensing and software entitlements — IBM Power environments often come with complex ISV licensing and IBM support entitlements. Moving a workload from on‑premises to cloud—even if “as‑is”—can have licensing, support and audit implications. These costs are vendor‑specific and must be validated with IBM and ISV contracts before migration. Kyndryl help docs and datasheets do not remove the need for license verification.
• Cost dynamics: infrastructure, egress and network topology — Running bare metal or dedicated host instances for Power workloads in Azure can be expensive. Additionally, organizations that intermix Canadian and non‑Canadian resources may face cross‑region egress fees and interconnect complexity. Plan for application‑level traffic patterns and test cost models in proof‑of‑concepts. Azure’s zone/region billing and ExpressRoute models mean egress and connectivity must be carefully modeled.
• Performance and latency expectations — Even when running in the same country, cloud networking and hypervisor behaviour differ from traditional on‑prem Power estates. Performance testing against representative workloads (peak I/O, batch windows, interdependent services) is essential before committing to a production cutover. Kyndryl’s self‑service cloning and lab features can help, but they do not replace full production‑scale load tests.
• Operational model changes — Running legacy stacks in Azure changes operations: telemetry platforms, patching windows, backup and DR patterns, and incident management will need re‑tooling. Teams should budget time for runbook updates, SRE adjustments and security baseline alignment.
• Sovereignty vs. regulatory nuance — “Data in Canada” satisfies many barometers, but regulatory regimes can require more than physical residency (e.g., control over encryption keys, government access, or specific certifications). Organizations must verify that running on Microsoft Canada plus a third‑party commercial offering meets their specific legal and procurement requirements. Don’t assume residency solves all compliance questions automatically.
• Vendor lock and long‑term modernization — Lift‑and‑run is an excellent near‑term risk reduction tactic, but it can delay essential modernization. Teams must maintain a clear roadmap from “lifted legacy” to an eventual refactor or replatform where it makes business sense, otherwise technical debt can simply migrate to the cloud.

---

Practical migration checklist: planning to production​

Successful migrations to Kyndryl Cloud Uplift on Azure Canada will follow disciplined steps. Below is a recommended, sequenced checklist for enterprise teams:

• Inventory and categorize workloads:
• Identify IBM Power systems by OS (AIX, IBM i, Linux) and dependent services.
• Classify criticality, peak I/O, and maintenance windows.
• Validate licensing and ISV agreements:
• Engage IBM and ISV partners to confirm licensing portability, support, and audit rules for cloud hosts.
• Define compliance and residency requirements:
• Document regulatory obligations (data residency, encryption, access controls) and map to Azure Canada region controls and Kyndryl controls.
• Establish network architecture:
• Design ExpressRoute or equivalent private connectivity; account for bandwidth, latency, and egress pricing.
• Ensure IP planning, DNS and security posture alignment.
• Run a proof‑of‑concept:
• Use Kyndryl Cloud Uplift’s lab/clone features to replicate representative workloads.
• Perform functional, performance and failover testing.
• Plan cutover and rollback:
• Define a stepwise cutover (pilot apps → non‑critical production → critical systems).
• Maintain clear rollback criteria and automated snapshots.
• Integrate telemetry, security and backup:
• Implement centralized logging, monitoring and SRE runbooks.
• Configure backup targets, retention, and DR plans that reflect in‑country SLAs.
• Modernization roadmap:
• Identify candidates for eventual replatform, containerization or data‑service migration.
• Schedule incremental modernization sprints once workloads are stable in Azure.

This sequence keeps risk small while unlocking the opportunity to modernize over time.

---

Costs and commercial considerations​

Cost modeling for a Cloud Uplift migration must account for multiple moving parts:

• Compute cost for Azure Dedicated/Host instances or bare‑metal mapping used to present IBM Power environments.
• Storage costs (including tiering for backups and snapshots).
• Network costs (ExpressRoute provisioning, cross‑region traffic, and any egress charges).
• Managed services and migration engineering fees from Kyndryl or partners.
• ISV and IBM licensing adjustments.

Kyndryl’s documentation and datasheets indicate Cloud Uplift runs on Azure infrastructure and supports standard enterprise networking patterns, but total cost will vary significantly by workload profile. Carefully scoping a proof‑of‑concept and using telemetry to estimate peak and steady‑state usage provides the most accurate forecast.

---

Integration with Azure-native modernisation and AI​

One of the strongest strategic arguments for bringing legacy Power workloads into Azure is the option value to adopt Azure‑native services at your own pace. Common follow‑up modernization paths include:

• Pairing transactional backends with Azure analytics and data platforms for enhanced reporting and AI‑driven insights.
• Exposing legacy functionality via API gateways or microservice facades to enable modern UX or SaaS front ends.
• Migrating non‑critical surrounding functions to Azure PaaS (databases, caching, telemetry) while keeping core processing on Power.
• Using Azure AI and MLOps pipelines to augment business processes without changing core transactional systems immediately.

Kyndryl explicitly frames Cloud Uplift as an enabler for this incremental modernization, allowing customers to “adopt modern cloud services and AI at their own pace.” That positioning aligns with industry best practice of staged modernization rather than big‑bang rewrites.

---

Realistic timelines and success metrics​

Expect a phased, iterative timeline rather than overnight migrations:

• Small pilots and labs: 2–6 weeks
• Pilot production migration for non‑critical workloads: 1–3 months
• Full production migration for critical systems (including extensive testing and regulatory sign‑offs): 3–12 months, depending on complexity

Success metrics should include:

• Recovery Time Objective (RTO) and Recovery Point Objective (RPO) adherence in the new environment
• Application transaction throughput and latency relative to on‑prem baselines
• Compliance audit pass rates for in‑country residency requirements
• Total cost of ownership (TCO) and run‑rate comparison after 12 months
• Measured time to enable a first Azure‑native capability (for example, exposing an API or integrating a data pipeline)

---

Case for and against: when Cloud Uplift is the right move​

When it’s a good fit:

• You run critical IBM Power workloads that are costly or risky to refactor.
• Regulatory, procurement or political constraints make in‑country data residency essential.
• You want to accelerate time‑to‑cloud while keeping operations intact and have a plan for incremental modernization.
• You need enterprise‑grade managed services and support during the migration.

When it’s not:

• You have a greenfield or cloud‑native stack where replatforming yields better long‑term cost and agility.
• Your team is already undertaking a planned, funded rewrite with clear ROI that outweighs short‑term lift benefits.
• The ISV or IBM licensing model prohibits cloud portability or imposes prohibitive costs.

---

Vendor and independent verification — what the documents show​

Kyndryl’s March 11, 2026 announcement explicitly names Microsoft Canada’s President Matt Milton and Kyndryl Canada’s President Brian Medeiros in support of the availability statement, reinforcing the partnership narrative. The announcement is published on Kyndryl’s site and carried via PR channels. Documentation and help pages for the Cloud Uplift platform (formerly Skytap) confirm region names and Azure host integration, and the product’s support documentation provides practical guidance (for example, ExpressRoute attachments and region identifiers) necessary to plan a migration. These materials corroborate the product’s technical claims and the Canada availability.
One caution: Kyndryl’s Readiness Report figures and language appear across several corporate summaries and press materials with slightly different percentages depending on the regional excerpt. The overall message (widespread concern about geopolitical risk and foundational technology constraints delaying innovation) is consistent; however, readers should consult the full Readiness Report and methodology for precise numbers and sample sizes before relying on specific percentages cited in vendor PR.

---

Recommendations for Canadian CIOs and IT leaders​

• Start with a short, accountable pilot: pick a non‑critical but representative IBM Power workload to prove performance, networking and cost assumptions inside Azure Canada.
• Lock down licensing early: engage IBM and your ISV partners before any move to understand entitlements and avoid audit surprises.
• Treat residency as a program, not a checkbox: confirm encryption, key management, and contractual controls that reflect your compliance requirements.
• Model network costs and DR: don’t underestimate egress, cross‑region traffic, and multi‑region DR implications.
• Plan a modernization runway: use Cloud Uplift to remove the immediate migration barrier, but maintain a concrete 18–36 month modernization roadmap to avoid replicating technical debt in the cloud.
• Use managed services strategically: where in‑house Power and Azure experience are limited, combine platform lift with vendor or partner managed services to accelerate learning and reduce risk.

---

Final analysis: practical bridge, not a final state​

Kyndryl’s Canada launch for Cloud Uplift delivers a pragmatic choice for organizations that face a trade‑off between operational continuity and modernization. It is a highly useful tool in the migration toolkit: it reduces migration risk, meets a real data‑residency demand, and buys IT teams time to modernize around stable, functioning core systems. The offering is especially relevant for regulated sectors and enterprises with extensive IBM Power estates that cannot be rewritten quickly.
That said, the solution is a bridge rather than a destination. Organizations should use it to de‑risk and accelerate early value realization, while simultaneously investing in long‑term modernization plans that reduce dependence on legacy architectures. Strategic clarity — from licensing implications to compliance, cost modeling and a disciplined migration/modernization roadmap — will determine whether Cloud Uplift is a tactical stopgap or the first step toward sustainable transformation.

---

Kyndryl’s Cloud Uplift availability in Microsoft Azure’s Canadian regions is a real, operationally useful option for Canadian enterprises; the hard work remains the same as always for migrations: disciplined planning, proof‑of‑concept testing, and a clear route from “lifted legacy” to modernized business capability.

---

Source: Kyndryl Cloud Uplift enables legacy migration to Azure Canada