Quick answer: An office server migration to the cloud takes about twelve weeks for an office with a handful of servers. Assess every server, decide each one with the 7 Rs, plan UAE data residency and licensing, then cut over on a Saturday. In OXEDGE’s experience, projects run from AED 15,000 for one file server to AED 300,000 and up for regulated estates.
Somewhere in most UAE offices there is a cupboard with a humming server: the file shares, the accounting database, a line-of-business app someone installed in 2016, and a backup drive that may or may not work. An office server migration to the cloud is no longer a question of whether but of when and how, because Microsoft’s support dates are forcing the issue and the UAE regions make in-country hosting easy. This guide sets out the step-by-step plan: assessment, choosing what to do with each workload, residency, licensing, downtime and a realistic timeline.
Sources: Mordor Intelligence, UAE cloud computing market · UAE Cyber Security Council, 20 January 2025 · Azure Migrate pricing
The support deadlines setting your timetable
For most offices the trigger is not strategy; it is a date. Microsoft products have a fixed lifecycle, and once extended support ends there are no more security patches unless you pay for Extended Security Updates (ESUs). Several of the versions still common in UAE server cupboards have reached or are about to reach that line.
| Product | Extended support ended or ends | Paid security updates (ESU) until | What it means |
|---|---|---|---|
| Windows Server 2012 R2 | 10 October 2023 | Year 3 ESU runs to 13 October 2026 | The last paid patches stop this month; these servers need to move or be rebuilt now |
| SQL Server 2014 | 9 July 2024 | 8 July 2027 | ESUs are free if the database runs on an Azure VM; otherwise paid |
| SQL Server 2016 | 14 July 2026 | 17 July 2029 | Already out of support; ESUs are paid, and Microsoft changed their pricing on Azure VMs, so check current terms |
| Windows Server 2016 | 12 January 2027 | ESUs announced by Microsoft | The largest group of office servers; three months left |
Sources: Microsoft Lifecycle: Windows Server 2012 R2 · Microsoft Learn: SQL Server ESU FAQ · Microsoft Lifecycle: SQL Server 2016 · Microsoft: planning ahead for Windows Server 2016 end of support, February 2026
Running unpatched servers is a real risk in a country where the Cyber Security Council reports more than 200,000 attacks a day on strategic sectors. ESUs buy time, but they cost money, cover only critical fixes and still leave you with ageing hardware. If a server will need replacing within two years anyway, the support date is the right moment to stop buying hardware altogether.
Step 1: assess everything, including what nobody remembers
A migration plan is only as good as its inventory. For a typical office of 20 to 200 people, the assessment takes one to two weeks and should cover five things.
- Servers and what runs on them. Operating system and version, CPU, memory and disk, and two weeks of real utilisation, not the specification on the invoice.
- Applications and their owners. Every line-of-business system, its vendor, its licence terms, whether the vendor supports it in the cloud, and who in the business depends on it.
- Data. File shares and their size, databases, mailboxes, and which of them hold personal or regulated data.
- The awkward edges. Scanners that save to a share, label printers, USB licence dongles, biometric attendance machines, CCTV recorders, and anything that talks to the server by IP address.
- Identity. The on-premises Active Directory, who has admin rights, and whether you already use Microsoft 365 or Entra ID.
Free tooling does most of the discovery. Azure Migrate’s discovery and assessment are free, and its server migration is free for the first 180 days per machine; AWS’s migration service gives each source server 2,160 free hours, which is 90 days of continuous replication. In both cases you still pay for the cloud resources used during replication and testing.
Sources: Azure Migrate pricing · AWS Application Migration Service FAQs · AWS Application Migration Service pricing
Do the bandwidth arithmetic early, too. A 2 TB file share is 16 million megabits; over a 100 Mbps upload that is about 44 hours of a fully saturated line, which in practice means several nights of copying while staff are not using the connection. Most office server estates hold at least one machine nobody can explain, and finding it before the move is cheaper than finding it after.
Most office server estates hold at least one machine nobody can explain, and finding it before the move is cheaper than finding it after.
Step 2: decide each workload with the 7 Rs
Not everything should be lifted and shifted. AWS’s migration guidance groups the choices into seven strategies, and the same vocabulary works on any provider. For an office estate, each server usually lands in one of them.
| Strategy | What it means | Typical UAE office example |
|---|---|---|
| Retire | Switch it off; nobody needs it | An old intranet, a server for a project that ended, a machine averaging under 5% CPU |
| Retain | Keep it where it is for now | A system tied to specialised hardware on site, or one due for replacement by its vendor’s SaaS version |
| Rehost | Move the server as it is to a cloud VM (“lift and shift”) | A line-of-business app whose vendor supports it on a VM but not as a service |
| Relocate | Move a whole virtualised platform without changing it | Offices already running VMware moving the cluster to a cloud-hosted version |
| Repurchase | Replace it with a SaaS product | File server to SharePoint and OneDrive; on-premises Exchange to Exchange Online; desktop accounting to a cloud edition |
| Replatform | Move with some optimisation, such as a managed database | SQL Server on an office box to a managed SQL service |
| Refactor | Rebuild the application for the cloud | Rarely right for an office migration; modernise later, once everything has moved |
Source: AWS Prescriptive Guidance: migration strategies (the 7 Rs). Examples reflect OXEDGE delivery experience.
In small and mid-sized offices, repurchase and retire do most of the work. The file server is usually the biggest single box, and moving it to SharePoint and OneDrive removes it entirely. AWS’s guidance is explicit that refactoring during a migration is the most complex option and is best done after the move; that advice applies even more strongly to a 50-person company than to an enterprise.
Step 3: residency and regulation
The UAE’s federal data protection law, Federal Decree-Law No. 45 of 2021, came into force on 2 January 2022 and sets requirements for transferring personal data outside the country. It does not ban hosting abroad, but in-country hosting removes most of the questions. Health data is different: under Federal Law No. 2 of 2019, Article 13, health information related to services provided in the UAE may not be stored, processed or transferred outside the country except where the health authorities allow it. Clinics and anyone handling patient records should plan for UAE-only hosting from the start.
Sources: u.ae: data protection laws · Mondaq: the UAE health data law and Article 13. This is general guidance, not legal advice; confirm obligations for your sector with counsel or your regulator.
The good news is that the common destinations for office workloads have a UAE location. Azure and AWS both run cloud regions in the country; our guide to AWS, Azure, Google Cloud and Oracle in the UAE compares the options. Microsoft 365 lists the UAE as a local data residency geography with data centres in Abu Dhabi and Dubai, covering Exchange Online, SharePoint, OneDrive and Teams. One trap: a Microsoft 365 tenant’s default geography is fixed at the moment the tenant is created and cannot be changed afterwards, so check the data location card for an older tenant before you move file shares into it; Microsoft’s Advanced Data Residency add-on is the route to move existing data in-country.
Source: Microsoft Learn: Microsoft 365 data residency overview
For a fuller treatment of which workloads must stay in-country and how to design for it, see cloud data residency in the UAE.
Step 4: licensing, the line that changes the business case
Licences decide whether the cloud bill is reasonable or painful. In Azure UAE North, a D2s v5 virtual machine lists at $0.118 an hour on Linux and $0.210 on Windows, so the Windows licence alone adds 78 per cent. Three questions settle most cases.
Source: Azure Retail Prices API, UAE North pay-as-you-go list prices, checked 1 October 2026
- Do you have Software Assurance? Windows Server and SQL Server core licences with active Software Assurance qualify for Azure Hybrid Benefit, which Microsoft says can save up to 85 per cent on SQL Server against pay-as-you-go. Without it, you pay licence-included rates.
- Where were the licences bought, and when? Since 1 October 2019, on-premises licences bought without Software Assurance and mobility rights cannot be deployed on dedicated hosted cloud services from Microsoft’s “Listed Providers”: Alibaba, Amazon and Google, as well as Microsoft itself. Check this before choosing a provider for Windows-heavy workloads.
- Does the application vendor allow it? Many line-of-business vendors license per server or per site; some require a new agreement for cloud hosting. Ask in writing during the assessment, not at cutover.
Sources: Azure Hybrid Benefit · Microsoft: updated licensing rights for dedicated cloud
The licensing picture often points to a hybrid answer: SaaS for files and email, a managed database where the application allows it, and a small number of Windows VMs only for the applications that genuinely need them.
How OXEDGE does this
We move office servers to UAE-hosted cloud in planned waves, with a tested rollback for every cutover.
- A two-week assessment: server and application inventory, utilisation data, dependency map and a 7 Rs decision for every workload.
- A residency and licensing check per workload, with the vendor questions asked in writing before anything moves.
- A landing zone built as code in a UAE region: identity, network, backups, monitoring and budget alerts.
- Weekend cutovers with written success criteria, then a handover runbook, a restore test and documented decommissioning of the old hardware.
Step 5: build the landing zone and plan the downtime
Before any workload moves, build the destination: identity connected to Entra ID, a network with a VPN or private link back to the office, backups switched on from day one, monitoring, and budget alerts. Build it as code so it can be rebuilt and reviewed; our DevOps baseline for small teams covers the minimum. Then plan downtime per workload, because a file share, a database and an application server each move in a different way.
Then plan downtime per workload, because a file share, a database and an application server each move in a different way.
| Workload | How it moves | Typical user-facing downtime |
|---|---|---|
| File server to SharePoint and OneDrive | Bulk copy over several nights, then a final delta sync and drive re-mapping | An hour or less for the final sync; a short adjustment period for users |
| Application server VM | Continuous block-level replication, a test cutover, then the real one | Usually under an hour at cutover |
| Accounting or ERP database | Backup and restore or replication, with writes frozen for the final sync | One to four hours, scheduled outside working days |
| On-premises email | Staged or hybrid migration of mailboxes in batches | Little or none if staged properly |
| Active Directory | Sync to Entra ID first, then move devices and apps over time | None if staged |
Ranges reflect OXEDGE delivery experience with UAE offices; your data volumes and applications will move them.
Since the federal working week moved to Monday to Friday in January 2022, with most private employers reported to be following, the natural cutover window for most offices is Saturday, with Sunday kept free for rollback. Agree in advance what “success” means for each cutover (users can log in, the accounting system posts a test invoice, scanners save to the new location) and what triggers a rollback. Plan the rollback before the cutover, because the decision to go back has to be made by a rule, not by a tired engineer at two in the morning.
Source: Mondaq: a new working week in the UAE from 1 January 2022
A realistic twelve-week office server migration timeline
For an office with a handful of servers, a file share, a database-backed business application and email, twelve weeks from kick-off to decommissioning is achievable without heroics. Select a phase to see what happens in it.
Durations reflect OXEDGE delivery experience with UAE offices of 20 to 200 people; regulated data, more sites or custom applications extend them.
What it costs, and what moves the price
A migration has two price tags: the one-off project and the new monthly run cost. The project is mostly people’s time, and its size depends far more on the number and awkwardness of applications than on the number of users.
| Office profile | Typical shape of the work | Typical UAE project range |
|---|---|---|
| Small office: one file server, email already in Microsoft 365 | Repurchase files into SharePoint and OneDrive, retire the server, set up backup and device management | AED 15,000–35,000 |
| Growing SME: three to eight servers, accounting or ERP database, one business application | Landing zone, a mix of rehost and replatform, two or three cutover waves | AED 45,000–120,000 |
| Multi-site or regulated: ten or more servers, health or financial data, in-country recovery | Residency controls, staged waves, recovery design and testing | AED 120,000–300,000 and up |
Ranges reflect OXEDGE delivery experience and quotes seen in the UAE market; your scope will move them. They cover the project only, not monthly cloud, Microsoft 365 or application licence costs.
What moves the price: applications with no vendor support for the cloud, undocumented dependencies, large databases with tight downtime windows, a second site, and regulated data that needs in-country recovery. What moves the monthly bill afterwards: right-sizing the VMs after the first month of real usage, scheduling anything that does not need to run overnight, and the licensing choices in step 4. Budget for a month of overlap where you pay for both the old and the new environment.
After the move: the first 90 days
The project is not finished at cutover. Three things decide whether the move was worth it. First, prove the backups by restoring something real, such as last week’s version of a shared folder or a copy of the accounting database, and write down how long it took. Second, review the first two monthly bills against the plan and resize anything running far below its capacity; cloud VMs are almost always oversized at first because they were matched to old hardware. Third, retire the old servers properly: wipe the disks, keep evidence of the wipe, remove them from the asset register and cancel the maintenance contracts.
Done this way, the server cupboard becomes a storage cupboard, staff can work from anywhere with the same access, and the next Microsoft support deadline becomes a line in a release note rather than a project. The security posture is the other quiet gain; once identity lives in the cloud, our guide to zero trust for a 50-person company is the natural next step.
FAQ: moving office servers to the cloud in the UAE
How much does it cost to move office servers to the cloud in the UAE?
In OXEDGE’s experience a small office with one file server runs AED 15,000 to 35,000, a growing SME with three to eight servers AED 45,000 to 120,000, and a multi-site or regulated estate AED 120,000 to 300,000 and up. These cover the project only, not monthly cloud or licence costs. Budget for a month of paying for both environments.
How long does an office server migration to the cloud take?
For an office with a handful of servers, a file share, a database-backed business application and email, twelve weeks from kick-off to decommissioning is achievable. The assessment alone takes one to two weeks for an office of 20 to 200 people. Regulated data, more sites or custom applications extend the timeline.
Will staff lose access to files and systems during the migration?
Only briefly if it is staged. A file share’s final sync usually takes an hour or less, an application server cutover usually under an hour, and an accounting or ERP database one to four hours. Most UAE offices cut over on a Saturday and keep Sunday free for rollback, with written success criteria agreed in advance.
Should we move our file server to SharePoint or a cloud server?
For most small and mid-sized offices, SharePoint and OneDrive replace the file server entirely, which removes the biggest single box. Microsoft 365 lists the UAE as a local data residency geography, with data centres in Abu Dhabi and Dubai. Check an older tenant’s data location first, because a tenant’s default geography is fixed when it is created.
What are the data residency requirements for cloud deployments serving clients in UAE?
Federal Decree-Law No. 45 of 2021, in force since 2 January 2022, sets requirements for transferring personal data outside the country. It doesn’t ban hosting abroad, but in-country hosting removes most of the questions. Health data is stricter: under Federal Law No. 2 of 2019, Article 13, it may not be stored, processed or transferred outside the UAE except where the health authorities allow it. Azure, AWS and Microsoft 365 all have UAE locations.
Work with OXEDGE
Get a migration plan for your office servers before the next support deadline arrives.
We would start with a short discovery call and a look at your server list, support dates and the applications your team relies on. You leave the first conversation with a draft 7 Rs decision for each server and a realistic sense of timeline and budget.
