What should a migration communication plan include?
A migration communication plan should include a schedule of messages, a named sender, a named help contact, and a clear list of what each person needs to do. Keep it practical. Your team does not need the technical details. They need to know the date, what will look different, what they must do before and after, and who to ask.
Write the plan during the Planning phase, alongside your migration checklist, so the dates in your messages match the dates in your project. Choose one channel your whole team reliably reads, usually email plus a mention at a staff meeting, and use it for every message.
When should you announce the migration?
Announce the migration as soon as the switchover date is firm, ideally a few weeks ahead. That gives people time to finish work that depends on the old system, ask questions, and clean up their mailboxes. Announcing before the date is set invites rumors and repeated questions. Announcing too late makes the change feel imposed.
If you plan a staged migration, announce the overall plan to everyone, then send batch-specific messages to each group before their date.
What should each message say?
Each message should cover one stage of the move and stay short enough to read on a phone.
Announcement
Say what is changing, why, and the date. Explain that email addresses stay the same, if that is true for your organization. Name the help contact.
One week before
Remind people of the date. List what they need to do, such as noting their Outlook rules and signature, saving desktop files to the right shared location, and making sure they know their phone passcode and have installed recent updates.
The day before
Send sign-in instructions, what to expect in the morning, and a note that some recent messages may take a little while to appear. Link to a short getting-started guide.
Cutover day
Confirm the switch happened, repeat the help contact, and ask people to report anything that looks missing.
First week
Check in, share answers to common questions, and announce any training sessions.
Who should send the messages?
Messages should come from a leader your team listens to, with practical details from whoever runs the project. A note from the owner or office manager signals that the change is a decision, not an experiment. The day-before and cutover-day messages can come from IT or from us, since they are about steps and support. Whoever sends them, use one consistent help contact so questions do not scatter across inboxes.
How do you handle questions and resistance?
Handle questions by answering them openly, and handle resistance by acknowledging what people are giving up. Some people have used Outlook for years and have habits built around folders and rules. Tell them what will feel different, such as Gmail labels instead of Outlook folders, and give them time to adjust. Collect common questions in a shared document and update it after each message.
Training helps more than persuasion. A short, hands-on session in the first week does more than a long email. Our training plan for a Google Workspace rollout and our guide to change management for a Google Workspace switch go deeper. Tell people up front about what does not migrate automatically, so a missing signature is expected, not alarming. The full project view is in how to plan a Google Workspace migration.
Next step
Our migration plans and process include an Adoption phase after the switch, and our support and training options cover the weeks that follow.
Frequently asked questions
Should we tell clients and vendors about the email migration?
Usually only if something they see will change. If your email addresses stay the same, most outside contacts will not notice. Tell them if you are changing domains, shared inbox addresses, or recurring meeting links, and ask key partners to update any allowlists they keep for your mail.
How much training do employees need before cutover?
Less than you might think. A short getting-started guide and a sign-in walkthrough before cutover are usually enough for day one. Deeper training works better in the first week or two, once people have real questions from using Gmail, Calendar, and Drive.
