> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/migration/from-outlook.md).

# From Outlook

Leaving Outlook usually means leaving behind distribution lists, shared mailboxes, and a lot of reply-all. This page covers the parts that are specific to Microsoft 365.

Read [Migrating to Missive](/docs/migration/migrating-to-missive.md) first. It's the team rollout playbook (pilot, workflow, sandbox week, cutover) and applies no matter where you're coming from. Migrating a single account rather than a team? Use [Outlook / Office 365](/docs/core-features/connected-accounts/email-accounts/outlook-office-365.md) instead.

## Converting distribution lists to shared inboxes

This is the core of an Outlook migration, and it's invisible to your contacts.

A distribution list (Microsoft 365 group) can't be connected to Missive directly. You bring it over as a shared mailbox or a [shared address](/docs/core-features/connected-accounts/sharing-options.md):

1. In Microsoft 365, convert the distribution list to a **shared mailbox**.
2. In Missive, go to **Settings** → **Accounts** → **Add account**, connect the mailbox, and choose **shared** when asked.
3. Assign it to the right [team](/docs/core-features/team-inboxes/creating-a-team-space.md).
4. Send a test email to confirm mail is flowing in.

The email address stays exactly the same, so clients keep emailing the address they always have. They won't notice the switch.

{% hint style="info" %}
**Tip:** Internal distribution lists (an **it@** or **accounting@** list) convert the same way. They make great low-stakes inboxes for your [pilot](/docs/migration/migrating-to-missive.md).
{% endhint %}

## What's different coming from Outlook

* **Folders become** [**labels**](/docs/core-features/understanding-label-types.md)**.** Same idea, but one email can carry several labels at once.
* **Outlook rules still apply, so pin their target labels.** If a rule auto-files mail into a folder, that mail skips your inbox in Missive too, exactly like in Outlook. Pin those labels to your sidebar (**+ Pin to Sidebar** → **Labels**) or you won't see the filed mail.
* **You can retire old distribution-list rules.** Personal rules that moved distribution-list mail into a folder no longer fire. That mail now routes to the shared inbox instead of your personal one.
* **Stop CC'ing the old distribution list** on replies. The shared inbox already gives the whole team visibility. CC'ing just recreates the duplicate copies you're leaving behind.
* **Outlook and Missive stay** [**two-way synced**](/docs/core-features/connected-accounts/email-accounts/outlook-office-365.md)**.** Nothing is stranded during the move. Do all real work (replying, assigning, closing, commenting) in Missive, though, or you lose the ownership tracking that's the point of switching. Keep Outlook for old history only.

{% hint style="info" %}
**Note:** Missive [rules](/docs/advanced-features/rules.md) are way more flexible and powerful than Outlook rules, so once you're settled, we recommend looking at recreating your Outlook rules in Missive and expanding upon them.
{% endhint %}

## Outlook-specific checklist

In addition to the [main rollout checklist](/docs/migration/migrating-to-missive.md#rollout-checklist):

* [ ] Admin access to your Microsoft 365 tenant
* [ ] Each distribution list converted to a shared mailbox
* [ ] Rule-target folders and labels pinned to the sidebar
* [ ] Obsolete distribution-list rules retired

## Next steps

* [Migrating to Missive](/docs/migration/migrating-to-missive.md), the full rollout playbook
* [Outlook / Office 365](/docs/core-features/connected-accounts/email-accounts/outlook-office-365.md) for per-account connection, folders, history import, and sync
* [From distribution lists to shared inboxes](/docs/core-features/team-inboxes/from-distribution-lists-to-shared-inboxes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://missiveapp.com/docs/migration/from-outlook.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.