Microsoft 365 migration consulting

Move business content and email to Microsoft 365 with a clear plan for what goes where, who can access it and how you will verify the move. AURUM helps you assess the source, test a representative migration and support people through cutover.

Microsoft Solutions Partner for Modern Work · Based in Nuremberg since 2014 · About AURUM

What to decide before copying data

  • What to migrate, archive or leave behind
  • Where team files, personal files and mailboxes will live
  • Which tests must pass before switching users to the new setup

Microsoft 365 migration services

We can start with a migration assessment, a representative pilot or an agreed workload. The plan should reflect the data and the work that depends on it.

Source inventory and target design

Identify sites, files, mailboxes, permissions and dependent workflows. Agree which content to keep and what structure it needs in the target.

File shares to SharePoint and OneDrive

Separate team documents from individual work files. Review paths, permissions and how employees will find migrated content.

SharePoint content and applications

Assess libraries, sites, customisations and legacy workflows. Decide what can be migrated and what needs redesign.

Mail and calendars

Plan user and shared mailboxes, delegates, domains and application mail. For a mailbox-focused project, see Exchange Online consulting.

Tenant and integration dependencies

Check ownership, identities, shared links, apps and external access. Confirm which workloads are supported by the chosen method and which need separate work.

Cutover, validation and adoption

Define migration waves and go-live criteria. Validate data and access, communicate what is changing and agree how to handle post-launch questions.

Which migration route fits your workload?

Start with data ownership, permissions and the people who rely on the source. Each workload may need a different migration method.

File shares to Microsoft 365

Common targets are SharePoint libraries for team content and OneDrive for personal work. Check current folder depth, paths, sharing and content ownership.

Email to Exchange Online

Test mail, calendars and shared access. Confirm domains, mail routing and application senders before changing the production route.

Tenant move or legacy platform

Review each workload individually. Some permissions, sharing links, applications and workflows may need recreating or redesigning.

See Microsoft’s migration overview and its file-share migration guide. For wider rollout and licensing decisions, see Microsoft 365 consulting.

What we validate before switching users over

A migration pilot should include tricky content and permissions as well as a typical mailbox or file share.

Data and access are accounted for

Compare what arrived with the agreed scope. Test representative permissions, shared access and whether users can find priority content.

Dependent workflows still work

Identify links, integrations and applications that may need changes. Record fixes and who will verify them after cutover.

From source assessment to staged migration

Plan acceptance criteria and fallback decisions before moving production workloads.

Discuss your requirements
  1. Inventory and prioritise

    Record sources, owners, data volumes, access and deadlines.

  2. Design the destination

    Map data to target locations and agree what needs to change before migration.

  3. Pilot a representative move

    Test content, access, mail or workflows. Fix issues and agree cutover timing.

  4. Migrate, validate and hand over

    Move in agreed stages, check the results with users and document remaining follow-up.

Microsoft 365 migration FAQ

Answers about scope, permissions, downtime and costs.

Can you migrate a file server to Microsoft 365?

Yes. We can assess the data and map team and individual files to appropriate SharePoint or OneDrive locations. Some applications and file types may need another approach.

Can we migrate in stages?

Yes where the source and target support it. We group workloads by dependencies and user needs, then plan each move and validation.

Do existing permissions transfer exactly?

That depends on the source and tool. Some permission models do not map directly, so we check the target rules and validate access in a pilot.

Will there be downtime?

That depends on the workload and migration method. We identify when users may be affected, test critical tasks and agree a cutover window.

What affects the cost of migration?

Data volume, source systems, permissions, integrations, cleanup, testing and support all affect effort. We review tools and licences separately.

Can we start with a migration assessment?

Yes. An assessment can give your team a phased plan, key risks and pilot scope before you commit to implementation.

Discuss your project in English

Tell us what needs to move, who relies on it and whether there is a deadline. In a free initial consultation, we’ll help decide what to assess first.

Mustafa Yaylak
Managing Director, AURUM GmbH

+49 911 25361972