Microsoft 365 migration

Microsoft 365 migration for growing companies

We move your mailboxes, calendars, contacts, shared mailboxes, files and archives into a Microsoft 365 tenant that we configure beforehand. Your staff keep working on the current system until the agreed switch date, usually a weekend.

  • Fixed price
  • Pilot group first
  • Switch over a weekend

Key facts

Sources
Google Workspace, Exchange, Lotus Notes, hosted mail, file servers
Typical duration
4 to 8 weeks for about 100 users
Mail flow
Uninterrupted during the project
Pricing
Fixed, quoted within one week
Request a quote

Common situations

Why companies contact us about a migration

The decision to move is usually triggered by one of the following. Often it is several at once.

Mail spread across several providers

Mailboxes hosted in different places, several domains, and no clear view of who has access to which mailbox.

An ageing on-premises server

An Exchange or file server that is out of support, or that only one person really knows how to maintain.

Lotus Notes or Domino still in use

Mail and internal applications built years ago, with license costs and fewer people able to support them every year.

Google Workspace no longer fits

Clients, partners and business software work with Office files and Teams, and switching between formats costs time daily.

Files stored in too many places

A shared drive, a NAS, personal Dropbox accounts and email attachments, with no reliable way to know which version is current.

A move that has been postponed

Everyone agrees the company should move, but the risk of disrupting email has kept the project on hold.

Scope

Scope of a migration project

We configure the destination tenant first, then move your content into it. Security, structure and permissions are settled before the first mailbox is copied.

Tenant configuration

The Microsoft 365 environment is prepared before any content moves.

  • Domains and DNS records
  • User accounts and groups
  • Security baseline and multi-factor authentication

Mailboxes

Each mailbox is moved with its full history.

  • Email, folders and rules
  • Calendars and meeting history
  • Contacts and distribution lists

Shared mailboxes and resources

Shared addresses are recreated and moved.

  • Shared mailboxes such as info@ or sales@
  • Meeting rooms and equipment
  • Aliases and forwarding rules

Files and drives

Personal and shared files are moved to OneDrive and SharePoint.

  • File servers, NAS, Google Drive, Dropbox and Box
  • Folder permissions mapped and reviewed
  • Path lengths and file names corrected beforehand

Archives

Older mail that still has value is kept and remains searchable.

  • PST files imported
  • Online archives where needed
  • Agreed list of what is left behind

Devices and users

Staff can log in and work on the first day.

  • Outlook and Teams on computers and phones
  • Instructions for each user
  • Support during the first days

Method

How a migration project runs

Every migration follows the same six phases. The tools and the waves change with your platform and your size.

  1. Phase 01

    Discovery and inventory

    We list everything that has to move and everything that has to keep working.

    • Users, mailbox sizes and shared resources
    • File shares, volumes and permissions
    • Devices, applications and dependencies
  2. Phase 02

    Plan and quote

    You receive the migration plan with the scope, the waves, the schedule and the fixed price.

    • Migration method for each source
    • Pilot group and waves
    • Switch date
  3. Phase 03

    Tenant configuration

    The new tenant is ready before content is copied.

    • Domains, accounts, groups and licenses
    • Security baseline
    • SharePoint and Teams structure if included
  4. Phase 04

    Pre-staging and pilot

    Content is copied in the background while staff keep working. A pilot group switches first.

    • Bulk copy of mail and files
    • Pilot users work on the new tenant
    • Corrections before the rest of the company
  5. Phase 05

    Switch

    On the agreed date, usually a weekend, incoming mail is redirected to Microsoft 365.

    • DNS records updated
    • Final synchronization of recent content
    • Checks on mail flow, files and access
  6. Phase 06

    First days and handover

    We stay available while staff settle in, then hand over the documentation.

    • Help with devices and first logins
    • User guides in English or French
    • Tenant documentation

How mail keeps flowing

Mail continues to arrive in the current system for the whole project. Content is copied in advance, the switch only redirects new mail, and a final synchronization brings over anything received in between.

Sources

What we migrate, by source platform

Each platform has its own limits. The table covers the sources we work with most often. For anything else, contact us.

Source Email and calendars Contacts Files Notes
Google Workspace Yes, labels become folders Yes Google Drive to OneDrive and SharePoint Google formats converted to Office files
Exchange Server on-premises Yes, full history Yes Public folders on request Hybrid or cutover method depending on size
Lotus Notes and HCL Domino Yes, including calendars Yes Attachments included Notes applications are rebuilt or archived
Hosted mail and IMAP (OVHcloud and others) Email, yes Export and import Not applicable Calendars depend on the provider
File servers and NAS Not applicable Not applicable Yes, permissions mapped Folder structure reviewed during the move
Dropbox and Box Not applicable Not applicable Yes, team and personal folders Shared links recreated where needed
Another Microsoft 365 tenant Yes Yes OneDrive, SharePoint and Teams Mergers, acquisitions and rebranding

Deliverables

A configured tenant, your content, and the documentation to run it

At the end of the project your company works in a documented, secured Microsoft 365 tenant, ready for the next steps such as Teams, information architecture or Copilot.

What you receive

  • Migration plan and schedule
  • Microsoft 365 tenant configured and secured
  • Mailboxes, calendars and contacts migrated
  • Files migrated with reviewed permissions
  • Migration report listing what moved and what was left behind
  • Administration documentation
  • User guides in English or French
  • Post-migration support period

Client stories

Recent migration projects

We do not name our clients, only their type of business and country.

Four countries, four storage tools, one tenant

The situation

Each subsidiary had organized itself on its own: Synology NAS in some offices, Dropbox in one, Box in another, and many employees keeping work files in personal Google Drive accounts.

Why they did it

Head office could not say where a contract or a drawing was, or who could open it. When someone left, their files often left with them, and every site paid for its own storage.

What we did

One tenant for the whole group, with shared identity, security and naming rules. We inventoried every source, agreed with each subsidiary what to move and what to archive, then migrated one country at a time, pilot group first. Network conditions in China were tested before the switch.

What changed

About 9 TB of files moved in 14 weeks. All company files now sit in one place under the same structure in every country, access is removed in one step when someone leaves, and the Dropbox, Box and NAS subscriptions were cancelled.

Leaving Google Workspace to answer corporate security questionnaires

The situation

Four consultants on Google Workspace, with files spread across laptops, Google Drive and a few SharePoint folders.

Why they did it

Their largest prospects sent security questionnaires before signing: multi-factor authentication, audit logs, data protection. With files on laptops, most of the answers were no.

What we did

Mailboxes moved to Microsoft 365 Business Standard, multi-factor authentication enforced for everyone, and one SharePoint site per client engagement, with its own permissions and a drop folder for client documents.

What changed

The firm answered its next corporate security questionnaire in two days, with evidence for every control. Confidential documents no longer travel by email.

Leaving Lotus Notes without losing the right to disconnect

The situation

Email on Lotus Notes, with rules built over the years: no access outside working hours without the VPN, an automatic reminder to anyone sending mail at night, and exceptions for management and on-call staff.

Why they did it

Lotus Notes was costly to keep and fewer people could support it, but the company did not want to give up its commitment to the right to disconnect.

What we did

Workshops first, then a written specification of how disconnection worked in Lotus Notes. We rebuilt the equivalent in Microsoft 365: quiet hours, sender reminders, access rules, reporting of off-hours sending and the same exceptions.

What changed

Mailboxes moved over one weekend. Quiet hours and reminders worked from the first Monday, and management now receives a monthly report of off-hours sending straight from Microsoft 365.

Our approach

How we keep migrations predictable

Fixed price

The price in the quote covers the agreed scope. Changes are discussed and approved before any extra work.

Automated checks

Our own tooling handles inventory, provisioning and post-migration checks, which reduces errors and shortens the project.

Pilot group

A small group moves first, so issues are found and fixed before the rest of the company switches.

Dedicated project lead

One project lead follows your migration from the discovery call to the handover.

Questions

Frequently asked questions about migration

Will our staff experience downtime?

No planned downtime for mail. Staff use the current system until the switch, which happens on an agreed date, usually over a weekend. On the following working day they open Outlook and Teams on the new tenant.

How long does a migration take?

For about 100 users, four to eight weeks from kickoff to the switch is typical. Data volume, the number of sources and your team’s availability make the difference. Your quote includes the schedule.

Can you migrate old emails and archives?

Yes. Full mailbox history is migrated by default. PST archives can be imported, and online archives can be set up for large mailboxes.

What happens to our Lotus Notes applications?

Notes applications cannot be copied as they are into Microsoft 365. In workshops we decide with you which ones to rebuild with SharePoint or the Power Platform, which to archive and which to retire.

Do we need new computers?

Usually not. Outlook, Teams and OneDrive run on recent Windows and Mac computers and on phones. We check your devices during discovery and flag anything that needs an update.

Who buys the Microsoft 365 licenses?

You do, from your current provider or directly from Microsoft. We specify which plans you need. Our licensing service can go further and review the whole mix.

What if something goes wrong during the switch?

Every switch has a rollback plan. Because content is copied in advance and the pilot has validated the method, the switch itself is a small, controlled step.

Request a quote

Describe your setup on the quote form. After a short discovery call, we send a written, fixed quote within one week.

Quote form
About five minutes
Discovery call
45 minutes, by video
Written quote
Fixed price, within one week
Request a quote

Related services

Services often combined with this one

When several services are part of the same project, we plan them together and send a single quote.

Plan your migration

Describe your current setup and you will receive a written, fixed quote within one week of the discovery call.