> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trilo.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Slack

> Step-by-step guide to migrate your Slack workspace to Trilo

Moving from Slack to Trilo gives you team messaging plus tasks, docs, calendar, video calls, and AI coworkers—all in one workspace. Stop paying for Slack + Asana + Notion + Zoom + Calendly. This guide walks you through the switch.

## Why Teams Switch from Slack

| Slack Limitation                      | Trilo Solution           |
| ------------------------------------- | ------------------------ |
| Just chat (need Asana for tasks)      | Built-in task management |
| Just chat (need Notion for docs)      | Built-in knowledge base  |
| Just chat (need Zoom for video)       | Built-in video calls     |
| Just chat (need Calendly for booking) | Built-in booking pages   |
| Per-user pricing scales up            | Flat workspace pricing   |
| Slack AI costs \$8.75/user extra      | AI coworkers included    |

## Migration Philosophy

Unlike document or task migrations, chat history migration is often **not recommended**. Here's why:

### Start Fresh vs. Import History

| Approach                 | When to Use                                          |
| ------------------------ | ---------------------------------------------------- |
| **Fresh start**          | Most teams - clean slate, no clutter                 |
| **Export for reference** | If you need to search old conversations occasionally |
| **Full import**          | Rarely needed - only for compliance requirements     |

<Tip>
  Most teams find that a fresh start is actually better. Old Slack channels accumulate noise, outdated discussions, and context that's no longer relevant. Trilo gives you a chance to start clean.
</Tip>

## Before You Start

<Steps>
  <Step title="Create your Trilo workspace">
    [Sign up for Trilo](https://app.trilo.chat) and set up your Areas and Projects.
  </Step>

  <Step title="Map your channel structure">
    Identify which Slack channels become Trilo Projects (each project has its own chat channel).
  </Step>

  <Step title="Invite your team">
    Add team members to Trilo.
  </Step>

  <Step title="Choose your cutover date">
    Pick a date when the team will switch. Communicate it clearly.
  </Step>
</Steps>

## Exporting from Slack (Optional)

If you need to preserve chat history for reference:

### Standard Export (Admin)

<Steps>
  <Step title="Go to Slack Admin">
    Visit your workspace settings at **\[workspace].slack.com/admin**.
  </Step>

  <Step title="Navigate to Settings">
    Click **Settings & Permissions** → **Workspace Settings**.
  </Step>

  <Step title="Import/Export Data">
    Click **Import/Export Data** in the sidebar.
  </Step>

  <Step title="Export">
    Click the **Export** tab and select **Start Export**.
  </Step>

  <Step title="Download">
    You'll receive an email when the export is ready.
  </Step>
</Steps>

### What Gets Exported

| Content Type     | Free/Pro Plan | Business+/Enterprise |
| ---------------- | ------------- | -------------------- |
| Public channels  | Yes           | Yes                  |
| Private channels | No            | Yes (with approval)  |
| Direct messages  | No            | Yes (with approval)  |
| Files            | Links only    | Links only           |

<Info>
  Slack exports are JSON files. They're useful for searching old content but not for importing into other tools. Store them as archives.
</Info>

## Setting Up Trilo Chat

### Channel Structure

In Trilo, chat is organized around Projects:

| Slack Concept    | Trilo Equivalent                              |
| ---------------- | --------------------------------------------- |
| Public channels  | Project channels (visible to project members) |
| Private channels | Private projects or DMs                       |
| DMs              | Direct Messages                               |
| @channel         | @everyone in project                          |
| Threads          | Threaded replies (infinite nesting)           |

### Creating Your Project Structure

<Steps>
  <Step title="Create Areas">
    Map Slack channel categories to Trilo Areas (e.g., "Marketing", "Engineering", "General").
  </Step>

  <Step title="Create Projects">
    Each Slack channel typically becomes a Trilo Project. The project automatically gets a chat channel.
  </Step>

  <Step title="Add team members">
    Add relevant team members to each project.
  </Step>
</Steps>

Example mapping:

| Slack Channel        | Trilo Structure                     |
| -------------------- | ----------------------------------- |
| #general             | General Area → Company-wide Project |
| #engineering         | Engineering Area → Main Project     |
| #eng-frontend        | Engineering Area → Frontend Project |
| #marketing           | Marketing Area → Main Project       |
| #marketing-campaigns | Marketing Area → Campaigns Project  |

## Feature Comparison

### What's Similar

| Feature             | Slack | Trilo                |
| ------------------- | ----- | -------------------- |
| Real-time messaging | ✓     | ✓                    |
| Threaded replies    | ✓     | ✓ (infinite nesting) |
| Emoji reactions     | ✓     | ✓                    |
| File sharing        | ✓     | ✓                    |
| @mentions           | ✓     | ✓                    |
| Search              | ✓     | ✓                    |
| Mobile apps         | ✓     | ✓                    |

### What's Better in Trilo

| Feature       | Slack                        | Trilo                            |
| ------------- | ---------------------------- | -------------------------------- |
| Tasks         | Requires Asana/Jira          | Built-in                         |
| Documents     | Requires Notion/Confluence   | Built-in                         |
| Video calls   | Huddles (limited) or Zoom    | Full video with AI transcription |
| Calendar      | Requires Google/Outlook      | Built-in with booking pages      |
| AI assistants | Slack AI (\$8.75/user extra) | AI coworkers included            |
| Pricing       | Per-user                     | Flat workspace fee               |

## What You Gain by Switching

### Everything in One Place

Instead of:

* Slack for chat
* Asana for tasks
* Notion for docs
* Zoom for video
* Calendly for scheduling

You get one workspace where chat, tasks, docs, video, and calendar all connect.

### AI Coworkers, Not Just Chatbots

Slack AI answers questions. Trilo AI coworkers:

* Join team conversations and provide insights
* Create tasks from discussions
* Transcribe meetings automatically
* Work on projects autonomously

### Simpler Pricing

| Team Size | Slack Pro + Tools | Trilo      |
| --------- | ----------------- | ---------- |
| 5 users   | \~\$100/month     | \$25/month |
| 10 users  | \~\$200/month     | \$25/month |
| 20 users  | \~\$400/month     | \$25/month |

*Slack Pro + Asana + Notion + Zoom estimates*

## Migration Checklist

<AccordionGroup>
  <Accordion title="Week before switch">
    * [ ] Announce migration date to team
    * [ ] Export Slack data (optional, for reference)
    * [ ] Set up Trilo workspace structure
    * [ ] Create all Areas and Projects
    * [ ] Invite team members
  </Accordion>

  <Accordion title="Day of switch">
    * [ ] Post final message in Slack announcing move
    * [ ] Set Slack to read-only or archive channels
    * [ ] Send welcome message in Trilo
    * [ ] Share quick-start tips with team
  </Accordion>

  <Accordion title="First week">
    * [ ] Be active in Trilo to encourage adoption
    * [ ] Answer questions and provide support
    * [ ] Set up first team tasks
    * [ ] Create initial documentation
    * [ ] Schedule a video call using Trilo
  </Accordion>

  <Accordion title="After two weeks">
    * [ ] Gather feedback
    * [ ] Make adjustments based on usage
    * [ ] Consider archiving/canceling Slack
  </Accordion>
</AccordionGroup>

## Tips for Smooth Transition

<AccordionGroup>
  <Accordion title="Lead by example">
    Admins and team leads should be active in Trilo first. When people see important conversations happening in Trilo, they'll follow.
  </Accordion>

  <Accordion title="Don't run both tools long-term">
    Parallel tools cause confusion. Set a firm date to stop using Slack. Two weeks of overlap is usually enough.
  </Accordion>

  <Accordion title="Highlight what's new">
    Show your team features Slack didn't have: built-in tasks, docs, video calls, AI coworkers. Make the switch feel like an upgrade.
  </Accordion>

  <Accordion title="Create a 'Getting Started' doc">
    Write a quick guide for your team covering: where to find things, how to create tasks from chat, how to start a video call.
  </Accordion>
</AccordionGroup>

## Common Questions

<AccordionGroup>
  <Accordion title="Can I import Slack messages to Trilo?">
    Direct import isn't supported, and we don't recommend it. Old chat history rarely provides value and clutters your new workspace. Export from Slack for reference if needed, then start fresh in Trilo.
  </Accordion>

  <Accordion title="What about Slack integrations?">
    Trilo has its own integrations including GitHub, Gmail, and more. The key difference: these integrations work with AI coworkers, so the AI can actually use them to do work.
  </Accordion>

  <Accordion title="Can I still use Slack for some things?">
    You can connect Slack as a Trilo integration to send notifications to Slack channels. But for team communication, pick one tool to avoid confusion.
  </Accordion>

  <Accordion title="What if my team resists the change?">
    Focus on what they gain: no more tool switching, AI that actually helps, video calls without Zoom. The consolidation benefit usually wins people over.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Set Up Team Chat" icon="comments" href="/chat/overview">
    Learn Trilo's messaging features.
  </Card>

  <Card title="Create Your First Task" icon="list-check" href="/tasks/creating-tasks">
    See how tasks work alongside chat.
  </Card>

  <Card title="Start a Video Call" icon="video" href="/chat/voice-video-calls">
    Try built-in video with AI transcription.
  </Card>

  <Card title="Meet AI Coworkers" icon="robot" href="/ai-coworkers/overview">
    See what AI can do in your workspace.
  </Card>
</CardGroup>