Skip to content

armgit / macro

Public Imported from GitHub
0

Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.

13.9 KB
Raw Blame
---
title: "Switch to Macro"
icon: "arrow-right-arrow-left"
description: "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 [Home](/product/home) (both are Gmail and Outlook clients) |
| Notion | [Docs](/product/docs) and [databases](/product/databases), 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 | [Drive](/product/drive) |
| Google Sheets / Excel | [Spreadsheets](/product/spreadsheets) |
| Zoom / Meet | [Calls](/product/calls) |

## From Superhuman

The main difference between us and Superhuman is that Macro supports multiple accounts in one inbox. It also adds more intelligent Signal vs. Noise splits, and it fully unifies messaging, tasks, @mentions and more into a single inbox. Another benefit of Macro is that Agents can draft, triage, and send mail for you right from AI chat with an embedded email widget.

<div className="switch-mark" role="img" aria-label="The Superhuman app icon with an arrow pointing to the Macro app icon">
  <img className="switch-mark-cream" src="/images/switch-from-superhuman-cream.svg" alt="" />
  <img className="switch-mark-dark" src="/images/switch-from-superhuman.svg" alt="" />
</div>

Both Macro and Superhuman are clients on top of Gmail and Outlook, so there's no migration in either direction. Your mail stays in Gmail or Outlook / Microsoft 365.

The <kbd>j</kbd> / <kbd>k</kbd> / <kbd>e</kbd> triage shortcuts you already know work unchanged.

|  | Superhuman | Macro |
| :-- | :-: | :-: |
| Built on Gmail and Outlook (no migration) | ✓ | ✓ |
| <kbd>j</kbd> / <kbd>k</kbd> / <kbd>e</kbd> 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 | ✓ |

<iframe src="https://www.youtube.com/embed/tnsxkywzTvY" title="Email on Macro" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

**To switch:**

1. On Home, click **Connect email** when the feed is empty, or open **Settings → Email** and click **Connect**.
2. Choose Gmail or Outlook / Microsoft 365 and finish signing in.
3. Your mail and history are already there because Macro syncs with that account directly.

That's it. You can run both during the transition, or keep Superhuman around if you want.

## From Notion

In Macro, tasks, CRM, email, channels, and files (docs, databases, spreadsheets, canvases, and other files in Drive) are each their own best-in-class, purpose-built Block, and they all share one data model and one search index. **Each Block works like a real product**, and agents can read all of it as one context vs. paging through a rate-limited API.

<div className="switch-mark" role="img" aria-label="The Notion app icon with an arrow pointing to the Macro app icon">
  <img className="switch-mark-cream" src="/images/switch-from-notion-cream.svg" alt="" />
  <img className="switch-mark-dark" src="/images/switch-from-notion.svg" alt="" />
</div>

|  | Notion | Macro |
| :-- | :-: | :-: |
| Markdown-native docs | ✓ | ✓ |
| [Databases](/product/databases) | ✓ | ✓ |
| [Spreadsheets](/product/spreadsheets) | X | ✓ |
| Tasks | Sort of | Built in |
| CRM | No | Built in |
| Email and channels | X | ✓ |
| Agent access to your workspace | Rate-limited API | One unified search index |

<iframe src="https://www.youtube.com/embed/hyU1XYmxkYM" title="What We Learned from Notion" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

**To switch:**

1. Open **Settings → Integrations**.
2. Under **MCP integrations**, click **Connect** on Notion and finish signing in.
3. Open Agents, click **New conversation**, and ask it to import. For example:

```text
Import my Notion workspace. Show me the plan before you create anything.
```

Pages become docs, kept in the same folder tree. Databases become databases. Databases that we detect track work become tasks.

We have a dedicated Notion importer. It reads the connected workspace and shows a plan of the pages, databases, and task lists it found. You choose what to include and whether the team can see it. Nothing is created until you approve the plan, and anything already imported stays.

## 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.

<div className="switch-mark" role="img" aria-label="The Slack app icon with an arrow pointing to the Macro app icon">
  <img className="switch-mark-cream" src="/images/switch-from-slack-cream.svg" alt="" />
  <img className="switch-mark-dark" src="/images/switch-from-slack.svg" alt="" />
</div>

Channel messages and @mentions appear on [Home](/product/home) with your email.

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 for external channels |

<iframe src="https://www.youtube.com/embed/1gDOXUxHo0U" title="What Macro learned from Slack/Superhuman" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

**To switch:**

An admin does this from team settings.

1. Open **Settings → Team → Connections**.
2. Click **Import from Slack**.

**Import with history** uses a Slack export from a workspace admin. Pick the channels, leave **Include message history** on to bring messages and threads, confirm the export belongs to the team's Slack workspace, and click **Import selected channels**. Files are not imported.

**Import channels without history** copies public channels and the teammates who are on your team. Messages stay in Slack.

## From Linear

<div className="switch-mark" role="img" aria-label="The Linear app icon with an arrow pointing to the Macro app icon">
  <img className="switch-mark-cream" src="/images/switch-from-linear-cream.svg" alt="" />
  <img className="switch-mark-dark" src="/images/switch-from-linear.svg" alt="" />
</div>

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 | ✓ | ✓ |
| [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 |

<iframe src="https://www.youtube.com/embed/nHxqE2mVKrA" title="What We Learned from Linear" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

**To switch:**

1. Open **Settings → Integrations**.
2. Under **MCP integrations**, click **Connect** on Linear and finish signing in.
3. Open Agents, click **New conversation**, and ask it to import. For example:

```text
Import my Linear workspace. Show me the plan before you create anything.
```

Issues become tasks. Linear teams, projects, and initiatives become projects.

## 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.

<div className="switch-mark" role="img" aria-label="The ClickUp app icon with an arrow pointing to the Macro app icon">
  <img className="switch-mark-cream" src="/images/switch-from-clickup-cream.svg" alt="" />
  <img className="switch-mark-dark" src="/images/switch-from-clickup.svg" alt="" />
</div>

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 | ✓ |

<iframe src="https://www.youtube.com/embed/gxJquVXRX5A" title="Tasks on Macro" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

**To switch:**

1. Open **Settings → Integrations**.
2. Under **MCP integrations**, click **Add server**.
3. Set **Name** to ClickUp and **URL** to `https://mcp.clickup.com/mcp`.
4. Sign in to ClickUp when Macro asks.
5. Open Agents, click **New conversation**, and tell it what to copy. For example:

```text
Import my open ClickUp tasks and the Docs in the Engineering space.
Skip archived work. Show me the list before you create anything.
```

The agent reads ClickUp and lists what it will create. It creates tasks and docs only after you say to.

## Everything else

**Settings → Integrations → MCP integrations** is where these connections live. Notion and Linear have a **Connect** button. For any other tool, click **Add server**, enter its name and MCP URL, and sign in.

Then start a chat and name what to copy and what to skip. Ask the agent to show the list before it creates anything. The connected tool is only read.

Macro's MCP server has no rate limit. That includes the Free plan.

Files mostly migrate themselves: email attachments are extracted into [Drive](/product/drive) 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 | ✓ |
| [Databases](/product/databases) | ✓ | X | ✓ | X | X | X |
| [Spreadsheets](/product/spreadsheets) | ✓ | X | X | X | X | X |
| [Canvas](/product/canvas) | ✓ | X | X | X | X | Whiteboards |
| [CRM](/product/crm) | ✓ | X | Via databases | X | X | Via setup |
| [Drive](/product/drive) | ✓ | X | Attachments | Attachments | X | Attachments |
| [Calendar](/product/calendar) | ✓ | ✓ | Separate app | X | X | ✓ |
| [Calls](/product/calls) | ✓ | X | X | Huddles | X | X |
| [Reviews](/product/reviews) | ✓ | X | X | X | X | X |
| [Agents](/product/agents) | ✓ | X | ✓ | X | ✓ | ✓ |
| [Routines](/product/routines) | ✓ | X | Automations | Workflows | X | Automations |
| [Home feed](/product/home) | ✓ | X | X | X | X | X |
| [Projects](/product/projects) | ✓ | X | Via databases | X | ✓ | ✓ |
| [Unified Tagging](/product/tagging) | ✓ | X | X | X | X | X |
| [Unified Search](/product/search) | ✓ | X | X | X | X | X |
| [Unified Memory](/product/unified-memory) | ✓ | X | X | X | X | X |

<Card title="Want help switching?" icon="calendar" href="https://macro.com/app/book/6de4003c-15e4-549f-b5a9-0e930bbf56e4/macro-demo">
  Book a call and we'll walk your team through the migration.
</Card>