Move mail, files and teams without losing a working day.
Tenant-to-tenant moves, Google Workspace to Microsoft 365 and on-premises Exchange to Exchange Online. Planned, tested and cut over as one migration, with DNS, identity and security handled in the same plan.
Migrations we deliver
| Scenario | Typical reason |
|---|---|
| Tenant to tenant | Acquisition, merger, divestment or a brand consolidating several Microsoft 365 tenants into one. |
| Google Workspace to Microsoft 365 | Standardising on Microsoft tools, licensing or a parent company requirement. |
| Exchange on-premises to Exchange Online | Retiring ageing servers and moving to a supported cloud platform. |
What moves
- Email, calendars and contacts for user, shared and resource mailboxes
- Files from OneDrive, Google Drive and SharePoint sites, with permissions mapped
- Groups and distribution lists, with membership and owners
- Teams: teams, channels and files, with any limits on chat history agreed up front
- Domains and DNS: MX, SPF, DKIM, DMARC and Autodiscover, moved in a planned window
- Security settings: MFA, conditional access and admin roles set up in the destination before users arrive
How a migration runs
- Discovery. Inventory of users, mailboxes, data sizes, sites, groups, devices, apps that sign in with Microsoft or Google, and every DNS record involved.
- Design. Identity and naming in the destination, the tool for each workload, the cutover date and the rollback plan, agreed in writing.
- Pilot. A small group moves first. We fix what the pilot finds before anyone else moves.
- Pre-stage. The bulk of mail and files is copied in the background while people keep working.
- Cutover. Domain and DNS switched in a planned window, usually outside working hours, followed by a final sync of recent changes.
- Day-one support. Outlook, OneDrive and mobile devices reconnected, issues handled the same day, and a handover document at the end.
What you receive
- A written migration plan with scope, dates and rollback steps
- User communications and a short guide for the first morning
- Progress reports during pre-stage and a migration report at the end
- Documentation of the destination tenant: users, groups, DNS and security settings
Common questions
How long does it take?
For 20 to 100 users, usually two to four weeks from discovery to cutover. Data volume and the number of workloads matter more than the user count.
Will users need new passwords?
In a move to a new tenant, yes: accounts in the destination are new. We plan the first sign-in, MFA registration and communication so it takes minutes on the day.
What about licensing?
The destination needs the right Microsoft 365 licences before cutover. Migration tools are licensed per user, whether Microsoft's own cross-tenant migration add-on or a third-party tool. We include the choice and the cost in the plan.
Can you work under our brand?
Yes. For IT providers and MSPs we deliver migrations as a subcontractor, under your name and your processes.
Read more
Planning a merger, a move or a platform change?
Tell us the source, the destination and the number of users. We will come back with a plan and a fixed scope.
Email contact@kullatech.com