Set the timing before anyone clicks over
Choose a go-live window that suits your team, your donors and your busiest internal hours. For many non-profits, that means early morning on a weekday, when staff in Cape Town, Johannesburg, Durban, Pretoria and Bloemfontein can all reach the same support contact point before meetings start. If your team works across offices or from home, make sure the move is timed around school runs, site visits and any board meetings already in the diary.
Before the switchover, confirm who is responsible for final checks, who gives the approval to proceed and who handles questions from staff. A small group is easier to manage than a long chain of replies. If you are planning around load-shedding or a weak internet day, have a backup power plan and mobile data ready so the right people can still log in and confirm each step.
- Pick a launch time when key staff are available
- Nominate one person to approve the move
- Share the support route with everyone in advance
- Check power and internet backup at the office
Check the essentials the day before
The day before go-live is for housekeeping, not last-minute guesswork. Make sure your domain settings are ready, each mailbox has the correct name, and shared calendars and document spaces are mapped to the right teams. If you are moving old messages, confirm which accounts need migration, which need contact imports and which users need mobile device setup.
Before launch, test passwords, access permissions and any admin roles. That way you do not discover missing rights when a manager tries to open a shared file or a finance officer needs calendar access for a payment deadline. Keep one person available to deal with any small issue, because a five minute delay can turn into a morning of confusion if no one is watching it closely.
- Confirm mailbox names and display details
- Check shared calendars and document folders
- Review mobile access for phones and tablets
- Make sure old and new login details are recorded safely
- Verify admin access for the right staff members
Keep your team informed without flooding them
Staff do not need a long technical note. They need clear instructions on what changes, when it changes and what to do if something looks different. A short message before launch should explain where to sign in, which account to use and who to contact through the enquiry form if they hit a snag. Keep the wording plain and avoid sending three different versions from three different managers.
On the morning of the move, send a reminder with the key steps and the time the change starts. If some users are field-based or often out with clients, let them know what to expect on mobile. A quick message can save hours of back-and-forth later, especially when people are juggling meetings, donor calls and the usual office interruptions.
- Send one clear pre-launch notice
- Include the switchover time and what users must do
- Tell staff how to report a problem
- Keep one communication owner for the day
Go-live morning: a simple working checklist
Once the switch starts, the job is to confirm that the core services are working in real use. Test sending and receiving messages, opening shared calendars, and uploading or editing a document in the shared space. Ask a few staff members from different departments to do the same, because finance, programmes and management often use the system in different ways.
If you are supporting a distributed team, ask one person in each region to reply with a quick status update. A short checklist keeps everyone focused and avoids the common problem of people assuming someone else has already checked it. If something is slow, note the exact time and the account involved so support can fix it faster.
- Send a test message to and from each active mailbox
- Open shared calendars and confirm appointments appear correctly
- Check document access from benchtop and mobile
- Make sure signatures and contact details display correctly
- Record any issue with time, user name and device used
Support the first day of live use
The first day after go-live is when small user questions usually appear. Someone may forget a password, another person may need help on a phone, and a team lead may want a folder moved or permissions adjusted. This is normal, and it is better to handle these early than wait until the following week. A calm response keeps the team focused on work, not on panic.
Staff should also be reminded that new habits take a day or two to settle. Shared calendars may feel unfamiliar at first and document collaboration can be new to people who are used to sending files around. Give short instructions, not long lectures. Keep the support line of communication simple and make sure one person can answer or escalate quickly. That is especially useful when office power cuts or poor signal interrupt the day.
What to do if something does not look right
Not every issue means the move has failed. A delayed message, a missing calendar item or a phone that has not refreshed may be fixed with a refresh, a re-sign-in or a device setting change. The best approach is to pause, check the account details and work through the problem step by step instead of changing several things at once.
If the issue affects several users, look at the common factor first. It may be a shared calendar permission, a group mailbox setting or a mobile sync problem. Keep the original settings notes nearby so you can compare what was planned with what is showing live. When you know exactly what changed, it is much easier to restore normal use without extra delay.
- Refresh or re-open the account first
- Check whether the issue is on one device or many
- Compare the live setting with the launch notes
- Escalate with screenshots or exact error text if needed
Hand over admin work once the team is settled
After the first few days, move from launch mode to steady administration. Confirm who manages new mailboxes, who approves calendar access and who updates document permissions when staff join or leave. For non-profits, this matters because teams change often and volunteer access can shift quickly. A clean handover prevents confusion later, especially when funding deadlines, events or board packs are due.
It is also worth setting a short review after launch to check what worked well and what should be improved. That review can cover training needs, security checks and any remaining admin help. Once the urgent items are done, the focus shifts to keeping communication clear and the system easy for your staff to use day after day.
