Audit and plan
We list all mailboxes, groups, domains, file volumes and the systems that send email. We select licences, the tool and the date. You receive a plan with what we do and what you need to do.
Microsoft 365 migration
We migrate mail, calendars, contacts and files to Microsoft 365 from Google Workspace, on-premises Exchange, IMAP hosting or another Microsoft 365 tenant. We plan it so that on Monday employees simply open Outlook and work.
Built for ISO 27001NIS2 DORA
- Mailboxes
- Calendars and contacts
- Shared mailboxes and groups
A migration that employees barely notice
- 4 sources: Google, Exchange, IMAP, another tenant
- Weekend main migration and DNS cutover after hours
- Pilot migration before the main one, no surprises
- MFA and Conditional Access on from day one
A company decides to move to Microsoft 365, but its mail lives on a hosting server with IMAP, its calendars in Google, its files on an old shared network drive, and some employees have several email addresses. The biggest fear is not the technology but Monday: will the emails arrive, will the old folders be there, will the phone work. In our experience, migrations fail not because of the tools but because of a skipped audit and a missed pilot migration: someone forgets a shared mailbox, a printer that sends scans, or an accounting program that sends invoices through the old server.
That is why we start with an audit: we list all mailboxes, shared mailboxes, distribution groups, domains, file volumes and everything that uses mail without a person, such as printers, accounting programs and website forms. Then we prepare the Microsoft 365 tenant: connect the domains, create Entra ID accounts, and turn on multifactor authentication and Conditional Access. We run a pilot migration for a few mailboxes to see the real speed and problems. We do the main migration outside working hours, usually over a weekend, switch DNS, and on Monday morning we are available to every employee. We use Microsoft's migration tools for Exchange and SharePoint, and third-party tools for more complex cases. The old system keeps running for a few more weeks until we are sure nothing is missing, and only then do we shut it down.
What we migrate and configure
A migration is finished not when the emails are copied but when every employee is working in the new environment.
Mailboxes
Emails with all folders, labels and attachments, rules and signatures. Archives from PST files or old servers go to the Exchange Online archive where the licence allows.
Calendars and contacts
Personal and shared calendars with recurring events, contact lists, room and resource calendars. We double-check that meeting attendees are preserved.
Shared mailboxes and groups
info@, accounting@ and other shared mailboxes, distribution groups, aliases. We define who can send on behalf of a shared mailbox.
Files to SharePoint and OneDrive
File server folders and Google Drive go to SharePoint sites by department, personal files go to OneDrive. We carry over permissions and fix overly long paths and disallowed characters.
Teams and SharePoint between tenants
When migrating from another Microsoft 365 tenant: Teams teams, channels and their files, SharePoint sites, Planner tasks. Chat history depends on the tool and what is possible.
Domains and DNS
We verify the domains in the new tenant, prepare the MX, SPF, DKIM and DMARC records and switch them at the agreed time. Mail flow is redirected until DNS changes propagate.
Workstations and phones
We configure Outlook on computers, mail and calendar on phones, and the Teams and OneDrive apps. We reconnect printers, accounting programs and website forms that send email.
Security from day one
Multifactor authentication for everyone, Conditional Access, protection against phishing emails, separate administrator accounts. Microsoft 365 backup is a separate service.
Where we migrate from and what is moved
The four most common sources and what can be moved from each.
| Google Workspace | On-premises Exchange | IMAP hosting | Another tenant | |
|---|---|---|---|---|
Emails with folders | ||||
Calendars and contacts | only from client apps | |||
Shared mailboxes and groups | recreated manually | |||
Files | Google Drive to SharePoint and OneDrive | file server to SharePoint | file server to SharePoint | OneDrive and SharePoint sites |
Teams teams and channels | yes, chat history is limited | |||
Passwords | new, with MFA | new, or synced with AD | new, with MFA | new, with MFA |
Tool | Microsoft migration tools | hybrid Exchange migration | IMAP migration | third-party tools |
Downtime | no downtime | no downtime | at DNS cutover | no downtime |
Migration stages
One week for a small company, 2-4 weeks for a larger one with a file server.
Tenant preparation and pilot migration
We create the Microsoft 365 tenant, verify the domains, create Entra ID accounts and groups, and turn on MFA and Conditional Access. We migrate a few mailboxes and a file folder and check speed and completeness.
Main migration and DNS
We migrate the remaining mailboxes and files, switch MX and other DNS records, and verify that email reaches the new environment while the old one still catches anything that arrives late. We run a final delta sync.
Workstations, support, training
We configure Outlook, Teams and OneDrive on computers and phones and reconnect printers and applications. In the first week our helpdesk responds to every question, and after that we run training for employees.
The new environment is only as secure as you configure it
After the migration we turn on Defender, Intune, Purview and Conditional Access according to your licence, as a separate Microsoft 365 security service.
Frequently asked questions
Will there be downtime during the migration?
Mail keeps working throughout: the old system receives emails until DNS changes, and the new one receives them immediately after the cutover. The short period when a message may still arrive in the old mailbox is closed by a final sync. We switch the file server over when employees are not working.
Will email addresses change?
No. We connect the domain to the Microsoft 365 tenant, and the addresses stay the same, including aliases and shared mailboxes. If you want to change the domain or address format at the same time, we plan it as a separate step.
Will employees need new passwords?
Yes, passwords from Google, hosting or another tenant are not migrated. Employees receive an initial password and change it with multifactor authentication. If you have an on-premises Active Directory, we can turn on Entra Connect synchronisation so there is only one password.
How long does a migration take?
For a company with a few dozen mailboxes and no file server, a week from audit to cutover. With a file server or large Google Drive volumes, 2-4 weeks, because file copying runs in the background for several days.
Do we need backups after the migration?
Microsoft protects the infrastructure, but not your deleted emails or files beyond the set retention period. We recommend Microsoft 365 backup as a separate service: it protects Exchange, OneDrive, SharePoint and Teams data in our data centre in Lithuania (EU).
Related services
Microsoft 365 security
Most incidents in companies start with a forged email or a stolen password.
Microsoft Entra ID
We manage your company's identities in Microsoft Entra ID: single sign-on to Microsoft 365 and other systems, MFA for everyone, conditional access…
Microsoft Power Platform
We build business apps and automate processes with Microsoft Power Platform tools, most of which are already in your Microsoft 365 licence.
Expertise confirmed by certifications
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
-
Lead Cloud Security Manager
Cloud security is managed following ISO/IEC 27017 and 27018 practices.
-
ISO/IEC 27001 Lead Implementer
The service is delivered in line with the requirements of an ISO/IEC 27001 management system.
Get a quote for Microsoft 365 migration
Tell us where you are migrating from and how many mailboxes you have, and we will send a plan with stages and a date within 1 business day.
We reply within 1 business day