Damco

Microsoft 365 migration services with nothing lost on the way Mail, files, Teams, and users moved in planned waves, over weekends

Wave 2 of 4, finance and HRIllustrated
Mailboxes180, from Exchange 2016
File shares2.1 TB to SharePoint and OneDrive
CutoverSaturday, 8 pm
Checked byIT lead, Monday 7 am

Office 365 migration services, from plan to support Everything between your old mail server and people working in Microsoft 365

Plan the migrationWe count mailboxes, files, and apps, and set the order of the waves.
Move mail, files, and TeamsExchange, Google Workspace, file shares, or another tenant, moved in waves.
Set security from day oneSign-in, retention, and data loss rules switched on before users arrive.
Train and support your peopleShort sessions per team, and a help desk for the first week.

How our Microsoft 365 migration works Five steps, each wave cut over outside working hours

  1. Week 1AssessWe inventory mailboxes, shares, sites, and the apps that send mail.
  2. Week 2Agree the planYou approve the waves, the cutover dates, and what gets archived.
  3. Weeks 3 to 8MigrateWe copy data ahead of time, then cut each wave over on a weekend.
  4. After each waveSupportA help desk answers questions and fixes issues the first week.
  5. At the endDocument and hand overYour IT team gets the settings, the runbook, and admin training.

When Microsoft 365 migration services are the right fit And when your IT team can run it alone

A good fit when

  • You're leaving Exchange on-premises, Google Workspace, or Lotus Notes
  • A merger means two Microsoft 365 tenants must become one
  • You have years of file shares nobody wants to sort by hand

Look elsewhere when

  • You have under 20 mailboxes and no file shares to move
  • You need a license reseller, not a migration
  • You're already on Microsoft 365 and need an intranet: see SharePoint

Our Microsoft 365 migration services in detail What each part covers, and what you have at the end of it

Office 365 migration consulting

Every migration starts with a count: how many mailboxes, how many terabytes of files, which apps send mail, and which users share calendars. We turn that into waves, usually by department, so the people who work together move together.

You end with a plan that names each wave, its cutover date, and what's archived instead of moved.

Migration from legacy platforms

We move mail and files from Exchange 2013, 2016, and 2019, Google Workspace, Lotus Notes, and IMAP servers. Files on old Windows shares go to SharePoint for team content and OneDrive for personal files, with permissions mapped from the old folders.

  • Exchange on-premises to Exchange Online
  • Google Workspace to Microsoft 365
  • File shares to SharePoint and OneDrive
  • Slack or Skype for Business to Teams

Microsoft 365 tenant-to-tenant migration

After a merger or a sale, two companies often need to become one tenant, or one division must leave. We move mailboxes, OneDrive, SharePoint sites, and Teams between tenants with Microsoft's native tools where they work, and keep mail flowing to both domains during the move.

A tenant-to-tenant move usually has a legal date behind it, such as the day a sale closes. We plan backward from that date, run a pilot with 20 users, and keep a rollback plan ready for each wave.

Security and compliance in Microsoft 365

We switch on multifactor sign-in, conditional access, retention policies, and data loss rules in Microsoft Purview before users arrive. That way, sensitive files land under the right rules from their first day in Microsoft 365, not months later.

Custom integrations

Printers, scanners, line-of-business apps, and websites often send mail through the old server. We find each one in week 1 and reconnect it to Exchange Online, so invoices and alerts keep going out after cutover.

Managed services, training, and support

Each team gets a short session on the tools it'll use most: Outlook, Teams, and OneDrive. After the last wave, we can run your Microsoft 365 tenant for you, covering licenses, user changes, and security alerts.

Questions about Microsoft 365 migration What buyers ask us before they start

Do you offer Microsoft 365 migration support?

Yes. We plan and run the migration, then run a help desk for the first week after each wave. After the last wave, we can manage your Microsoft 365 tenant on a monthly plan.

Do you support Microsoft 365 migration from legacy platforms?

Yes. We move mail and files from Exchange on-premises, Google Workspace, Lotus Notes, IMAP servers, and Windows file shares. Each source has its own tools and checks, and we pick them in the assessment.

How long does it take to migrate to Microsoft 365?

It depends on the number of mailboxes, the volume of files, and how many waves you want. We copy data ahead of each cutover, so the switch itself happens over a weekend and people start Monday in Microsoft 365.

How do I keep my data secure during a Microsoft 365 migration?

Data moves over encrypted connections, and we set access, retention, and data loss rules in the new tenant before anything lands. We count items before and after each wave, so nothing is missing.

What types of data can be migrated to Microsoft 365?

Email, calendars, contacts, archives, file shares, SharePoint sites, OneDrive files, and Teams chats and channels. Some items, such as old public folders, may be archived instead of moved, and we agree that with you first.

Can we migrate from Google Workspace to Microsoft 365?

Yes. We move Gmail, Google Calendar, contacts, and Google Drive files to Exchange Online, OneDrive, and SharePoint. Google Docs and Sheets are converted to Word and Excel files, and we test a sample of each file type before the main waves.

Tell us what you're moving to Microsoft 365

We'll count it with you and sketch the waves and cutover dates, in one working session.