A Monday morning is a poor time to discover that a trustee cannot find an old message, the fundraising inbox is not receiving enquiries, or a member of staff has been locked out of their account. This email migration case study follows a typical scenario for a busy West Yorkshire charity moving to Microsoft 365, with names and identifying details changed. The result was not flashy technology. It was a safer, more reliable email system that people could use without their work grinding to a halt.

The charity had a small office team, several part-time colleagues and volunteers who accessed email from home. Like many community organisations, it had grown around a mixture of old email accounts, ageing PCs and informal workarounds. Their email was hosted on a legacy platform with limited security controls, unreliable syncing and no clear process for leavers’ accounts.

They did not need a lecture about servers. They needed a sensible plan, patient support and confidence that their messages would still be there on Tuesday.

The problem was bigger than changing email addresses

At first glance, the request sounded straightforward: move existing email to Microsoft 365 and make it work on everyone’s devices. A closer look showed why migrations need care.

Several staff members had years of folders stored locally in Outlook. Shared inboxes were being used for referrals, donations and general enquiries, but no one could say with certainty who had access. A former employee’s account was still forwarding messages. Multi-factor authentication had not been switched on, and some passwords had been reused for a long time.

There was also a practical worry. The charity could not simply stop using email for a day. Service users, funders, partner organisations and volunteers all relied on it. A missed referral or a delayed safeguarding query was not just inconvenient.

This is where the trade-off becomes clear. A fast migration might look attractive on paper, but rushing can leave old data behind, confuse users or interrupt mail flow. Taking too long creates its own problems, particularly when the existing provider is unreliable or nearing the end of its contract. The right approach was to plan thoroughly, then make the change in a controlled window.

Email migration case study: planning before the switch

Before moving a single mailbox, the IT team built a clear picture of what existed. This involved checking every active account, shared mailbox, distribution list and device that used the charity’s email. It also meant speaking to people, not just reading an admin dashboard.

One member of staff explained that they kept important correspondence in personal folders because the old system’s search function was so unreliable. Another highlighted a shared address used by volunteers during evenings and weekends. Those details are easy to miss if a migration is treated as a purely technical exercise.

The agreed plan covered three areas: data, security and people.

For data, the team identified which mailboxes and archives had to move, how far back email should be retained and which inactive accounts needed to be preserved for records rather than deleted. Not every organisation needs to migrate every old newsletter and duplicate attachment. However, decisions about retention should be deliberate and based on operational, legal and funding requirements.

For security, the new Microsoft 365 accounts were set up with individual user access, multi-factor authentication and clearer controls around shared mailboxes. Former staff access was removed. Mail forwarding rules were reviewed so that no confidential information continued travelling to an account outside the organisation.

For people, the project included plain-English communications. Staff were told what would change, when it would happen and what they would need to do. They were not sent a ten-page technical manual and left to get on with it. Most people only needed to know how to sign in, approve multi-factor authentication, find their email and ask for help.

Choosing the right migration window

The actual switch was scheduled for a quieter period, after the team had confirmed that backups and mailbox copies were in place. There is no perfect time for every organisation. A retail business may prefer an overnight change. A charity with weekend services may need a different window. The key is to understand when a short interruption will cause the least disruption and make support available when people return.

The team also agreed a fallback plan. If a critical issue appeared, they knew who would make decisions, how users would be updated and which checks had to be completed before the old service could be retired. That planning reduced panic because no one was guessing under pressure.

What happened on migration day

The mailboxes were moved in stages, with priority given to the core office team and shared addresses. Email routing was changed only after pre-migration checks had been completed. Incoming and outgoing messages were then tested from external accounts, rather than assuming a green tick in an admin portal meant everything was working.

A small number of issues did appear, as they often do. One laptop had an older Outlook profile that needed reconnecting. A volunteer had changed their mobile number and could not receive the multi-factor authentication code. A shared calendar was visible but had the wrong permissions for one team member.

None of these problems were major, but they mattered to the people affected. The difference was that support was ready, knew the organisation’s setup and could resolve issues calmly. Rather than being passed between a software provider and a generic helpdesk, users had a clear point of contact.

By the next working day, staff could access their existing mail, send and receive messages, use shared inboxes and work from their usual devices. The office manager had a simple list of any outstanding checks and knew exactly who to contact if something surfaced later.

The value showed up after the move

The immediate outcome was a working email system. The longer-term benefit was better control.

New starters could be given an account properly, with the right access from day one. When someone left, their account could be secured and managed rather than left forwarding indefinitely. Shared addresses for enquiries and fundraising had named owners. Staff had stronger sign-in protection, and the organisation had a clearer view of where its information lived.

There was a cost to the new setup, of course. Microsoft 365 licences and ongoing support are not free. But the charity could weigh that predictable monthly cost against repeated outages, lost time, security risk and the pressure placed on staff who were already doing several jobs at once. For many small organisations, that is a more useful calculation than comparing licence prices alone.

The project also showed that cloud email is not a set-and-forget purchase. Accounts need reviewing, devices need updating and people need support when they change phones, forget passwords or take on new responsibilities. Good IT management keeps the improvement in place after migration day has passed.

What other organisations can take from this case study

If your organisation is considering an email move, start by asking a few grounded questions. Which addresses are business-critical? Where are old emails currently stored? Who needs access to shared mailboxes? What happens to an account when a colleague leaves? And who will help staff when they first sign in to the new system?

Do not assume the answer is always a full migration of everything. A small business with a handful of current mailboxes has different needs from a charity with years of sensitive correspondence and rotating volunteers. Equally, a move to Microsoft 365 may be right for many teams, but the licence level, storage needs and security settings should fit the way you actually work.

The strongest migrations are not judged by whether the technical cutover happened on time. They are judged by whether people can carry on serving customers, supporting beneficiaries and doing their jobs with less worry.

If email is becoming unreliable, difficult to manage or a source of security concern, a calm conversation is a good place to start. Bees Knees IT helps organisations across Bradford, Leeds and Halifax make practical decisions without the jargon. Give us a buzz and we will help take the sting out of IT.