Exchange Online migration: prepare your users before cutover day

An Exchange Online migration for SMBs starts with a people inventory

The list of addresses doesn’t tell the whole story. You also need to identify shared mailboxes, aliases, room calendars, delegations and accounts used by a photocopier or billing software. Ask each manager what they actually open during a normal week. The forgotten uses are often the ones that become urgent after the move.

Use the inventory to confirm active employees and recent departures. An old account shouldn’t be migrated just because it still exists. Instead, decide whether its content should be kept, transferred to a manager or archived according to company rules. Also have an owner named for each generic mailbox, such as sales@ or billing@.

Finally, identify the people whose day depends heavily on email: reception, management, customer service, the mobile team. They don’t necessarily get different treatment, but they should be tested early and know who to contact if they’re missing an access.

Prepare accounts, passwords and MFA

The first sign-in to the new environment should be predictable. Confirm the sign-in address, the initial password, how to change it and the recovery contact information before the cutover. Avoid sending this sensitive information to the very mailbox being migrated. A familiar internal channel, or handing it over in person, reduces confusion.

Multi-factor authentication deserves a short demo. Show a real sequence: enter the password, recognize the legitimate prompt, then reject an unexpected notification. Also explain what to do when someone changes phones. The goal isn’t to give a security course, but to keep a vague instruction from turning every first sign-in into a support ticket.

Administrator accounts must stay separate from day-to-day work accounts. Also check that at least two authorized people can step in if the main administrator is away. This preparation helps as much during the migration as at the next employee departure.

Test the devices and habits around Outlook

A test on a recent computer doesn’t validate every device in the company. Choose a few representative profiles: a Windows laptop, a Mac, an iPhone or Android phone, a shared workstation and a remote user. Check Outlook, but also the calendar, contacts, shared mailboxes and sending from a service address.

Look at the small details that interrupt work. A signature may stay on the old profile. A local rule may not carry over. An employee may have added their mailbox to their phone using an old protocol. Note these gaps and prepare a short sheet per device type, with only the steps the user will actually need to take.

Applications that send email need their own test. A web form, a scanner or accounting software doesn’t use the same authentication method as Outlook. Confirm who is responsible for each application and avoid sharing a personal account to reconnect them.

Organize the cutover without drowning the team in DNS

Changing the DNS records and moving the data belong to the technical plan. What the team mainly needs to know is when the old access will stop being reliable, how long to avoid certain actions and how to tell that the new access works. Translate the plan into business instructions, without copying the administrator’s procedure.

Plan a window that respects operations. A business that handles urgent requests on Friday evenings doesn’t have the same leeway as an office that’s closed on weekends. Also define a rollback threshold: what problem would justify pausing the next step rather than piling up improvised fixes?

Before the cutover, check that the old provider isn’t the only one controlling the domain, the DNS or the backups. Access must be tested, not just written down in a document. The page on Microsoft 365 and email at Infotech Canada outlines the technical and security elements that come with this kind of transition.

Communicate briefly, but at the right time

A long email sent two weeks ahead will be forgotten. Go with three short messages instead: what’s changing and why, what to prepare the day before, then the steps for the first sign-in. Add the name of the support channel and the hours when someone will be available. Managers should get the same version to avoid conflicting instructions.

Run a test with a small group and ask them to note any words that aren’t clear. If “Outlook profile” or “authenticator app” raises questions, replace the jargon or add an approved internal screenshot. The test is as much about fixing the communications as confirming the configuration.

For an Exchange Online migration for SMBs to be truly finished, also plan the day after: check for missing devices, confirm shared mailboxes, watch for bounced messages and properly close the old access. Success isn’t measured only by the fact that the data moved, but by operations getting back to normal.

Validate the plan before setting the date

If you’re preparing an email migration, Infotech Canada can review accounts, devices, MFA, dependencies and user communications. The goal is to identify the missing questions before cutover day and build a realistic sequence for your team.

Book a meeting

Have a specific question about your situation? Write to us.