Case study, UAE
Moving Only Part of Your IT to Azure
A mid-sized Dubai trading firm ran everything on a single ageing server room in Al Quoz. Email was slow, the ERP crashed every quarter-end, and the finance team could not work from home during Ramadan hours. They did not want a full lift-and-shift. They wanted email, backup, and the ERP database in the cloud, while keeping their old accounting system and file server on-premises for another two years. That is a partial migration, and yes, it is completely possible on Microsoft Azure.
The short answer to the question in the title: you do not have to move your entire estate. Azure is built for hybrid setups. You pick the workloads that hurt the most, migrate those first, and leave the rest alone until you are ready. For most UAE businesses, that is the sensible starting point.
Before and After: The Al Quoz Trading Firm
One physical server room, no offsite backup, Outlook running on an old Exchange box, ERP database on a five-year-old machine. Quarter-end took 14 hours to close. Remote work required a shaky VPN. Power cut in July 2023 wiped two days of invoicing.
Email moved to Microsoft 365, ERP database moved to Azure SQL, backups replicated to Azure in the UAE North region. File server and legacy accounting stayed on-premises, connected via Azure ExpressRoute. Quarter-end now closes in under 4 hours. Downtime during cutover was 90 minutes, done on a Friday night.
Section 1
What We Tried First (and Why It Nearly Failed)
The original plan was to move everything in one weekend. Email, ERP, files, accounting, the lot. Two things stopped that idea cold.
- The accounting software was ancient. The vendor had stopped supporting it in 2019. Lifting it to Azure would have meant paying for a rewrite the business did not need yet.
- Data residency questions. The finance director wanted written confirmation that customer data would stay inside the UAE. That took three weeks of paperwork with legal and with Microsoft.
- Bandwidth reality. The office had a 100 Mbps line. Pushing 4 TB of file data over that link would have taken about a week of continuous upload, blocking normal work.
- Staff nerves. The IT manager had run that server room for eleven years. A full migration felt like erasing his job overnight. Change management matters.
We paused, and shifted to a phased approach. Email first, database second, files third, legacy accounting never (it will be replaced, not migrated).
Section 2
What Actually Worked
Once we accepted that partial was the goal, the project moved fast. The pattern that worked, and that we have since used for two other UAE clients, looks like this:
- Assess before you touch anything. We ran the Azure Migrate tool for 30 days to see actual CPU, RAM, and I/O patterns. Half the on-prem servers were oversized by a factor of three.
- Start with email. Moving Exchange to Microsoft 365 gave the whole company a visible win in week one. Staff stopped complaining about mailbox limits, and management saw the cloud was not scary.
- Use hybrid identity. Azure AD Connect kept the on-prem Active Directory as the source of truth. Users logged in with the same password. Zero retraining.
- Pick a UAE region. Azure has two UAE regions UAE North (Dubai) and UAE Central (Abu Dhabi). Choosing UAE North kept data residency clean and satisfied the finance director.
- Move the database with Azure Site Recovery. Replication ran for two weeks in the background. The actual cutover was 90 minutes on a Thursday night.
- Keep the file server on-prem, for now. A Storage Sync agent gives the same files a cloud copy for backup, without forcing users to change how they open documents.
- Engage a local partner. A team offering Azure cloud services in Dubai handled the licensing paperwork, the VAT invoicing setup, and the initial security baseline. That saved roughly six weeks of trial and error.
The lesson is boring but true: move the workloads that hurt, leave the ones that work, and stop pretending cloud is all-or-nothing. Partial Azure migration is not a compromise, it is the plan.
Hybrid Cloud vs Full Migration: The Honest Difference
A full migration means every server, database, and application ends up running on Azure. On-premises hardware is retired. It is clean, but it is expensive to plan and it exposes you to one vendor.
A hybrid setup keeps some workloads on-premises and connects them to Azure over a private link (VPN or ExpressRoute). You get cloud elasticity where you need it and predictable local performance for the things that must stay close to the office. For most UAE SMEs, hybrid is where you live for the first three years, and possibly forever. There is nothing wrong with that.
A Simple Readiness Checklist
- You have at least one workload causing real pain. Slow email, aging database, expiring hardware warranty. If nothing hurts, wait.
- Your internet link is 200 Mbps or better, or you can add a dedicated ExpressRoute circuit.
- You know which data must stay in the UAE. Personal data under the UAE Personal Data Protection Law usually should.
- You have a signed budget, not just a hope. Partial migrations typically start around AED 40,000 to AED 120,000 for a small firm, depending on scope.
- Someone owns the project internally. Not the CEO, not the intern, an actual IT lead or operations manager with time on their calendar.
- You accept it will take 8 to 16 weeks, not one weekend.
Frequently asked questions
Is a partial Azure migration secure and compliant with UAE regulations?
Yes, when set up correctly. Azure offers UAE North and UAE Central regions, so data can stay inside the country. Microsoft holds ISO 27001, SOC 2, and CSA STAR certifications, and it publishes attestations covering UAE-specific requirements.
For compliance with the UAE Personal Data Protection Law and sector rules from the Central Bank or ADGM, work with your legal team to map which datasets can move and which must stay on-premises. A local partner usually has template documentation ready.
How much does a partial migration cost for a UAE business?
For a small to mid-sized company, the project cost typically lands between AED 40,000 and AED 120,000, depending on how many workloads move and whether you need ExpressRoute. Ongoing Azure consumption is separate and usually AED 3,000 to AED 20,000 per month for a first phase.
Ask any partner for a fixed-scope assessment first. If they cannot give you a number after two weeks of discovery, keep looking.
Which workloads should I move to Azure first?
Email and collaboration (Microsoft 365) are the easiest wins. Backup and disaster recovery come next, because Azure Site Recovery gives you offsite protection cheaply. Development and test environments are also low-risk candidates.
Production databases and file shares are worth moving when the underlying hardware is close to end-of-life or when remote access is causing daily complaints.
Which systems should stay on-premises?
Legacy applications from vendors who no longer support cloud deployment, systems with very high local I/O such as CAD workstations or video editing, and anything tied to physical hardware like factory sensors or POS terminals. Also keep on-prem anything you plan to retire in the next 18 months, there is no point moving what you will delete.
Will a partial migration reduce downtime?
In most cases, yes. Azure regions offer availability zones, automated failover, and geo-redundant backup. Once your critical database or email is in Azure, unplanned downtime typically drops from hours per year to minutes.
The migration itself does require a short planned outage, usually one to four hours per workload, done outside business hours.
How long does a phased Azure migration take?
Plan for 8 to 16 weeks for the first phase of a partial migration. That includes assessment, procurement, pilot, cutover, and two weeks of stabilisation. Subsequent phases are faster because the connectivity, identity, and monitoring are already in place.
Do I need a certified Azure partner in the UAE?
You do not legally need one, but it usually pays for itself. A local partner handles CSP licensing with AED invoicing, understands local telecoms for ExpressRoute, and can send an engineer on-site when something breaks. They also carry Microsoft co-funding that can offset assessment costs.
What are the most common mistakes to avoid?
Three keep repeating. First, migrating without an assessment, which leads to oversized VMs and surprise bills. Second, ignoring identity, which forces users to remember two passwords. Third, treating the go-live as the end of the project. Post-migration tuning in the first 60 days is where you claw back 20 to 40 percent of the monthly cost.
Hello! My name is Lars Jensen, and I am a fitness enthusiast and a healthy lifestyle coach from Denmark. Moving to a hot climate completely changed my approach to training, hydration, and recovery. I had to adapt my routine, nutrition, and lifestyle to maintain maximum performance even in extreme heat.