How your migration works — step by step

You tell us about your project — fastest via the price calculator, which sends your configuration along. In a short call we clarify source, target, scope and your preferred date.

We set up technical access to source and target (e.g. an app registration in Microsoft 365, a service account in Google Workspace; we guide you or do it together with you). Our software then automatically records the inventory: mailboxes and folders, calendars, contacts, drives, groups and shares. Credentials are stored exclusively encrypted in our key vault and never in plain text in databases or logs.

Based on the discovery figures you receive a fixed-price quote with a clear scope and schedule. Before the main migration we run a test migration with individual real mailboxes, so you see the result in your own system before you commit.

Most of the data is transferred in the background: emails with folder structure and read status, calendars, contacts, files. Your team keeps working as usual: we only read from the source and change nothing there. Several mailboxes run in parallel; standard folders such as Inbox or Sent end up in the real system folders at the target, not in copy folders.

On the agreed date — happily at the weekend or in the evening — we switch over (e.g. mail delivery to the new platform). A delta sync transfers everything that has arrived since the pre-migration. The actual switch is therefore short, and nothing that arrived in the meantime is lost.

After the migration our software compares source and target: per mailbox and per folder, not as a sample. Every discrepancy is named, re-migrated or documented with a reason (e.g. objects rejected by the target system). You receive a final report that proves completeness.