Discovery and assessment
Inventory of servers, databases and applications using Azure Migrate, with performance data and dependency mapping
Services
Migrating to Microsoft Azure: A Practical Method for UAE Organisations
Migrating to Microsoft Azure means moving servers, databases and applications from your own hardware or another cloud into Azure, usually in planned waves after an assessment of dependencies, sizing and cost. Each workload is rehosted, replatformed or rebuilt depending on its value and age. emtech plans and runs Azure migrations for UAE organisations, commonly into the UAE North region.
- Azure Migrate assessment
- Migration in planned waves
- Rollback for every cut-over
Updated · emtech Computer Co LLC
1993Established in the UAE
ISO/IEC 20000-1Certified service management
Dubai · Abu DhabiLocal teams
- TDRACertified
- SIRACertified
- MCCCertified
- ISO20000-1 certified
- 1993Established in the UAE
Is this for you
Signs you need Azure migration
If two or more of these sound familiar, a short conversation with a specialist usually saves time and cost later.
- 01Server warranties end within the next year
- 02Windows Server or SQL Server versions are out of support
- 03A data centre or colocation contract is up for renewal
- 04Cloud cost estimates vary widely between proposals
- 05Application dependencies are undocumented
Scope
What is included
Migration strategy per workload
A rehost, replatform, refactor, replace or retire decision for each application, with reasons
Business case
Projected Azure run cost compared with keeping or refreshing current infrastructure, including one-time migration costs
Landing zone
Subscriptions, networking, identity, security policies, backup and monitoring in place before the first workload moves
Wave plan
Grouping of workloads by dependency and risk, with test, cut-over and rollback plans for each wave
Migration execution
Replication, test migrations, user acceptance testing and cut-over in agreed windows
Post-migration tuning
Right-sizing, reserved capacity where justified, and decommissioning of old hardware
Rehost, replatform or refactor: choosing a route per workload
Microsoft's Cloud Adoption Framework describes several migration routes. In practice most projects use three of them, plus two decisions that remove work altogether.
| Route | What changes | Good for | Watch out for |
|---|---|---|---|
| Rehost (lift and shift) | The server moves as a virtual machine, largely unchanged | Third-party apps you cannot modify, tight deadlines, end-of-support servers | Brings old inefficiencies along; costs more than it could if sized from the old server |
| Replatform | Small changes to use managed services, for example SQL Server to Azure SQL Managed Instance, or IIS sites to App Service | Databases and web apps with standard requirements | Feature differences need testing; vendor support terms for managed databases |
| Refactor or rebuild | Application redesigned for cloud services such as containers or serverless | In-house applications with long life and growth | Time and developer effort; rarely justified for a first migration |
| Replace | Move to a SaaS product instead | Email, file sharing, HR, CRM | Data migration and process change |
| Retire | Switch off | Servers nobody can identify an owner for | Confirm with a scream test: disconnect, wait, then remove |
A typical UAE mid-sized estate ends up mostly rehosted, with databases and web front ends replatformed and a few systems retired. Retiring is underrated: assessments regularly find servers that are still powered on but no longer used, and each one removed is a cost that never reaches Azure.
Do not judge a workload by its operating system alone. A server running a vendor's application may be supported by the vendor only on specific configurations, so check support statements before planning a replatform. Our earlier article on cloud migration strategies gives a gentler introduction.
End-of-support deadlines that trigger a move
Many Azure migrations in the UAE are started by a deadline rather than a strategy. Microsoft product lifecycles drive a lot of these decisions.
- Windows Server 2012 and 2012 R2 reached end of extended support in October 2023. Extended Security Updates are available, and servers moved to Azure receive them at no additional charge, which buys time to upgrade properly.
- SQL Server 2016 reached end of extended support in July 2026. Moving to Azure SQL Managed Instance or Azure SQL Database removes the version upgrade cycle, as Microsoft keeps the engine current.
- Windows Server 2016 reaches end of extended support in January 2027. Organisations with many 2016 servers should plan now, because in-place upgrades of application servers often need vendor input.
A deadline is a good reason to start, but a poor reason to rush. Rehosting an unsupported server into Azure keeps it running safely for a while; it does not remove the need to upgrade the operating system or the application eventually. Build the upgrade into the wave plan, so the end-of-support work is done once rather than twice.
Hardware is the other common trigger. If your servers and storage are due for refresh and the server room needs new cooling or UPS batteries, compare the refresh cost with a migration over the same five years. Sometimes keeping a smaller on-premises footprint for latency-sensitive or licensing-bound systems and moving the rest is the cheaper answer; our hybrid and multi-cloud page covers that model.
Licensing can help. Azure Hybrid Benefit lets you apply eligible Windows Server and SQL Server licences with active Software Assurance or qualifying subscriptions to Azure, which can remove a significant part of the compute price.
What migration cost estimates usually miss
Azure pricing calculators estimate the steady-state running cost. Projects run over budget because of the one-time and transition costs around it. Include these in the business case from the start:
- Dual running. For several weeks or months you pay for Azure and keep on-premises systems powered for rollback and for workloads not yet moved.
- Connectivity. A site-to-site VPN or ExpressRoute circuit, and possibly faster internet links at offices that now reach applications in the cloud.
- Application testing. Business users must test each application after migration. Their time is a real cost and a common cause of delay, particularly during Ramadan, summer leave and financial year-end.
- Vendor involvement. Some software vendors charge to re-license, re-install or certify their product on Azure.
- Licensing changes. Licences tied to physical hosts or processor counts may need to be converted. Check Oracle and other per-core licensing especially carefully.
- Backup and DR redesign. On-premises backup jobs do not follow servers into Azure. Azure Backup, and disaster recovery if required, need designing and budgeting.
- Operations. Someone has to patch, monitor and review costs after go-live, whether your team or a managed service.
- Data egress. Data leaving Azure, for example to on-premises reporting tools or another cloud, is charged.
None of these should stop a migration, but each should be visible before approval. Business cases that include them hold up better at budget review, and they avoid the experience of a first Azure invoice that nobody can explain. Our cloud migration checklist lists the questions to settle before you start.
Outcomes
What changes for your organisation
01
A reasoned route per workload
Each application is rehosted, replatformed, rebuilt, replaced or retired for a stated reason.
02
Predictable cut-overs
Waves are tested with their users and have a rollback window.
03
Known run cost
Azure spend is estimated from measured performance data, then right-sized after the move.
04
Hardware retired
Old servers are decommissioned once workloads are stable in Azure.
Approach
How emtech delivers Azure migration
- 1
Discover
Collect inventory and at least two to four weeks of performance data, and interview application owners.
- 2
Decide
Assign a migration route to each workload and agree the target region and architecture.
- 3
Prepare
Build the landing zone, connectivity and security guardrails, and run a pilot migration.
- 4
Migrate
Move workloads in waves, test each with its users and cut over with a rollback window.
- 5
Optimise
Resize, apply savings options, retire on-premises equipment and hand over to operations.
Audience
Who it is for
Firms with ageing servers
Organisations deciding between a hardware refresh and moving workloads to Azure.
Companies on another cloud
Teams moving from AWS or a hosting provider to consolidate on Microsoft.
Regulated organisations
Entities that need a UAE region and documented approvals before data moves.
ERP and SQL Server users
Businesses whose core systems need careful cut-over planning and testing.
UAE requirements
Regulations and standards
| Requirement | How this helps |
|---|---|
| UAE PDPL (Federal Decree-Law No. 45 of 2021) | Choosing a UAE region and documenting data flows during migration supports personal data obligations. |
| UAE Information Assurance Regulation | Government and critical infrastructure migrations need control mapping and approval before data moves. |
| ISO/IEC 27001:2022 | Change management, supplier and cloud service controls are evidenced by the migration plan, test records and sign-offs. |
What affects the cost
Migration cost depends on the number of servers and databases, how many applications need changes rather than a straight move, data volume, and the testing effort each business owner requires. Azure run cost then depends on sizing, operating hours, storage and licensing choices such as Azure Hybrid Benefit. Funding programmes from Microsoft are sometimes available for eligible migrations; emtech checks eligibility during assessment.
Itemised: implementation, licences, equipment and support shown separately.
Trusted since 1993
What our clients and partners say
Their staff is made up of the highest caliber of qualified people and always available whenever we need them; they assisted us throughout several IT projects and still do. We have a relationship with emtech for outsourced Infrastructure services. I recommend emtech at any time.
emtech has proven their commitment to be a professional contractor during various projects carried out with us. Their team have offered their valuable expertise whenever called upon and they possess the ability to turn around a design and build scope within critical time frames.
emtech has a broad range of technology partners and the expertise to deliver solutions and products that enable us to focus on our core business processes while ensuring efficiency, reliability, and security. In our fast-paced industry, having a reliable partner allows us to focus our energy where it matters most.
FAQs
Questions about Azure migration
Can't find your question? Ask our team.
How long does an Azure migration take?
For a typical mid-sized UAE organisation with 20 to 100 servers, three to six months from assessment to final cut-over is common, with individual waves taking a few weeks each. Application testing and change freezes usually decide the timeline more than the technical work.
Is Azure Migrate free?
Yes. Azure Migrate's discovery, assessment and server migration tools are provided at no additional charge, though you pay for the Azure resources the migrated workloads use. Some advanced dependency analysis or third-party tools integrated with it may have their own costs.
Can we migrate to Azure without downtime?
Not entirely, but downtime can usually be reduced to a short planned window per application. Servers are replicated in advance while they keep running, and the final cut-over involves a brief stop, a last sync and redirection of users.
What is Azure Hybrid Benefit?
It is a licensing benefit that lets you use eligible Windows Server and SQL Server licences with active Software Assurance or qualifying subscriptions in Azure, so you pay only the base compute rate. It can make a large difference to the business case for Windows and SQL workloads.
Do our applications need changes to run in Azure?
Most do not, if they are rehosted on virtual machines. Changes are needed when moving to managed services such as Azure SQL Database or App Service, or when an application relies on hardware such as dongles, fax boards or local serial devices.
Will Azure be cheaper than running our own servers?
Sometimes, but not automatically. Savings come from right-sizing, shutting down non-production systems out of hours, licence benefits and avoiding hardware refreshes. Servers moved as-is and left running at full size around the clock often cost more than they did on-premises.
Can we migrate to Azure from AWS or another cloud?
Yes. Azure Migrate supports moving servers from AWS and Google Cloud as well as from on-premises, and databases can be moved with Azure Database Migration Service. Plan for data transfer charges from the source cloud and differences in networking and identity.
Keep exploring
Related services and guides
Next step
Plan your Azure migration project with emtech
Tell us about your users, sites and timeline. A specialist reviews your requirement and gets back to you.
- Scoped proposal with assumptions stated
- Dubai and Abu Dhabi teams
- No obligation
Technology partnerships
