Consider the CTO of a 1,200-employee insurance and asset-management group headquartered in DIFC. The board has given them 18 months to move core systems off aging servers. Policy-administration and claims platforms are five years past their refresh cycle.
One systems integrator is pitching a fast lift-and-shift. Another wants a full rearchitecture. Neither vendor has answered the question the compliance team keeps asking. Does moving to the cloud mean policyholder data leaves the UAE? The CTO does not need a sales deck. They need a migration plan that the board and auditors will approve. It also has to satisfy CBUAE.
VLink is a global IT services company. It helps CIOs and CTOs at UAE-regulated and mid-market enterprises plan and execute cloud migrations using the 6Rs framework. That includes moving legacy workloads to AWS, Azure, and compliant sovereign infrastructure. It also means building the cost and compliance case their boards actually approve. Delivery hubs span the United States, India, and Indonesia. A dedicated practice supports UAE-based engagements across banking, insurance, healthcare, and government-adjacent sectors.
Most published guidance on this topic covers one piece at a time. A vendor page covers migration services, a blog covers the 6Rs, a compliance note covers data residency. This guide puts process, data residency, and cost in one place. Every figure comes from a named research report, not a generic industry claim.
What Is Driving Cloud Migration Growth in the UAE in 2026?
Three independent research firms have published UAE cloud market estimates in the past two years. They agree on direction, even where the exact numbers diverge. Mordor Intelligence's January 2026 update puts the market at $12.84 billion in 2025. It projects growth to $56.26 billion by 2031, a 27.93% compound annual growth rate. Mark't and Tel Advisors estimated $13.14 billion in 2024, reaching $40.73 billion by 2030. GMI Research put the 2024 base at a more conservative $4.1 billion. It projects $23 billion by 2032, a 24.1% CAGR.

UAE Cloud Computing Market Size — Three Independent Estimates
| Research Firm | Base Year Size | Projected Size | CAGR | Forecast Period |
| Mordor Intelligence | $12.84B (2025) | $56.26B (2031) | 27.93% | 2026-2031 |
| Mark't and Tel Advisors | $13.14B (2024) | $40.73B (2030) | ~20.7% | 2024-2030 |
| GMI Research | $4.1B (2024) | $23B (2032) | 24.1% | 2025-2032 |
Behind the growth: infrastructure-as-a-service holds 52.40% of 2025 spend, while platform-as-a-service is the fastest-growing segment. Public cloud still accounts for 63.20% of deployments. Hybrid cloud is growing fastest, at a 31.45% CAGR, and is projected to exceed $16.28 billion by 2031. Regulated industries are driving that shift. They keep sensitive workloads on sovereign or private infrastructure. Everything else moves to public cloud.
Government policy is a direct driver, not a backdrop. Abu Dhabi's AED 13 billion (roughly $3.54 billion) Digital Strategy 2025-2027 mandates a hard target. Every ministry must move 100% of mission-critical workloads to sovereign cloud infrastructure. Hyperscalers are responding with matching investment. AWS and e& signed a $1 billion, six-year alliance in January 2025. Microsoft holds a $1.5 billion stake in G42. du and Microsoft signed an AED 2 billion ($544 million) hyperscale data-center agreement in April 2025. Combined, AWS, Microsoft, Oracle, and G42 held more than 54.40% of UAE cloud revenue share in 2025.
Two more data points show where UAE cloud capacity is headed next. Oracle has committed roughly $30 billion a year to its infrastructure partnership with G42. Separately, OpenAI, Oracle, NVIDIA, Cisco, and SoftBank are building the Stargate UAE AI campus. It's a 5-gigawatt facility, announced in May 2025. Core42, formed from the merger of G42, Injazat, and Inception, is also the sovereign-cloud partner behind CBUAE's new SFCSI infrastructure. Together, these signal that UAE cloud capacity is being built for AI workloads as much as for traditional enterprise migration. That's worth knowing if your roadmap will eventually need to support AI or machine learning workloads. The market map of AI companies in Dubai and the UAE covers which vendors deliver that work.
What Is the 6Rs Framework, and Which Strategy Fits Your Workload?
The 6Rs framework — Rehost, Replatform, Refactor, Repurchase, Retire, Retain — originated at Gartner. AWS later extended it into its current six-strategy form. Gartner's principal research analyst on cloud migration strategy has written that architects generally choose among several migration paths. The choice depends on how critical and how customized a given workload is. Few teams apply one strategy across an entire estate. That distinction matters more than most vendor pitches suggest. A single migration program almost always uses three or four of the six strategies, not one.

The 6Rs Migration Framework
| Strategy | What It Means | Best For | UAE-Specific Consideration |
| Rehost | Lift-and-shift onto cloud infrastructure with minimal change | Legacy apps nearing hardware end-of-life; fastest time-to-cloud | A reasonable first step while a data residency review is still in progress |
| Replatform | Minor optimizations without full rearchitecture | Apps that need modest cloud-native gains without a rebuild | Common for core banking middleware running on IBM WebSphere MQ or similar |
| Refactor | Rearchitect for cloud-native services | Strategic systems with a long remaining lifespan and clear ROI | Highest cost and effort; reserve for systems that justify the investment |
| Repurchase | Replace with a SaaS equivalent | Commodity workloads such as CRM, HR, or ERP modules | Confirm the SaaS vendor's own UAE data residency and sub-processor terms |
| Retire | Decommission the workload entirely | Redundant or low-value systems found during discovery | Frequently the single biggest source of budget recovery in a migration program |
| Retain | Keep the workload on-premises for now | Regulatory- or latency-bound workloads | Common for core ledgers pending onboarding to CBUAE's sovereign cloud infrastructure |
What this means for a CTO in that position: the question is not "lift-and-shift or refactor." It is which of the six strategies applies to each system in the estate, and in what order. A discovery phase should map every application against these six categories before any vendor conversation happens. That step is what separates a defensible board proposal from a generic migration pitch.
What UAE Data Residency Laws Apply to Your Migration?
Data residency in the UAE is not one rule. It is a set of sector-specific regimes layered on top of a federal data protection law. Getting this wrong is the single most common reason a migration stalls after the technical plan is already approved.
UAE Data Residency Requirements by Sector
| Sector | Regulator / Law | Key Requirement |
| Banking & Finance | CBUAE (Central Bank of the UAE) | Licensed institutions must keep their Master System of Record and all confidential/transaction data within the UAE, and obtain prior non-objection before outsourcing or offshoring material data. CBUAE launched the Sovereign Financial Cloud Services Infrastructure (SFCSI) on 25 February 2026 with Core42 for licensed institutions. |
| Healthcare | DHA / DoH, Health ICT Law | Federal Law No. 2 of 2019 (Health ICT Law) requires electronic health data to remain in-country. |
| Government & Semi-Government | TDRA / Federal Authority for Artificial Intelligence and Data | Government data classified secret, sensitive, or confidential must remain within the UAE at all times. |
| Cross-sector baseline | Federal Decree Law No. 45 of 2021 (PDPL) | Sets the general framework for data residency and the conditions under which cross-border data transfer is permitted. |
Two additional jurisdictions matter for regional or holding-company structures. The DIFC Data Protection Law (DIFC Law No. 5 of 2020) governs entities registered in that free zone. So does the ADGM Data Protection Regulations 2021, for entities registered in ADGM. Both operate independently of the federal PDPL. A group with entities in DIFC, ADGM, and mainland UAE may face three overlapping data protection regimes. They are not identical, and each needs its own compliance review.
The practical effect for a BFSI migration: "cloud" does not automatically mean "public cloud, any region." A bank's Master System of Record has to stay in the UAE, regardless of which hyperscaler is chosen. Any offshoring of confidential data needs CBUAE's prior non-objection before it happens, not after. The February 2026 SFCSI launch gives regulated institutions a sovereign alternative that did not exist eighteen months ago. That option is worth raising with CBUAE-supervised clients before defaulting to a standard hyperscaler region.
How Do AWS, Azure, and Google Cloud Compare for UAE Workloads?
Region availability, not brand preference, is the first filter for any UAE workload with a residency requirement.

AWS vs. Azure vs. Google Cloud — UAE Region Availability
| Provider | UAE Region(s) | Launched | Compliance Note |
| AWS | AWS Middle East (UAE), multiple Availability Zones | 2022 | Suited to workloads that need in-country residency with multi-AZ resilience |
| Microsoft Azure | UAE North (Abu Dhabi) and UAE Central (Dubai) | 2019 | First of the major hyperscalers to open Middle East data centers; two operational regions give failover options within the country |
| Google Cloud | No dedicated UAE region | — | Nearest regions are Doha, Qatar and Dammam, Saudi Arabia; Mordor Intelligence's competitive analysis notes Google "trails in in-country zones" versus AWS and Azure |
For a CBUAE- or DHA-regulated workload with a hard in-country requirement, this table narrows the field fast. In practice, that means AWS or Azure today. Teams already committed to Google Cloud have reasons to stay — existing Anthos investments, data analytics tooling, or pricing. For a regulated workload, that means a compensating design. One option is application-layer data localization. Another is a hybrid architecture that keeps the regulated dataset on AWS or Azure while other workloads stay on GCP.
Beyond region availability, cost structures and service catalogs vary between providers. A like-for-like comparison needs its own spreadsheet, not a single number. AWS and Azure both publish UAE-specific pricing calculators; Google Cloud's rates are typically quoted against its nearest available region. Teams comparing all three should model landed cost for their actual workload profile. That includes data egress and support tiers, not just published list prices.
Do You Have the In-House Talent and Security Posture to Execute This?
A migration plan is only as good as the team executing it, and UAE-specific cloud skills are scarce. Certified AWS, Azure, and GCP professionals are in short supply across the region. That scarcity shows up directly in compensation. Cloud-native and FinOps specialists can command salary premiums of up to 40% over general IT roles. Oracle has pledged to train 350,000 professionals across the Middle East as part of its regional cloud investment. That commitment is itself a signal of how large the talent gap is.
Security posture is the second gap teams underestimate. A cloud migration is also an identity and access-management redesign. Zero Trust architecture, least-privilege IAM policies, and cloud-native governance tooling do not carry over from an on-premises environment by default. Teams without in-house security architects for the target cloud platform should plan for that gap before migration, not after go-live.
What Does Cloud Migration Actually Cost in the UAE?
Published UAE migration pricing is inconsistent because scope varies so widely between a single-application rehost and a multi-system regulated program. Reviewing engagement patterns across UAE cloud migration projects gives a more useful planning range than any single vendor's headline number.
Typical UAE Cloud Migration Cost and Duration by Scope
| Migration Scope | Typical Cost Range (USD) | Typical Duration |
| Small workload (single application, fewer than 10 servers) | $20,000 - $75,000 | 6-12 weeks |
| Mid-size workload (department-level system or ERP module) | $75,000 - $300,000 | 12-24 weeks |
| Enterprise program (multi-system, regulated environment) | $300,000 - $2,000,000+ | 6-12 months |
These ranges are directional, not a quote. The actual number depends on how many applications need refactoring versus a straight rehost. It also depends on how much discovery work has already been done.
A note from VLink's VP of Strategy. "Early in a pre-sales cycle for a UAE logistics client, the board had already rejected one migration proposal. The vendor had led with a single lump-sum number and no breakdown of where the cost came from. We rebuilt the business case as a phased TCO model instead of one figure. It broke down discovery, pilot, phased migration, and a first-year optimization line separately. That was what got it through the board, not a lower price."
Here's what this means for a finance or IT leader building a business case. A single all-in number is usually a red flag. A defensible cost model breaks cost down by migration phase and by 6Rs strategy. A rehost-heavy plan and a refactor-heavy plan can carry a two- to five-times cost difference for the same workload.
What Does a Realistic UAE Migration Timeline Look Like?
Skipping discovery to start faster is tempting. It's also the most common reason UAE migration projects run over budget. A realistic sequence looks like this:
- Discovery and assessment (1-3 weeks): inventory every application against the 6Rs, map data flows, and identify which workloads carry a residency requirement.
- Migration strategy and roadmap (2-4 weeks): assign a 6Rs strategy per workload, select target regions, and build the compliance sign-off plan with legal and the relevant regulator.
- Pilot migration (2-4 weeks): migrate one non-critical workload end-to-end to validate the process, tooling, and rollback plan before committing the full program.
- Phased full migration (8-24 weeks, scope-dependent): migrate remaining workloads in waves, grouped by dependency and business criticality.
- Optimization and handover (ongoing, first 90 days critical): right-size infrastructure, tune costs, and transfer operational ownership to the internal team or managed-services partner.
Three risk factors most often push these timelines out. Legacy applications with undocumented dependencies take longer to map during discovery than teams expect. A migration roadmap built without input from application owners, not just infrastructure, tends to miss integration points. Those points often only surface during the pilot. And rollback planning that gets treated as an afterthought turns a manageable delay into a full program reset.
Which UAE Industries Are Migrating Fastest, and Why?
BFSI is the largest vertical by cloud spend, holding 21.60% share of the UAE cloud market in 2025. That reflects a direct consequence of CBUAE's outsourcing framework maturing. Banks now have a documented sovereign-cloud path, rather than a blanket "stay on-prem" default. Healthcare is the fastest-growing vertical by CAGR, at 29.74% through 2031. Providers are digitizing records under DHA and DoH oversight, while keeping data in-country under the Health ICT Law. Government and semi-government demand is being pulled forward by policy, not technology readiness. Abu Dhabi's Digital Strategy 2025-2027 sets a hard 100% mission-critical-workload target. That puts many agencies on a compliance-driven timeline, not a discretionary one.
Retail, logistics, and manufacturing are migrating for a different reason — cost and elasticity, not compliance. They typically move faster through the 6Rs, because fewer of their workloads carry a hard residency requirement.
Two other groups show up repeatedly in UAE migration conversations, even though market-size reports rarely single them out. International companies expanding into the UAE often inherit a cloud stack built for a different regulatory environment entirely. Their first migration decision usually is not which provider to use. It is which existing workloads even need a UAE region at all. The rest can often stay on their global infrastructure. SaaS and product companies face a related but different problem. Their engineering teams are usually cloud-native already. So their 6Rs conversation is less about legacy rehosting. It is more about whether their existing multi-tenant architecture can satisfy a UAE enterprise customer's residency requirement. Often it cannot, without a costly re-platform.
How Does VLink Support Cloud Migration for UAE Enterprises?
VLink runs UAE cloud migration services engagements from discovery through optimization. Every application gets mapped against the 6Rs before VLink recommends a target region or provider.
That includes the compliance work most migration vendors treat as a side conversation. VLink confirms which regulator applies — CBUAE, DHA, or TDRA. It also identifies which workloads need to stay on sovereign infrastructure. It flags which ones can move to a standard AWS or Azure UAE region instead.
VLink's application modernization practice handles workloads that need rearchitecting, not just a lift-and-shift. That practice sits inside its custom software development team. It rebuilds middleware and integration layers, rather than simply relocating them.
Post-migration, VLink's DevOps consulting services cover cloud infrastructure management — monitoring, cost optimization, and CI/CD pipelines. That keeps the environment from drifting back into the sprawl that made the original migration necessary.
UAE teams often need certified AWS, Azure, or GCP engineers embedded during the migration itself. VLink's IT staff augmentation practice fills that gap directly. Clients can hire cloud engineers on a project or ongoing basis, without running a full-time hiring cycle.

In Summary
- The UAE cloud market is growing 24-28% annually across three independent forecasts, driven as much by government mandate (Abu Dhabi's Digital Strategy 2025-2027) as by enterprise demand.
- The 6Rs framework — not a single migration approach — should drive strategy per workload; most portfolios mix three or more of the six.
- Data residency is sector-specific: CBUAE for banking, DHA/Health ICT Law for healthcare, TDRA for government, with PDPL as the cross-sector baseline.
- AWS and Azure both operate UAE regions; Google Cloud does not, which narrows provider choice for hard-residency workloads.
- Cost planning should be phased and broken down by 6Rs strategy, not delivered as a single lump-sum number.

Vice President, Strategy – VLink Inc.
Sambhavi Gopalakrishnan is the Vice President of Strategy at VLink Inc., bringing over a decade of experience in IT leadership, project implementation, and strategic growth. She possesses a strong foundation in technical project management and pre-sales, driving innovation and business transformation at VLink.

























