• About us
    About us
    question mark
    Who we are

    Learn more about Mantu values, governance and offices.

    hexagon
    Our brands

    11 brands united by a shared vision.

    leave
    Sustainability

    Our strategy through diversity, environment and innovation.

    bookshelf
    Pressroom

    Breakthroughs, partnerships, and voices behind the transformation.

  • What we do
    What we do
    mantu
    PRACTICES

    Four practices designed to empower organizations, connect talent, and shape sustainable growth.

    cpu
    Technology

    Deep industry knowledge & cutting edge technology to co-create meaningful solutions.

    handshake
    Total Talent Management

    Tech to boost talent and create strong links between companies and the minds they need.

    digital qr
    Creative Intelligence

    Ensure continuity between decision, activation, and adoption. One team, one trajectory, through to lasting impact.

    medal
    Leadership & Advocacy

    Equip executive teams to define their purpose, shape their positioning and drive their strategy.

  • Insights
    Insights
    book open 4
    Blog

    Bold thinking. Fresh perspectives.

    book check
    Client Stories

    Where audacious ideas turn into real stories.

    mantu best managed companies award
    Mantu awarded one of Switzerland’s Best Managed Companies 2025 by Deloitte

    This award highlights the exceptional performance of privately held Swiss companies that demonstrate excellence in strategy, governance, innovation, and long-term results.

    Read more
    WeMeet 2025-2772 1 1
    Mantu signs the DEI Charter

    At the beginning of July 2025, Mantu’s Executive Committee signed the DEI Charter to foster diversity, equity, and inclusion at Mantu.

    Read more
  • Careers
    Careers
    binoculars
    Life at Mantu

    Mantu, as seen by its team members.

    building
    Find a company

    Mantu brings together complementary brands that cover many sectors, all around the world.

on-premise-to-cloud-microsoft-365-benefits-risks-and-migration-checklist

On-premise to cloud Microsoft 365: benefits, risks and migration checklist

An on-premise to cloud migration to Microsoft 365 affects identity, data, security and daily work, not only email.

This checklist helps you weigh the benefits and risks, choose a migration path, test dependencies and plan a controlled cutover.

What does an on-premise to Microsoft 365 migration involve?


Moving from on-premises infrastructure to Microsoft 365 is a change to how the organisation provides email, files, collaboration, identity and endpoint services. It is not only a mailbox transfer. The migration may include Exchange mailboxes, calendars, contacts, shared mailboxes, file shares, SharePoint sites, OneDrive, Teams, Office applications, device management, DNS, authentication and business applications.

The scope depends on the starting environment and the target operating model. A small organisation may move users in one cutover, while a larger enterprise may need coexistence between on-premises Exchange and Exchange Online. File repositories, legacy applications and compliance data may require separate workstreams rather than one technical migration.

Define the scope before moving data. Include the systems that send email, read directory information, use file paths, depend on shared calendars or apply retention rules. A transfer can appear successful while a scanning system, forwarding rule or delegated mailbox permission has stopped working.

What benefits can Microsoft 365 deliver?


Microsoft 365 can reduce the amount of infrastructure that the internal team has to host, patch and refresh. The provider manages the underlying cloud service, while the customer manages the tenant, identities, permissions, devices, policies, applications and user experience. The benefit is a different allocation of operational work, not the removal of responsibility.

Cloud access can also support collaboration across offices and locations. Users can work with mail, documents, calendars and Teams without relying on the same local network. This works best when permissions, workspace ownership, external sharing and support processes are designed as part of the move.

A subscription model can make capacity planning more flexible than buying servers and storage several years ahead. It still requires careful decisions about licence levels, storage, archive data, security features, backup and retention. A migration business case should compare both the project cost and the long-term operating cost.

Microsoft 365 can become a foundation for wider infrastructure modernisation when it is connected to identity management, endpoint controls, security monitoring and application planning. Moving workloads without reviewing those dependencies can leave legacy processes in place and create new support issues.

Which risks should you assess before migration?


Identity is one of the most important dependencies. Review the directory structure, synchronisation rules, authentication methods, multi-factor authentication, privileged accounts, guest users, service accounts and joiner, mover and leaver processes. A failed identity change can remove access to email, files, Teams and business applications at the same time.

Security controls also need to be designed before migration waves begin. A cloud service does not remove the need to manage tenant configuration, identities, data access, application consent, device posture, audit logging, retention and alerting. A Cloud Strategy & Security review can help connect those controls to the target architecture and risk model.

Data validation is another major risk. Record the source baseline for mailbox counts, file volumes, site structures, ownership, sharing permissions, delegated access, version history, archive data and obsolete content. A migration tool can report that a job completed even when files are unsupported, permissions changed or a business user cannot find a required document.

Finally, create a dependency register for applications, ERP and CRM platforms, scanning and printing systems, SMTP relays, archive products, backup tools, monitoring systems and supplier connections. Test each integration in the target environment before retiring the source service.

How do migration approaches differ?


Approach

Best fit

Main trade-off

Cutover

Smaller environments with limited dependencies

Short coexistence, but problems can affect everyone at once

Staged

Teams that need migration waves and learning

Requires clear coexistence, routing and support rules

Hybrid

Large or complex Exchange environments

More flexibility, but two administrative models run together

A cutover migration moves users in a concentrated window. It can be efficient when the environment is small, well understood and easy to validate. Its risk is concentration: a problem with mail flow, identity or permissions can affect the whole organisation.

A staged migration moves users in batches. It gives the project team time to test representative groups, fix defects and improve communications. It also requires rules for coexistence, shared calendars, address lists, routing and support across both platforms.

A hybrid approach connects on-premises Exchange with Exchange Online while mailboxes move in phases. It can support a controlled transition, but it adds work for synchronisation, routing, permissions, monitoring and troubleshooting. Set an end date for coexistence so the temporary architecture does not become permanent.

How should you prepare the target tenant?


Start with the target operating model rather than copying the old environment. Define the tenant and domain configuration, identity architecture, administrator roles, authentication methods, device policies, application controls, Teams and SharePoint governance, external sharing and support ownership.

A Cloud Strategy & Security review can help align tenant configuration, identity controls, security policies and cloud adoption decisions before the first production wave.

Plan information governance at the same time. Decide how retention, archive data, legal holds, sensitive information and external sharing will be handled. Clarify who owns Teams spaces, SharePoint sites and shared mailboxes. Without ownership, the tenant can accumulate orphaned content and permissions that no one reviews.

What should a Microsoft 365 pilot test?


Select a representative pilot group rather than only the easiest users. Include different mailbox sizes, devices, locations, business roles and application dependencies. The pilot should expose the conditions that make a migration difficult, not simply confirm that a basic mailbox can sign in.

  • Authentication, multi-factor authentication and access from managed and unmanaged devices

  • Mail flow, calendars, delegates, shared mailboxes, mobile access and meeting invitations

  • File permissions, SharePoint access, Teams collaboration and external sharing

  • Business applications, scanning, printing, automated email and archive integrations

  • Service desk procedures, user communications, data validation and rollback decisions

Record defects by owner, severity, workaround and target fix. Do not increase the migration volume until the pilot has passed technical validation and business users have confirmed that they can complete normal tasks.

How should you plan migration waves and cutover?


Each migration wave needs a defined scope, owner, communication plan, technical runbook, support contact, validation checklist, maintenance window and completion criterion. The runbook should document the order of synchronisation, DNS changes, mail routing, identity changes, application tests and user support.

Set rollback triggers before the cutover begins. Examples include failed authentication for a material user group, broken mail flow, missing business data, a critical integration failure or an inability to restore the source service. A rollback decision should have one accountable owner and a time limit, rather than being debated during an outage.

  1. Confirm the wave scope, source baseline, dependencies and user communications.

  2. Synchronise data and verify that identity, routing and permissions are ready.

  3. Execute the cutover in the agreed sequence and monitor technical signals.

  4. Validate business tasks, resolve defects and record the go or no-go decision.

How do you validate the environment after migration?


Compare the target environment with the source baseline. Technical completion metrics are useful, but they do not prove that the new environment supports the work people need to do. Ask business users to confirm normal workflows, including email, calendars, file access, Teams meetings and application tasks.

Post-migration checks should cover mailbox and file counts, mail delivery, delegate permissions, site access, mobile devices, meeting policies, security alerts, backup and restore processes, support tickets and unresolved exceptions. Keep the results in the project record so acceptance is based on evidence.

Monitoring should continue after the first successful day. Track authentication failures, mail flow errors, application incidents, external sharing changes, service desk themes and user feedback. The first weeks after a wave often reveal issues that did not appear in a controlled test.

When can legacy infrastructure be retired?


Do not decommission the source environment immediately after the last mailbox moves. Keep it recoverable until the migration has passed acceptance criteria, required data has been validated and critical applications have been tested. The retention period should reflect business risk and recovery requirements.

Before retirement, confirm that all users and shared mailboxes have moved, mail routing and DNS are stable, applications use the target services, backup and restore procedures work, retention requirements are met and documentation is complete. Obtain formal approval from the technical owner, security or compliance reviewer and business sponsor.

Decommissioning is also a security activity. Remove obsolete accounts, service connections, firewall rules, certificates, privileged access and monitoring dependencies. Record what was removed and what remains, so future incidents are not investigated against an undocumented environment.

How does governance keep the migration on track?


Microsoft 365 migration has business consequences, so governance must connect technical delivery with user readiness, risk ownership, communications and decisions. Assign a migration owner, technical workstream leads, security and compliance reviewers, business representatives, a communications lead and a service desk lead.

A Cloud Strategy & Security perspective is useful when the migration must align cloud adoption, identity, tenant security, compliance and infrastructure modernisation. The goal is not to add a separate review at the end, but to make design decisions traceable throughout delivery.

Maintain a risk register with the issue, owner, probability, business impact, mitigation, decision date and status. Review it at each wave checkpoint. This makes it easier to distinguish a technical defect that can be fixed during the next batch from a control gap that should stop the release.

The strongest migration plans treat Microsoft 365 as part of a wider cloud adoption and infrastructure modernisation programme. They combine a clear target design with pilot evidence, controlled waves, user support, monitoring and a deliberate retirement plan.