Microsoft Office 365 Migration

Fresh Mango Microsoft Office 365 migration projects for businesses. It requires careful planning and management and is not an...

Colleagues collaborating on a laptop and tablet during a video call.

Office 365 Migration · Methodology

An Office 365 migration is the structured move of email, files, and identities from an existing system — an on-premises server, a different hosted provider, or another Microsoft 365 tenant — into a properly configured Microsoft 365 environment.

Fresh Mango Technologies has run Microsoft 365 migrations for British Virgin Islands businesses since Office 365 launched, and treats migration as a planned project rather than a simple data copy.

The methodology below is the same sequence used whether the source is a Microsoft Exchange server, a different hosted mailbox provider, or an existing Microsoft 365 tenant being consolidated after an acquisition.

Discovery and planning

Every migration starts with an inventory: mailbox sizes, file server volumes, custom mail rules, distribution lists, line-of-business application dependencies on email or file shares, and any regulatory retention requirements. This inventory determines the migration approach and realistic timeline rather than an assumed one, and surfaces dependencies — a booking system that emails through the old server, for example — before they cause a failure on cutover day.

Tenant setup

A new Microsoft 365 tenant is configured with domains, security baselines, Microsoft Entra ID conditional access, multi-factor authentication and licensing before any data moves. Getting this configuration right before migration avoids retrofitting security controls onto live mailboxes afterwards, which is disruptive and easy to get wrong.

Mail and file migration approaches

Mailbox migration typically runs mailbox-by-mailbox or in batches, replicating messages, calendars and contacts into Microsoft Exchange Online ahead of cutover, then completing a final short delta sync just before switching mail flow.
File migration maps existing folder structures into SharePoint sites and libraries with a metadata scheme, rather than a like-for-like folder copy, as covered in Fresh Mango's SharePoint migration approach.
A coexistence period runs the old and new systems side by side briefly for mail flow and file access, giving a safety net before the old system is switched off.
DNS records — MX, autodiscover, SPF, DKIM and DMARC — are updated at cutover to route mail flow to Microsoft 365 and are verified rather than assumed correct.

Cutover and adoption

Cutover is scheduled outside business hours where possible, with a rollback plan agreed in advance in case an unexpected issue appears. After cutover, staff are supported through the first days of using Microsoft Teams, SharePoint and Outlook in their new configuration, since technical migration success and user adoption are separate outcomes that both need managing.

Common failure points

DNS changes propagating slower than expected, causing intermittent mail delivery immediately after cutover.
Line-of-business applications that send email through the old mail server and are not reconfigured before cutover.
Underestimating file migration time for large SharePoint uploads over limited island internet bandwidth.
Skipping staff training, leaving users confused by SharePoint's structure or Outlook's new interface.
Migrating security misconfiguration from the old environment instead of resetting baselines in the new tenant.

Migration approaches by starting point

Consideration	Migrating from an on-premises server	Migrating from another Microsoft 365 tenant
Typical driver	Server end of life, hardware failure risk, hurricane resilience	Business acquisition, divestment, or provider change
Mail migration method	Hybrid or cutover migration from Microsoft Exchange	Tenant-to-tenant mailbox migration
File migration	Map file server folders into SharePoint sites	Move SharePoint/OneDrive content between tenants
Identity	New Microsoft Entra ID accounts created	Accounts re-provisioned or merged into target tenant
Typical complexity	Moderate — depends on server age and customisation	Higher — depends on scale and overlapping domains

When should a business use this?

Retiring an ageing on-premises Microsoft Exchange server

Move mail into Microsoft Exchange Online before ageing hardware or an unsupported version becomes a security and continuity risk.

Consolidating tenants after an acquisition

Merge two Microsoft 365 tenants into one so staff share a single directory, mail domain and set of Teams and SharePoint sites.

Switching from a different hosted email provider

Move mailboxes and calendars into Microsoft 365 to gain SharePoint, Teams and Microsoft Copilot in one licence.

Rebuilding after inherited misconfiguration

Use a migration to reset security baselines and Microsoft Entra ID conditional access rather than carrying forward existing weaknesses.

Best practices we recommend

Complete a full discovery inventory before committing to a cutover date.
Configure security baselines and conditional access in the new tenant before migrating any data.
Reduce DNS record time-to-live values in advance so cutover changes propagate quickly.
Run a coexistence period rather than a single hard cutover for anything beyond a very small mailbox count.
Identify every application that sends mail through the old system before switching mail flow.
Budget time for staff adoption support in the days immediately after cutover, not just the technical migration.

Frequently asked questions

How long does an Office 365 migration take?

It depends on mailbox count, data volume and internet bandwidth, but most British Virgin Islands small and mid-sized businesses complete migration within two to six weeks from discovery to cutover. Large file volumes migrated over limited bandwidth, or complex line-of-business application dependencies, extend that timeline and should be identified during discovery.

Will staff lose access to email during migration?

A well-planned migration keeps disruption to a short cutover window, often scheduled outside business hours, with a coexistence period beforehand so mail keeps flowing on the existing system until the new one is verified. Fresh Mango agrees a rollback plan in advance in case an unexpected issue appears at cutover.

Can we migrate from an old Microsoft Exchange server directly into Microsoft 365?

Yes. A hybrid or cutover migration moves mailboxes, calendars and contacts from an on-premises Microsoft Exchange server into Microsoft Exchange Online, followed by a DNS cutover to route new mail flow to Microsoft 365. The right approach depends on mailbox count and how long coexistence is needed.

What happens to our files during a migration to Microsoft 365?

Files are mapped from the existing file server or storage system into SharePoint sites and libraries with a metadata scheme, rather than copied across as an identical folder tree. This is planned and executed alongside the mail migration so staff gain SharePoint and OneDrive access at the same time as their new mailbox.

Do we need to reconfigure security after migrating to Microsoft 365?

Security should be configured before migration, not after. Fresh Mango sets up Microsoft Entra ID conditional access, multi-factor authentication and Exchange Online protection in the new tenant as part of tenant setup, so mailboxes and files arrive into an already-secured environment rather than one retrofitted later.

Related services and guides

Practical advice, no obligation

Plan a migration that does not disrupt your business

Fresh Mango Technologies has migrated British Virgin Islands businesses onto Microsoft 365 since it launched, with a discovery-led methodology and a rollback plan for every cutover.

Book Your Free 30-Minute Consultation

Fresh Mango Technologies has extensive experience in Microsoft Office 365 migration projects. Microsoft Office 365 is a cloud-based email. Previously email was configured using Microsoft Exchange Based on a server. This created many problems not least of which was if your server went down or was offline for any reason your email went with it. That’s one of many reasons that businesses are moving their email through Microsoft Office 365 migration. Whilst setting up a Microsoft 365 account is straightforward, you and your staff will likely need to have access to all your previous emails. Moving these emails across to your new Microsoft Office 365 account is called migration, and we will be pleased to assist you with your Microsoft Office 365 migration. We have conducted numerous Microsoft Office 365 migrations for companies. It requires careful planning and management and is not an ‘overnight’ task. Contact Fresh Mango today to find out more and to arrange your Office 365 migration.

About Microsoft 365

Microsoft 365 provides more than just email service – if you want it. You can add on Microsoft Office software to your subscription list – Word, Excel, PowerPoint and so forth. The beauty of this is you never have to pay for another licence for your office software nor pay extra to upgrade your office software. You will always have the latest version of Microsoft Office. With the advent of enforced working from home and social distancing rules, the video software and collaborative working elements of Microsoft 365 have come into their own space. Microsoft Teams is now the predominant business-based means of communicating with video conferencing for geographically dispersed teams. Microsoft 365 is equipped with its own cloud file storage system called OneDrive. Like any old cloud file storage systems, it is very convenient but does require careful management, especially when files and folders are shared across multiple members of staff. OneDrive and other cloud file storage systems such as Dropbox and Google docs are not a substitute for managed folders, files and software deployment that businesses would typically deploy with a server.

Explore more in Microsoft 365

Microsoft 365 licensing, migration, Teams, SharePoint and security hardening.

View the Microsoft 365 hub