Microsoft 365 migration, cut over in one weekend.

Historical mail and files are copied while everyone keeps working on the old system. Mail flow switches over in the cutover window, which is why we plan it for a weekend; the final delta pass then moves the last changes. On the first working day users sign in to the new account and reconfigure Outlook, OneDrive and their phones with our guide; we support them remotely through those first days.

Mailboxes with archives, calendars and contacts; OneDrive files; SharePoint sites and libraries; and Teams teams and channels when scoped (Teams chat history and public folders only when scoped and licensed). From Google Workspace we move Gmail, Calendar, Contacts and Drive. From IMAP mail we move mail folders only, because IMAP does not carry calendars or contacts. File servers move with their folder structure and dates; permissions are redesigned for SharePoint rather than copied one-to-one.

Yes, over IMAP. Mail folders move; address books, calendars and rules do not travel over IMAP, so they are exported and imported separately or set up again. Before we start, IMAP must be enabled on the source (Alibaba Mail blocks third-party clients on new accounts by default), and we need a password, client password or authorisation code for each mailbox. Mailboxes are created in Microsoft 365 first, then copied in batches, and the MX record is switched at the cutover.

In two parts. If a paid tool is needed, it is licensed per migrated user at the vendor's price (see migration tool pricing). Brocent's work is fixed price per project, quoted after scoping: we estimate the seven phases from your inventory and quote one fixed price for the project before work starts. Users, data volume, SharePoint sites, the number of domains, the coexistence period and the cutover window drive the price. Prices are reviewed every quarter; the current ones are valid until 2026-12-31.

Often not. For IMAP mailboxes (Tencent Exmail, Alibaba Mail, NetEase, Zoho, hosting-provider mail and personal Gmail), Google Workspace, on-premises Exchange, file servers and Dropbox, Box, Google Drive or Egnyte, we use Microsoft's own migration tools, so there is no tool licence to buy — as long as every mailbox fits the target plan's mailbox quota (100 GB on Business plans, E3 and E5; 50 GB on standalone Exchange Online Plan 1) and IMAP sources stay within Microsoft's limits of 500,000 items per mailbox and 35 MB per message. A paid licence is needed for tenant-to-tenant moves (Microsoft's Cross-tenant User Data Migration add-on or a third-party tool such as BitTitan), for Slack direct messages, and when a source goes beyond those limits. We confirm which case applies in discovery; tool prices are on our migration tool pricing page.

About 45 users in one region usually takes 5–10 days; most projects take 2–6 weeks from signed scope to handover. The cutover itself happens over one weekend; very large organisations move in waves, each with its own window. Data volume, the number of SharePoint sites and the time your own approvals take move the date most.

Remotely by default, which gives users in every office the same support during cutover. If you want an engineer at a desk on the first working day, on-site visits can be added at our published dispatch rates.

First we confirm it really is a different tenant: if the new domain can simply be added to your current tenant, that is a much smaller job without migration licences. If it is a move, their sign-in name and email domain move to the group tenant, so Outlook, OneDrive, Teams and phone apps are set up again after cutover. Mail, files and Teams content move with them. Because a domain can only exist in one tenant at a time, the domain is moved in one controlled window at the weekend, after a pilot has proved the method.

Yes, as a migration between two tenants. In mainland China, Microsoft 365 is operated by 21Vianet as a separate service, so a tenant cannot simply be switched over; users and data are migrated and licences are bought for each service. Transfer speed across the border is tested in the pilot. If personal data leaves mainland China, PIPL cross-border rules may apply — your legal team makes that assessment, and we document what data moves where.

It includes what the move needs: verified domains, SPF, DKIM and DMARC records, and protected admin accounts in the target tenant. A full review of security settings is a separate, fixed-price product: the Microsoft 365 security audit checks the new tenant against the CIS Microsoft 365 Benchmark after hypercare.