Services · Deployment and migration
Deployment andmigration services
Email, tenants, file servers and servers moved to Zoho, Microsoft 365, Google Workspace or the cloud, planned so your team keeps working.
Inventory shared mailboxes
Bulk copy of older email
Target layout agreed
Why companies trust us with their move
Zoho Authorized PartnerMicrosoft Solutions Partner and Google Cloud Premier Partner: we migrate in either direction, not only towards one vendor.
Since 2007with 1,500+ active cloud customers across the Middle East.
Offices in Dubai, Muscat and Dohawith English and Arabic support during and after the move.
350,000+ users migratedsince 2007.
Cloud migration services move your email, files, servers and business data from where they run today to Zoho, Microsoft 365, Google Workspace, Azure, Google Cloud or AWS. Gulf Infotech has planned and run these moves for companies in Oman, the UAE, Qatar and the wider Middle East since 2007, with the cut-over typically done outside working hours.
MG- Mail, files and servers · 120 users
What can we migrate, and with which tools?
We choose the tool for each project from your use case and its complexity. The vendors' own migration options come first, because they are supported and usually included with the licence; we also use BitTitan MigrationWiz for mailbox and tenant moves and SysTools for data migration where they fit better.
| Migration | From | To | Main tool | What moves |
|---|---|---|---|---|
| FromExchange 2010–2019, hosted Exchange, Zimbra, cPanel or other IMAP mail | ToGoogle Workspace | Main toolGoogle data import, or GWMME for on-premise Exchange | What movesMail; calendar and contacts from Exchange sources | |
| FromExchange on-premise | ToMicrosoft 365 | Main toolCutover, staged or hybrid migration | What movesMail, calendar, contacts | |
| FromGoogle Workspace | ToMicrosoft 365 | Main toolExchange admin center Google Workspace migration | What movesMail and rules, calendar, contacts | |
| FromMicrosoft 365 or Exchange Online | ToGoogle Workspace | Main toolGoogle data import | What movesMail, calendar, contacts, OneDrive files | |
| Tenant to tenant | FromOne Microsoft 365 tenant | ToAnother Microsoft 365 tenant | Main toolCross-tenant mailbox and OneDrive migration | What movesMailboxes and OneDrive, per-user licence needed |
| Files | FromWindows file server, NAS | ToSharePoint, OneDrive, Teams | Main toolMicrosoft Migration Manager | What movesFolders and files, up to 250 GB per file |
| Files | FromWindows file server, Box, Dropbox | ToGoogle shared drives | Main toolGoogle Workspace Migrate (file shares, Box Enterprise) or Google data import (Dropbox, up to 100 users) | What movesFiles and, where supported, permissions |
| Servers | FromVMware, Hyper-V, physical servers | ToAzure, AWS, Google Cloud | Main toolAzure Migrate, AWS Transform MGN, Migrate to Virtual Machines | What movesWhole servers, as they are |
| Business apps | FromSpreadsheets, Tally, QuickBooks, other CRMs | ToZoho | Main toolZoho import tools and our scripts | What movesCustomers, items, balances, history |
IMAP-only sources carry mail but not calendars or contacts, so we export and import those separately. Details per platform: Google Workspace migration, Microsoft 365 migration, lift-and-shift server migration and migrating to Zoho.
How do we migrate without stopping your business?
We copy data in the background while you keep working, then switch over in a short, planned window.
Rollout plan
InventoryStep 1
we list mailboxes, shared mailboxes, aliases, groups, file shares, servers and their sizes, and note anything that will not move as-is.
DesignStep 2
we decide the target layout (domains, shared drives or SharePoint sites, server sizes), the batches and the cut-over date.
PilotStep 3
a small group of users or one test server moves first, so we can fix permissions, mobile setup and app issues early.
Bulk copyStep 4
older email, files and server disks copy across while users stay on the old system.
Cut-overStep 5
we switch MX records or point users to the new system outside working hours, typically on the evening before the weekend. A final sync picks up the last changes.
Clean-up and supportStep 6
we check reports, re-run failed items, set up phones and Outlook or Gmail, and keep the old system read-only until you are happy.
Which migration types need extra care?
Three cases take more planning than a standard mailbox move.
On-premise Exchange. Microsoft's cutover method suits up to 2,000 mailboxes, but Microsoft itself recommends 150 or fewer for a single cutover. Larger or newer Exchange estates (2013 and later) usually go through a hybrid setup, which lets users move in batches while mail flows between both systems.
Tenant to tenant. Mergers and rebrands often leave two Microsoft 365 tenants. Microsoft's cross-tenant migration moves mailboxes and OneDrive but needs a one-time Cross Tenant User Data Migration licence per user, so we include it in the budget from day one. Domain moves between tenants also need a short window where the domain is removed from one and added to the other.
Large Google Workspace estates. Google's standard data import handles Exchange Online moves up to 1,000 users. Above that we use Google's advanced data import. Google is withdrawing Google Workspace Migrate for Exchange Online, SharePoint Online and OneDrive at the end of 2026, so we no longer plan new projects from those sources on it.
What does a migration cost?
Migration is quoted per mailbox, from AED 100 a mailbox, and the price rises with the volume of data, the source system and how many batches you need. A 20-user move from hosting-company IMAP mail is a small job; a 500-user Exchange hybrid move with file shares is a project with its own plan. Third-party tools such as BitTitan MigrationWiz or SysTools, where needed, and Microsoft's cross-tenant licences are shown as separate lines. Migration is always charged separately from licences.
Migration support in your country
IT and cloud company in Oman
Muscat head office; migrations run remotely.
Learn more: IT and cloud company in OmanGulf Infotech in the UAE
Dubai office in JLT.
Learn more: Gulf Infotech in the UAEGulf Infotech in Qatar
Doha office.
Learn more: Gulf Infotech in QatarGulf Infotech in Saudi Arabia
served from Dubai.
Learn more: Gulf Infotech in Saudi Arabia
Frequently asked questions
How long does a cloud migration take?
A cloud migration for a small office typically takes one to two weeks from kick-off to cut-over, most of it planning and background copying. Larger moves with several hundred mailboxes, file shares or servers run over several weeks in batches. The cut-over itself is usually one evening or weekend. Data volume, the source system and how quickly DNS and admin access are handed over set the pace. These durations are indicative estimates, not fixed commitments: they depend on your number of users, the complexity, your current setup, the requirements of the new platform and the availability of your team and decision-makers.
Will there be downtime?
Usually there is no email downtime. We copy older mail and files in the background, then switch MX records outside working hours so new mail lands in the new system straight away. Users may need to sign in again and set up their phones. Server moves have a short planned cut-over window per application, which we schedule for an evening or weekend and agree with you in advance.
What does migration cost?
Migration is priced per mailbox, from AED 100 a mailbox, not per hour. The final quote depends on the amount of email and file data, the source system and the number of batches. We list tool or licence costs separately, for example Microsoft's one-time per-user licence for tenant-to-tenant moves. Send us your user count and current system and we will return a fixed quote.
Do you migrate from on-premise Exchange?
Yes. We migrate Exchange Server 2010 to 2019 to Zoho Workplace, Microsoft 365 or Google Workspace. For Microsoft 365 we use cutover migration for smaller estates and a hybrid setup for larger or newer ones, so mail, calendars and contacts move in batches. For Google Workspace we use Google's migration tool for Exchange, which also handles PST files and public folders.
What is a tenant-to-tenant migration?
A tenant-to-tenant migration moves users, mailboxes and OneDrive files from one Microsoft 365 organisation to another, typically after a merger, acquisition or rebrand. Microsoft's native cross-tenant tools need a one-time licence per migrated user; depending on the case we use them or BitTitan MigrationWiz. We also plan the domain move, Teams and SharePoint content, and the order of batches so that both companies can email each other throughout.
Can we move from Microsoft 365 to Google Workspace, or the other way?
Yes. Both directions use the vendors' own tools: Google's data import moves mail, calendars, contacts and OneDrive files into Google Workspace, and Microsoft's Google Workspace migration moves mail, calendars and contacts into Exchange Online. Drive files go to SharePoint or OneDrive with Migration Manager. See our Google Workspace vs Microsoft 365 comparison before deciding.
Plan your migration with us
Tell us your user count, current email or server setup and target platform, and we will send a migration plan and quote.
