A charity Microsoft 365 migration example is often less about moving emails and more about protecting the organisation’s ability to support people. When staff, trustees and volunteers rely on ageing systems, shared inboxes and files stored in several places, a poorly planned move can cause real disruption. Done properly, however, Microsoft 365 can make everyday work simpler, safer and easier to manage.

The following is a representative example based on the challenges commonly seen in smaller charities. It shows what a migration needs to consider beyond the technical work, particularly where there is limited internal IT capacity and a mix of employed staff, part-time workers and volunteers.

The starting point: a charity held back by its systems

Imagine a Sussex charity with 22 staff members, 14 regular volunteers and a board of trustees. It provides practical support to vulnerable local residents, so it handles personal information, referral records, funding applications and confidential case notes.

Its technology had grown gradually. Email was hosted with a basic provider, documents sat across a local server, individual laptops and several personal cloud-storage accounts, and the team used a mix of WhatsApp groups and personal email addresses to coordinate urgent work. There was no consistent process for removing access when volunteers left, and backups were unreliable.

Nothing had failed dramatically, but the warning signs were clear. Staff were spending time hunting for the latest version of documents. Home working was awkward. A lost laptop could have become a data protection issue. And the charity manager had no simple answer to a trustee asking who could access sensitive files.

The aim was not to introduce technology for its own sake. The aim was to give people dependable tools, reduce avoidable risk and allow the charity to focus on its services.

What the charity needed from Microsoft 365

Microsoft 365 offered a sensible route forward because it could bring email, document storage, meetings and user security under one managed platform. Charities may also be eligible for discounted or donated licences, depending on their status and the programmes available at the time. That can make a significant difference to a limited budget, although eligibility and licence terms should always be checked before plans are made.

For this organisation, the project had five practical outcomes:

• move email addresses and historic mailboxes without losing messages;
• create a safe, shared home for documents and team folders;
• give staff secure access from office and home;
• set clear access rules for volunteers, trustees and leavers; and
• put backups, multi-factor authentication and device security in place.

The charity did not need every Microsoft 365 application. This matters. Paying for more features than people will use creates confusion as well as unnecessary cost. The migration plan focused first on Exchange Online for email, SharePoint and OneDrive for files, Teams for meetings and messaging, and core security controls.

Planning the migration before moving anything

The most valuable part of a migration usually happens before the first mailbox is moved. A good discovery phase identifies what exists, who owns it and what should not be carried into the new environment.

In this case, the team mapped every email account, shared mailbox, mailing list, laptop and document location. They also identified volunteer accounts that were no longer needed, old shared folders with unclear ownership and files containing sensitive information that required tighter controls.

This stage uncovered a common issue: the charity had several versions of the same grant application template, stored in different locations. Moving all of them would simply recreate the old problem in a newer system. Instead, the charity agreed which files were current, archived what had to be retained and removed material that no longer had a business purpose.

Data retention needs careful judgement. Charities cannot simply delete information because it is inconvenient, particularly where records are needed for safeguarding, finance, contractual or legal reasons. Equally, keeping everything forever raises risks. The charity’s leadership should agree retention decisions with appropriate governance and, where necessary, specialist advice.

Building a secure structure that people can use

The technical setup was designed around the way people actually worked. Every member of staff received an individual account rather than sharing logins. This created clearer accountability and made it possible to remove access promptly when someone left.

SharePoint sites were created for core functions such as fundraising, finance, operations and service delivery. Permissions were based on roles, not personal favours. Finance documents were restricted to the right people, while general policies and volunteer resources were available more widely.

OneDrive was positioned as each person’s working area, while SharePoint became the home for documents that belong to the organisation. That distinction is simple but important. If an employee leaves, vital files should not be stranded in a personal folder that nobody else can find.

Multi-factor authentication was enabled for all users. This adds a second check when signing in and is one of the most effective protections against stolen passwords. It can feel like an extra step at first, especially for occasional volunteers, so the rollout included clear instructions and support rather than assuming everyone would be comfortable with it immediately.

The charity also introduced managed device settings for staff laptops. Screen locks, security updates and encryption helped reduce the consequences of a device being misplaced. For volunteers using personal devices, the approach was more cautious: access was limited to the information they genuinely needed, rather than attempting to manage equipment the charity did not own.

Moving email and files in manageable stages

The email migration was scheduled for a quieter period, with the final switch taking place outside normal working hours. Beforehand, staff were told exactly what would happen, what they needed to do and where to get help the next morning.

Mailboxes were copied in advance, then a final synchronisation captured the latest messages before the email domain was switched to Microsoft 365. Old mail remained accessible, and shared addresses such as enquiries and fundraising were rebuilt as shared mailboxes with named access permissions.

Files were not moved in one uncontrolled bulk transfer. The charity began with its most active shared folders, checked the structure with the relevant teams and then moved the remaining approved material. This gave staff time to get used to SharePoint and OneDrive while avoiding a sudden, confusing change to every file they had ever created.

There was a trade-off. A phased move takes slightly longer than copying everything overnight. But for a charity with busy staff and limited time for retraining, the lower disruption was worth it. The best approach depends on the size of the organisation, the quality of existing data and how critical each system is to daily services.

Supporting people after go-live

A migration is not complete when the new email platform starts working. The real test is whether people can confidently do their jobs on Monday morning.

The charity received short, role-based guidance rather than a long technical manual. Staff learned how to find shared documents, share files safely, use Teams meetings and spot suspicious sign-in prompts. Trustees were shown the simplest secure route to board papers. Volunteers received only the guidance relevant to their access.

For the first few weeks, questions were expected and treated as part of the project, not as user error. Some people needed help setting up authentication on a new mobile phone. Others needed a reminder that sending a file link was safer than attaching multiple versions by email. Small, timely support prevented these frustrations becoming reasons to return to old habits.

The result: more control without making work harder

After the migration, the charity had one secure system for email and shared files, clearer ownership of information and a straightforward process for joining and removing users. Staff could work from home or the office without relying on personal accounts, and managers had better visibility over access to sensitive data.

The biggest change was operational rather than technical. People spent less time asking where a document was or whether they had the latest version. The charity was also in a stronger position to respond to a cyber security incident, an audit question or a staff departure because access and information were no longer spread across unmanaged services.

For organisations considering a similar move, the lesson is simple: start with the work your people need to do, then build the Microsoft 365 environment around it. My Tech Team can help charities in Sussex assess their current setup, plan a practical migration and provide ongoing support once the new system is in place.

A well-run migration should leave your team with less technology to worry about, not more. When access is clear, information is protected and support is available, your people can keep their attention where it belongs – on the community they serve.