Migrating to Missive

Roll out Missive to your team. Pilot, workflow, sandbox week, and cutover.

Moving a team to Missive is mostly a people project, not a technical one. This guide is our recommendation for transitioning smoothly, wherever you're coming from.

Why teams migrate

Most teams come to Missive to fix the same handful of problems:

Shared accounts with no ownership. Shared email accounts and distribution lists where everyone gets a copy and nobody knows who's handling it.
Side conversations that get lost. The "can you look at this?" lives in a separate chat, detached from the email.
No visibility or metrics. You can't see who's handling what, how fast you respond, or where the time goes.

In Missive, you can have one copy of each message, assigned to one person, but still visible to the whole team.

Before you start

Pick a rollout lead. One person who owns the migration end to end. The smoothest rollouts always have one.
Decide your inbox structure. One shared inbox per client or team, or a few broader ones like support@ and sales@? Fewer, busier inboxes are simpler. One inbox per client/team gives cleaner separation.
Get admin access to your current email provider. You'll need it to move shared and group addresses, this is especially important for Outlook users.

The recommended rollout, step by step

1. Run a small pilot first

Pick a small team (2 or 3 people) and one low-stakes inbox (an internal address like it@ works well). Connect it, create a team, and use it for real for a week or two. You'll surface the questions your whole team will have before they have them, and you'll know what to put in your company-specific FAQ.

2. Agree on one shared-inbox workflow

This is the step most teams skip, and the one that matters most. Decide as a team how you'll work a shared inbox: how mail gets assigned, when to close versus archive, and who routes what. See From distribution lists to shared inboxes for a proven approach you can adopt as-is.

Why it matters: Missive can keep a shared inbox spotless, but only if everyone works it the same way. One agreed workflow beats a dozen personal habits.

3. Move your shared email accounts into shared inboxes

Connect each shared account (accounting@ or clienta@) to Missive and assign it to a team. Everyone on that team then sees its mail in the Team Inbox. The address never changes, so your contacts won't notice.

How you connect depends on where you're coming from. See your source page under Migration by source for the exact steps. Distribution lists and shared accounts each have their own path.

Tip: You can add one simple rule per inbox to auto-label incoming mail with the team or client name. Keep automation light at launch. You can always add more once people settle in.

4. Give everyone a sandbox week

About a week before go-live, invite the whole team and have each person set up their own account: connect their email, calendar, and signature, and click around. Leave the shared inboxes off for now. Everyone keeps doing real work in their old tool.

This is what makes migrations painless: people get comfortable with Missive at zero stakes, before anything they rely on moves.

Note: Everything in Missive is 2-way synced with your email provider, so actions taken in Missive affect what you see in your email server (Gmail/Outlook/IMAP).

5. Go live in one cutover

After the sandbox week, do the switch in a single window (after hours is easiest): connect the shared inboxes and assign team members as members or observers. The next morning, your team works entirely in Missive.

Run both systems in parallel until you're confident everything's flowing. Connect the new accounts and verify mail arrives before you retire the old setup. Don't turn anything off on day one.

Make the switch painless

A few things that consistently separate smooth rollouts from rocky ones:

Write one short FAQ and point everyone to it. Capture the questions from your pilot, keep it somewhere central, and answer "where's this" and "how do I" with a link. The questions repeat.
Set one workflow, not many. See From distribution lists to shared inboxes.
Let the AI assistant answer "how do I" questions. The ? in the bottom-right searches Missive's own docs. Point new users there first.
Expect a couple of holdouts. Change is hard for some people. Most of the team will be won over within days once the inbox is calmer.
Attend a live demo or watch the pre-recorded demo. Either gives a nice overview of Missive.

What feels different coming from a traditional inbox

Worth telling your team up front. These apply no matter where you're coming from:

Your unified Inbox shows anything you're involved with, not just mail to your address. Assignments and threads you're @mentioned on show up too. Use the filter icon if it feels noisy.
The inbox sorts by last activity, not date received. A new reply moves a thread to the top.
Folders (from Outlook) become labels, and one message can carry several labels.
You assign instead of forward, and you talk on the thread with internal comments instead of starting a side chat.
Read/unread states are per person, not per email. If you read an email in Missive, it won't be marked read for a colleague.