> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macro.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Switch to Macro
> Migration guides for moving to Macro from Superhuman, Notion, Slack, Linear, and ClickUp.
Macro replaces several tools with one unified system, but you don't have to move over all at once. Most teams like to connect their old tools first to ensure nothing gets lost. Then, when you're ready, you can ask the agent to fully migrate you.
If you want to keep most of your existing tools and just use Macro for Email+Tasks or Docs+Files, for example, you're able to keep your other tools connected via MCP.
At a glance, here's what maps to what:
| Coming from | The Macro equivalent |
| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------ |
| Superhuman | [Email](/product/email) and the [inbox](/product/inbox) (both are Gmail clients) |
| Notion | [Docs](/product/docs), plus built-in [tasks](/product/tasks) and [CRM](/product/crm) |
| Slack | [Channels](/product/channels) |
| Linear | [Tasks](/product/tasks) |
| ClickUp | [Tasks](/product/tasks), with [docs](/product/docs), [CRM](/product/crm), and [channels](/product/channels) replacing the rest of the suite |
| Google Drive / Dropbox | [File storage](/product/folders) |
| Zoom / Meet | [Calls](/product/calls) |
## From Superhuman
Before creating Macro, we were Superhuman users ourselves, and were heavily inspired by them when designing Macro's email. The main difference between us and Superhuman is that Macro supports multiple accounts in [one inbox](/product/email#multi-account-inbox). It also adds more intelligent [Signal vs. Noise](/product/email#signal-vs-noise) splits, and it fully unifies messaging, tasks, @mentions and more into a single inbox. Another benefit of Macro is that [Agents](/product/agents) can draft, triage, and send mail for you right from AI chat with an embedded email widget.
Both Macro and Superhuman are just clients on top of Gmail, so there's no migration in either direction; your mail stays in Gmail.
The j / k / e triage shortcuts you already know work unchanged.
| | Superhuman | Macro |
| :---------------------------------------------------------- | :--------: | :---: |
| Built on Gmail (no migration) | ✓ | ✓ |
| j / k / e triage shortcuts | ✓ | ✓ |
| Multiple accounts in one unified inbox | X | ✓ |
| [Signal vs. Noise](/product/email#signal-vs-noise) split | X | ✓ |
| Messages, tasks, and @mentions in the same inbox | X | ✓ |
| [Agents](/product/agents) that draft, triage, and send | X | ✓ |
To switch:
1. Connect your Gmail or Google Workspace account (ideally at signup, or later in **Settings**).
2. Your mail, labels, and history are already there because Macro syncs with Gmail directly.
That's it. You can run both during the transition, or keep Superhuman around if you want.
## From Notion
Notion asks you to build your own tools out of markdown pages and databases: your CRM, your task tracker, and your wiki are all databases of markdown files. We think databases are the wrong level of abstraction for serious business software. Even before AI, when scaling our previous company, we had to migrate off of Notion onto HubSpot, Linear, etc. as the team grew. **Markdown files and databases simply aren't powerful enough compared to domain-specific tools.** The longer version of this argument is in the [FAQ](/faq) and the video below.
In Macro, tasks, CRM, email, channels, and files are each their own best-in-class, purpose-built [block](/concepts/blocks), and they all share one data model and one search index. Yes, you give up some of Notion's freeform database flexibility, but **each block works like a real product**, and agents can read all of it as one context vs. paging through a rate-limited API.
| | Notion | Macro |
| :----------------------------- | :--------------: | :---------------------------------------------------: |
| Markdown-native docs | ✓ | ✓ |
| Tasks | Sort of | Built in |
| CRM | No | Built in |
| Email and channels | X | ✓ |
| Freeform databases | ✓ | [Properties](/concepts/properties) on built-in blocks |
| Agent access to your workspace | Rate-limited API | One unified search index |
The docs import is clean because both sides are markdown-native:
1. Go to **Settings → Connectors** and connect Notion.
2. Open an agent chat (c + a) and ask it to import. For example:
```text theme={null}
Import my Notion docs from the "Engineering" workspace as Macro docs.
Keep the folder structure and skip anything archived.
```
The agent reads pages through the Notion connector and recreates them as [Macro documents](/product/docs). For structured Notion databases, think about whether each one is really tasks, CRM records, or a doc with [properties](/concepts/properties) and ask the agent to import them as such.
You can also keep Notion MCP connected indefinitely so agents can reference legacy content. Don't feel the need to migrate everything — we personally like starting with a clean slate!
## From Slack
The main thing Macro improves on versus Slack is making channels/DM's less noisy and more focused for technical discussions. The first few replies in a thread show inline, so you don't have to open a thread every time someone replies, and a busy channel looks more like Reddit: organized, and easy to remember where a conversation happened.
Channels also share a single unified inbox with your email, split into [Signal vs. Noise](/product/email#signal-vs-noise).
The other big thing is [channel-based sharing](/permissions): [@mention](/concepts/mentions) a doc or task in a channel and every member gets access to it automatically. This avoids the Slack+Notion footgun where people need to ask "hey can you share \_\_ with me?"
| | Slack | Macro |
| :----------------------------------------------- | :---: | :--------------------------------------: |
| Channels, threads, emoji | ✓ | ✓ |
| Inline thread replies (forum-style reading) | X | ✓ |
| One inbox shared with your email | X | ✓ |
| @mention a doc or task to share it automatically | X | ✓ |
| External channels with customers (Slack Connect) | ✓ | Keep Slack connected as an MCP connector |
To switch:
1. Create a channel per team or project (c + m).
2. Add people by email. They don't need a Macro account yet to be included.
3. Use @mentions to share docs and tasks as you discuss them.
If you're not ready to leave Slack (archives, Slack Connect with customers), connect it under **Settings → Connectors** as an MCP connector so agents in Macro can still search it. Many teams run Macro for internal communication and keep Slack only for external channels during the transition.
## From Linear
In building Macro Tasks we were heavily inspired by Linear: status, priority, assignee, keyboard-first, and a [GitHub integration](/integrations/github) that covers the workflow you're used to. Copy a branch name from a task and it moves through "In Progress," "In Review," and "Done" as you branch, open the PR, and merge.
The difference between Macro and Linear is that on Macro, tasks live in the same app as your email, channels, and docs. You can turn an email or a channel message into a task in one click, and non-engineers can see engineering work without a seat in a separate tool. Tasks are also less ceremonious: fields are minimal by default, and story points, effort, etc. are there via [properties](/concepts/properties) if you really want them, but we advise keeping it light.
| | Linear | Macro |
| :------------------------------------------------------------------------------ | :------------------------------: | :-----------------------------------------------------------------------: |
| Status, priority, assignee, keyboard-first | ✓ | ✓ |
| [GitHub integration](/integrations/github): branch, PR, and merge move the task | ✓ | ✓ |
| Tasks in the same app as your email, channels, and docs | X | ✓ |
| Turn an email or channel message into a task in one click | X | ✓ |
| Non-engineers see engineering work | Separate seat in a separate tool | Same workspace |
| Deep workflow configuration (cycles, triage, custom flows) | ✓ | Minimal by default, [properties](/concepts/properties) when you want them |
For migration, most teams just recreate their open work; finished issues rarely justify carrying over. If you do want history, connect Linear under **Settings → Connectors** and have an agent bring open issues across.
## From ClickUp
ClickUp covers tasks, docs, chat, goals, and whiteboards through a deep stack of spaces, folders, lists, and custom statuses that you configure yourself. Macro covers the same ground with dedicated [tasks](/product/tasks), [docs](/product/docs), [channels](/product/channels), and [CRM](/product/crm) that share one data model.
There's less setup and fewer knobs because each tool is already built for its job. Tasks keep the essentials (status, priority, assignee, and [properties](/concepts/properties) when you want them), and [agents](/product/agents) can read across all of it as one context.
The biggest day-to-day change is that tasks live in the same app as your email, channels, and docs. You can turn a message or an email into a task in one click, and @mentioning a task in a channel shares it automatically.
| | ClickUp | Macro |
| :------------------------------------------------------------- | :-------------------------------------: | :----------------------: |
| Tasks, docs, chat | ✓ | ✓ |
| Setup required | Spaces, folders, lists, custom statuses | Works out of the box |
| CRM | Configure it yourself | [Built in](/product/crm) |
| Email | X | ✓ |
| One data model, one search index | X | ✓ |
| [Agents](/product/agents) with your whole workspace as context | X | ✓ |
To switch:
1. Recreate your active lists as Macro tasks. Most teams skip closed work.
2. If you want history or a gradual cutover, connect ClickUp under **Settings → Connectors** as an MCP connector and ask an agent to bring open tasks across.
3. Move ClickUp Docs over too: they're markdown-native, so an agent can recreate them as [Macro documents](/product/docs). Open an agent chat (c + a) and ask it to import. For example:
```text theme={null}
Import my ClickUp Docs from the "Engineering" space as Macro docs.
Keep the folder structure and skip anything archived.
```
## Everything else
Any tool with an MCP server can be connected under **Settings → Connectors**, which makes it readable to your agents. That works as a migration path (ask an agent to copy content over) or as a permanent bridge for tools you keep. Files mostly migrate themselves: email attachments are extracted into [file storage](/product/folders) automatically, and anything you drag into a channel or doc is imported and searchable.
## Macro vs. the world
Here's the full picture side by side of how Macro compares to the rest of the toolset.
| | Macro | Superhuman | Notion | Slack | Linear | ClickUp |
| :---------------------------------------- | :---: | :--------: | :-----------: | :---------: | :----: | :---------: |
| [Email](/product/email) | ✓ | ✓ | X | X | X | X |
| [Channels](/product/channels) | ✓ | X | X | ✓ | X | ✓ |
| [Tasks](/product/tasks) | ✓ | X | Via databases | X | ✓ | ✓ |
| [Docs](/product/docs) | ✓ | X | ✓ | X | X | ✓ |
| [CRM](/product/crm) | ✓ | X | Via databases | X | X | Via setup |
| [File storage](/product/folders) | ✓ | X | Attachments | Attachments | X | Attachments |
| [Calls](/product/calls) | ✓ | X | X | Huddles | X | X |
| [Agents](/product/agents) | ✓ | X | ✓ | X | ✓ | ✓ |
| [Unified Inbox](/product/inbox) | ✓ | X | X | X | X | X |
| [Unified Search](/product/search) | ✓ | X | X | X | X | X |
| [Unified Memory](/product/unified-memory) | ✓ | X | X | X | X | X |
Book a call and we'll walk your team through the migration.
Both Macro and Superhuman are just clients on top of Gmail, so there's no migration in either direction; your mail stays in Gmail.
The j / k / e triage shortcuts you already know work unchanged.
| | Superhuman | Macro |
| :---------------------------------------------------------- | :--------: | :---: |
| Built on Gmail (no migration) | ✓ | ✓ |
| j / k / e triage shortcuts | ✓ | ✓ |
| Multiple accounts in one unified inbox | X | ✓ |
| [Signal vs. Noise](/product/email#signal-vs-noise) split | X | ✓ |
| Messages, tasks, and @mentions in the same inbox | X | ✓ |
| [Agents](/product/agents) that draft, triage, and send | X | ✓ |
To switch:
1. Connect your Gmail or Google Workspace account (ideally at signup, or later in **Settings**).
2. Your mail, labels, and history are already there because Macro syncs with Gmail directly.
That's it. You can run both during the transition, or keep Superhuman around if you want.
## From Notion
Notion asks you to build your own tools out of markdown pages and databases: your CRM, your task tracker, and your wiki are all databases of markdown files. We think databases are the wrong level of abstraction for serious business software. Even before AI, when scaling our previous company, we had to migrate off of Notion onto HubSpot, Linear, etc. as the team grew. **Markdown files and databases simply aren't powerful enough compared to domain-specific tools.** The longer version of this argument is in the [FAQ](/faq) and the video below.
In Macro, tasks, CRM, email, channels, and files are each their own best-in-class, purpose-built [block](/concepts/blocks), and they all share one data model and one search index. Yes, you give up some of Notion's freeform database flexibility, but **each block works like a real product**, and agents can read all of it as one context vs. paging through a rate-limited API.
| | Notion | Macro |
| :----------------------------- | :--------------: | :---------------------------------------------------: |
| Markdown-native docs | ✓ | ✓ |
| Tasks | Sort of | Built in |
| CRM | No | Built in |
| Email and channels | X | ✓ |
| Freeform databases | ✓ | [Properties](/concepts/properties) on built-in blocks |
| Agent access to your workspace | Rate-limited API | One unified search index |
The docs import is clean because both sides are markdown-native:
1. Go to **Settings → Connectors** and connect Notion.
2. Open an agent chat (c + a) and ask it to import. For example:
```text theme={null}
Import my Notion docs from the "Engineering" workspace as Macro docs.
Keep the folder structure and skip anything archived.
```
The agent reads pages through the Notion connector and recreates them as [Macro documents](/product/docs). For structured Notion databases, think about whether each one is really tasks, CRM records, or a doc with [properties](/concepts/properties) and ask the agent to import them as such.
You can also keep Notion MCP connected indefinitely so agents can reference legacy content. Don't feel the need to migrate everything — we personally like starting with a clean slate!
## From Slack
The main thing Macro improves on versus Slack is making channels/DM's less noisy and more focused for technical discussions. The first few replies in a thread show inline, so you don't have to open a thread every time someone replies, and a busy channel looks more like Reddit: organized, and easy to remember where a conversation happened.
Channels also share a single unified inbox with your email, split into [Signal vs. Noise](/product/email#signal-vs-noise).
The other big thing is [channel-based sharing](/permissions): [@mention](/concepts/mentions) a doc or task in a channel and every member gets access to it automatically. This avoids the Slack+Notion footgun where people need to ask "hey can you share \_\_ with me?"
| | Slack | Macro |
| :----------------------------------------------- | :---: | :--------------------------------------: |
| Channels, threads, emoji | ✓ | ✓ |
| Inline thread replies (forum-style reading) | X | ✓ |
| One inbox shared with your email | X | ✓ |
| @mention a doc or task to share it automatically | X | ✓ |
| External channels with customers (Slack Connect) | ✓ | Keep Slack connected as an MCP connector |
To switch:
1. Create a channel per team or project (c + m).
2. Add people by email. They don't need a Macro account yet to be included.
3. Use @mentions to share docs and tasks as you discuss them.
If you're not ready to leave Slack (archives, Slack Connect with customers), connect it under **Settings → Connectors** as an MCP connector so agents in Macro can still search it. Many teams run Macro for internal communication and keep Slack only for external channels during the transition.
## From Linear
In building Macro Tasks we were heavily inspired by Linear: status, priority, assignee, keyboard-first, and a [GitHub integration](/integrations/github) that covers the workflow you're used to. Copy a branch name from a task and it moves through "In Progress," "In Review," and "Done" as you branch, open the PR, and merge.
The difference between Macro and Linear is that on Macro, tasks live in the same app as your email, channels, and docs. You can turn an email or a channel message into a task in one click, and non-engineers can see engineering work without a seat in a separate tool. Tasks are also less ceremonious: fields are minimal by default, and story points, effort, etc. are there via [properties](/concepts/properties) if you really want them, but we advise keeping it light.
| | Linear | Macro |
| :------------------------------------------------------------------------------ | :------------------------------: | :-----------------------------------------------------------------------: |
| Status, priority, assignee, keyboard-first | ✓ | ✓ |
| [GitHub integration](/integrations/github): branch, PR, and merge move the task | ✓ | ✓ |
| Tasks in the same app as your email, channels, and docs | X | ✓ |
| Turn an email or channel message into a task in one click | X | ✓ |
| Non-engineers see engineering work | Separate seat in a separate tool | Same workspace |
| Deep workflow configuration (cycles, triage, custom flows) | ✓ | Minimal by default, [properties](/concepts/properties) when you want them |
For migration, most teams just recreate their open work; finished issues rarely justify carrying over. If you do want history, connect Linear under **Settings → Connectors** and have an agent bring open issues across.
## From ClickUp
ClickUp covers tasks, docs, chat, goals, and whiteboards through a deep stack of spaces, folders, lists, and custom statuses that you configure yourself. Macro covers the same ground with dedicated [tasks](/product/tasks), [docs](/product/docs), [channels](/product/channels), and [CRM](/product/crm) that share one data model.
There's less setup and fewer knobs because each tool is already built for its job. Tasks keep the essentials (status, priority, assignee, and [properties](/concepts/properties) when you want them), and [agents](/product/agents) can read across all of it as one context.
The biggest day-to-day change is that tasks live in the same app as your email, channels, and docs. You can turn a message or an email into a task in one click, and @mentioning a task in a channel shares it automatically.
| | ClickUp | Macro |
| :------------------------------------------------------------- | :-------------------------------------: | :----------------------: |
| Tasks, docs, chat | ✓ | ✓ |
| Setup required | Spaces, folders, lists, custom statuses | Works out of the box |
| CRM | Configure it yourself | [Built in](/product/crm) |
| Email | X | ✓ |
| One data model, one search index | X | ✓ |
| [Agents](/product/agents) with your whole workspace as context | X | ✓ |
To switch:
1. Recreate your active lists as Macro tasks. Most teams skip closed work.
2. If you want history or a gradual cutover, connect ClickUp under **Settings → Connectors** as an MCP connector and ask an agent to bring open tasks across.
3. Move ClickUp Docs over too: they're markdown-native, so an agent can recreate them as [Macro documents](/product/docs). Open an agent chat (c + a) and ask it to import. For example:
```text theme={null}
Import my ClickUp Docs from the "Engineering" space as Macro docs.
Keep the folder structure and skip anything archived.
```
## Everything else
Any tool with an MCP server can be connected under **Settings → Connectors**, which makes it readable to your agents. That works as a migration path (ask an agent to copy content over) or as a permanent bridge for tools you keep. Files mostly migrate themselves: email attachments are extracted into [file storage](/product/folders) automatically, and anything you drag into a channel or doc is imported and searchable.
## Macro vs. the world
Here's the full picture side by side of how Macro compares to the rest of the toolset.
| | Macro | Superhuman | Notion | Slack | Linear | ClickUp |
| :---------------------------------------- | :---: | :--------: | :-----------: | :---------: | :----: | :---------: |
| [Email](/product/email) | ✓ | ✓ | X | X | X | X |
| [Channels](/product/channels) | ✓ | X | X | ✓ | X | ✓ |
| [Tasks](/product/tasks) | ✓ | X | Via databases | X | ✓ | ✓ |
| [Docs](/product/docs) | ✓ | X | ✓ | X | X | ✓ |
| [CRM](/product/crm) | ✓ | X | Via databases | X | X | Via setup |
| [File storage](/product/folders) | ✓ | X | Attachments | Attachments | X | Attachments |
| [Calls](/product/calls) | ✓ | X | X | Huddles | X | X |
| [Agents](/product/agents) | ✓ | X | ✓ | X | ✓ | ✓ |
| [Unified Inbox](/product/inbox) | ✓ | X | X | X | X | X |
| [Unified Search](/product/search) | ✓ | X | X | X | X | X |
| [Unified Memory](/product/unified-memory) | ✓ | X | X | X | X | X |