E-mail and files

Migration to Microsoft 365: Exchange, Zimbra and file servers

We move e-mail from Exchange Server, Zimbra, Google Workspace or IMAP to Exchange Online, and files from servers or NAS to SharePoint, OneDrive and Teams. We keep folder structure and permissions, and explain to your people what changes.

From
Exchange, Zimbra, Google, IMAP, file server, NAS
To
Exchange Online, SharePoint, OneDrive, Teams
We keep
Mail, calendars, contacts, permissions
Tenant-to-tenant
Yes, for mergers

What we migrate

SourceTargetNotes
Exchange Server 2010–2019Exchange OnlineHybrid or cut-over migration
ZimbraExchange OnlineMail, calendars, contacts
Google Workspace / IMAPExchange OnlineMail and calendars
File server / NASSharePoint, OneDrive, TeamsStructure and permissions redesigned
Another Microsoft 365 tenantYour Microsoft 365Tenant-to-tenant for mergers

How we work

  1. Inventory

    Mailboxes, archives, public folders, file structure and permissions, devices that send mail.

  2. Preparation

    Microsoft 365 tenant, licences, domain verification, MFA and SharePoint structure.

  3. Pilot

    We move a small group first, while mail and files sync in advance.

  4. Cut-over and support

    MX records, Outlook and phone setup, user support in the first days.

What you get

A migration plan

Timeline, cut-over window and a rollback scenario.

Mail and files moved

With calendars, contacts, folder structure and permissions.

A secure Microsoft 365

MFA, SPF, DKIM, DMARC and sharing rules from day one.

Guides for your people

What to do on cut-over day and how to connect on the phone.

Indicative timeline

PhaseDuration
Inventory and plan3–5 business days
Preparation and pilot1–2 weeks
SynchronisationA few days to a few weeks, depending on data volume
Cut-over and supportA weekend + a week of support

Durations are indicative – you get an exact plan and dates in the proposal, after we have assessed your environment.

What we need from you

To keep things moving, please have ready:

  • access to your domain’s DNS;
  • admin access to the current mail and file server;
  • Microsoft 365 licences (or we help you choose the right ones);
  • a list of mailboxes, public folders and key file shares;
  • a contact person to inform staff and agree the cut-over time.

A typical project: Zimbra and a file server to Microsoft 365

Situation

The company ran an old Zimbra mail server and a file server in the office; remote work was awkward and the server was out of warranty.

What we do

We moved mail, calendars and contacts to Exchange Online and files to SharePoint and Teams with a redesigned permission structure, enabled MFA and set up SPF, DKIM and DMARC. The cut-over ran over a weekend.

Result

On Monday staff worked in the new environment, files are available from anywhere, and the old server was switched off after a short monitoring period.

A composite example based on our most common projects.

Frequently asked questions

Will we lose e-mail during the move?

No. Mail is synchronised in advance and the final switch (MX records) happens at an agreed time.

Do phones need to be set up again?

Usually yes – we prepare a simple guide and help your people.

Do you migrate from Zimbra?

Yes – mail, calendars and contacts from Zimbra to Microsoft 365.

Will file permissions be kept?

We redesign permissions with you – usually a good moment to tidy up who can access what. The SharePoint and Teams structure is ready before the move.

How do we prepare for an Exchange migration?

The essentials are an inventory, DNS access and informing staff. See the full list in our guide Exchange Server to Microsoft 365.

Get a migration assessment

Number of users
More details (optional) – for a more accurate proposal
Current e-mail systems · select all that apply
Where are your files? · select all that apply
User management · select all that apply
You’ll get a written proposal by the next business day.
  • Microsoft partner
  • Lenovo Gold Partner
  • Scoris Business Excellence Award 2026
  • 433+ companies served
  • Since 2005
CallGet a proposal

Choose which cookies you allow. You can change your choice at any time.

Strictly necessary

Needed for the site to work securely and remember your choices (e.g. cookie settings or text typed into a form). They cannot be switched off and need no consent.

Always on
Cookies (3)
  • ithink-consent · IThink (localStorage)
    Stores your cookie choice and an anonymous consent ID. Expires: 12 months.
  • ithink-form:* · IThink (sessionStorage)
    Keeps the text you type into a form so you don’t lose it while filling in a request. Expires: Until the browser tab is closed or the form is sent.
  • __cf_bm, cf_clearance · Cloudflare
    Protection against bots and attacks (set only when needed). Expires: 30 minutes.

Analytics

Help us understand how visitors use the site (Google Analytics 4) so we can improve it. Data is aggregated and IP addresses are not stored.

Cookies (3)
  • ithink-utm, ithink-landing · IThink (sessionStorage)
    Adds the campaign source and first page visited to your request. Expires: Until the browser tab is closed.
  • _ga · Google Analytics 4
    Distinguishes visitors for visit statistics. Expires: 2 years.
  • _ga_8EFLVCZYDP · Google Analytics 4
    Keeps the state of your visit (session). Expires: 2 years.

Marketing

Let us measure the effectiveness of our Google Ads advertising and show you more relevant ads.

Cookies (2)
  • _gcl_au · Google Ads
    Measures whether an ad led to a visit and a request. Expires: 90 days.
  • IDE, test_cookie · Google (doubleclick.net)
    Ad delivery and measurement on Google networks. Expires: Up to 13 months (test_cookie – 15 minutes).

Cookie policy · Privacy policy

Privacy policy

Loading…