From your old email environment or Google Workspace to Microsoft 365: in steps and under control, with a check afterwards that everything came across. With a migration report as proof.
Workplace One-off project work per mailbox or per user, alongside the monthly management
What you buy- Inventory in advance
- Pilot group first
- Background synchronisation
- Updates until the switch
- Scheduled cutover
- MX, SPF, DKIM and DMARC checked
- Instructions for employees
- Extra support after the switch
- Fallback scenario for every step
- Migration report
Who it is for, what you get and how you pay
- Who it is for
- Organisations that want to move their email and files to Microsoft 365.
- The problem
- A switchover affects everyone at once, so it has to go right the first time.
- What you get
- A migration in steps: first a pilot group, then everything in the background, and a short switchover.
- What you do yourself
- You give access to your current environment and agree the switchover moment with us.
How you pay
- One-off Project work per mailbox or per user, plus the standard onboarding.
Comes on top
- Licences Microsoft licences, always separate.
The amount is in your quote, excluding VAT.
The next step
You get one quote with scope, quantities, planning and price.
Pilot, sync, delta, cutover
First a small pilot group. Then we sync the rest in the background, and delta syncs keep everything up to date until the switchover moment. After the cutover comes the migration report.
Migrating is a controlled process, not a leap
An email migration affects everyone in your business. That is why we work to a fixed, proven sequence, with a check and a fallback option at every step.
Inventory in advance
We first fully map out mailbox sizes, aliases, shared mailboxes, permissions and dependencies. No surprises halfway through.
Pilot before the bulk
A small pilot group moves over first. Only when that runs flawlessly does the rest follow, in scheduled batches.
Copy, update, switch over
We copy large amounts of mail and files in advance in the background; after that we only update the differences until the moment of the switch. That keeps the switch itself short.
Mail flow switched over under control
MX, Autodiscover, SPF, DKIM and DMARC: checked before the switch and again afterwards. Making sure your mail keeps arriving is not a side issue but a checklist.
Clear communication
Employees get clear instructions in advance: what changes, when, and what they need to do themselves. For the first few days after the switch we are on standby for questions.
Proof and acceptance
The status is visible per batch and per user. Completion is based on acceptance and a migration report, not on "it'll probably be fine".
Migration and project work
One-off project work, alongside the monthly management fee for Microsoft 365 management.
Standard onboarding
Tenant and domain inventory, administrators and service ownership, licence and user plan, security baseline and connection to the SEBA platform.
one-off
Simple mailbox migration
Mailbox only, priced per mailbox.
one-off
Mail, calendar and contacts
Full mailbox migration per user.
one-off
Mail, OneDrive and Teams
Mailbox, files and collaboration per user.
one-off
Complex tenant migration
Tenant-to-tenant or merger, always by quote.
one-off
New Intune setup
Setting up device management: profiles, compliance and rollout.
one-off
Conditional Access baseline
Designing, testing and rolling out access policies.
one-off
The standard onboarding consists of a fixed part plus a part per user; the migration project comes on top of that as a one-off. Your quote shows both as separate lines, with the number of users and mailboxes we are basing it on.
If the inventory or a batch shows that more is needed than agreed, you hear about it first. The source environment stays intact until you accept the migration.
Frequently asked questions about a Microsoft 365 migration
What does a migration to Microsoft 365 cost?
A migration is one-off project work and is priced per mailbox or per user, depending on what needs to move: just the mailbox, or also calendar, contacts, OneDrive and Teams. A tenant-to-tenant migration is always by quote. On top of that comes the standard onboarding, which is one-off and partly counted per user. Microsoft licences are always added separately. The amount is in your quote, together with the number of mailboxes and users.
Can we keep working during the migration?
Yes. We migrate in phases: first a pilot with a small group, then the initial synchronisation in the background, after which we only update the differences (delta syncs) until the scheduled moment of the switch, the cutover (usually outside office hours). Email keeps coming in; employees mainly notice the moment of the switch itself.
Which systems can you migrate from?
From virtually any source: old IMAP/POP email environments at hosting providers, Google Workspace, on-premises Exchange and existing Microsoft 365 tenants (tenant-to-tenant, for example after an acquisition).
What happens to email during the switch (MX, SPF, DKIM)?
We plan the mail cutover carefully: MX records, Autodiscover, SPF, DKIM and DMARC are switched over in a controlled way and validated before and after the switch. That way mail keeps arriving and your domain stays protected against spoofing.
What if something goes wrong during the migration?
The source environment stays intact until the migration has been accepted; there is a fallback scenario for every step. Failed items are flagged, classified and processed again. Afterwards you receive a migration report showing what was transferred and checked.
Read more about a Microsoft 365 migration
The articles themselves are in Dutch.
Planning to move to Microsoft 365?
Tell us what you need. You get one quote with scope, quantities, planning and price, and up front what we need from you.
You’ll hear back within one working day