Skip to content
Deckbell

Migrate

Switch to Deckbell

Bring your chat history from Slack and your issues from Linear, Jira, ClickUp, Asana, Trello, GitHub or any CSV. Deckbell matches statuses and people for you, and tells you exactly what it skipped.

Start for freePlan the move

What you can import

Importers and what each one brings across
FromHowWhat comes across
SlackWorkspace export (ZIP)Channels, private channels and DMs in your export, with messages, threads and reactions
LinearAPI key, or CSVIssues with status, priority, labels, estimate, cycle, sub-issues, relations and comments
JiraAPI token, or CSVIssues with description, status, priority, labels, parent, links and comments
ClickUpAPI token, or CSVTasks with status, priority, tags, subtasks, dependencies and comments
AsanaCSVTasks with section, assignee, tags and description
TrelloCSVCards with list, labels and members
GitHub Issues, Notion or any CSVCSVWhatever columns your file has

Importing, tool by tool

Import issues from a board's ⋯ menu (Import issues), and Slack history from Settings. Issue imports need permission to manage issues; Slack imports are run by a workspace owner or admin.

From Slack

  1. Invite your team to Deckbell first: people in the export are matched to members by email address.
  2. In Slack, a Workspace Owner or Admin opens Workspace settings → Import/Export Data → Export, picks a date range and downloads the ZIP.
  3. In Deckbell, go to Settings → Import and upload the ZIP. The preview lists every conversation and who matched; tick the ones to bring over. Free and Pro Slack exports hold public channels only; on Business+ and Enterprise, owners can also export private channels and DMs.
  4. Messages keep their dates, authors, threads and reactions, and nobody is notified about old messages. Importing a newer export later skips what is already there.

Deckbell vs Slack (and Linear + Slack)

From Linear

  1. Create a personal API key in your Linear settings and paste it into Deckbell, then pick the teams to import. Or export a CSV from Linear (Settings → Import / Export).
  2. Each Linear status is matched to a board column, and Linear's 0–4 priorities to Deckbell's.
  3. People are matched by email; anyone who can’t be matched is left unassigned and listed in the report.

Deckbell vs Linear

From Jira

  1. Create an API token for your Atlassian account and connect your Jira Cloud site with your email and the token, then pick the projects. Or run an issue search in Jira and choose Export → Export CSV (all fields).
  2. Deckbell recognises Jira fields and priorities such as Highest, Critical or P1.
  3. Map each Jira status to a board column, or leave some out, such as old canceled work.

Deckbell vs Jira

From ClickUp

  1. Copy your personal API token from your ClickUp settings, paste it into Deckbell and pick the Lists to import. Or export a List to CSV.
  2. Tags become labels, subtasks become sub-tasks and dependencies become blocking relations.
  3. Map each ClickUp status to a board column.

Deckbell vs ClickUp

From Asana

  1. Export the project to CSV from the project's menu in Asana.
  2. Upload it to a Deckbell board. Deckbell recognises Asana's columns and suggests how they map.
  3. Turn sections into board columns, then add sprints and estimates if your Asana project used custom fields for them.

Deckbell vs Asana

From Trello

  1. Export the board to CSV, for example with a CSV export Power-Up.
  2. Each Trello list maps to a board column, and labels come across as labels.
  3. Members are matched to teammates by email or name.

From GitHub Issues, Notion or any CSV

  1. Export a CSV with a header row: GitHub Issues (title, body, state, labels, assignees), a Notion database (Export → Markdown & CSV), or a spreadsheet.
  2. Choose which column is the title, description, status, priority, assignee, labels, estimate and source ID.
  3. A file can hold up to 5,000 issues and be up to 10 MB; split larger exports into several files.

Deckbell vs Notion

Plan the move in four steps

  1. Step 1

    Set up the workspace

    Create it, invite people (or turn on SAML single sign-on on Enterprise) and connect GitHub.

  2. Step 2

    Import the work

    Import issues into one board per project, check the report, and fix any unmatched people.

  3. Step 3

    Bring the conversation

    Import your Slack export. Each board also gets its own channel for new discussion.

  4. Step 4

    Switch over

    Start the next sprint in Deckbell, keep the old tools read-only for a sprint, then cancel them.

Step-by-step guides are in the Deckbell docs.

FAQ

Migration questions

Anything else? Write to support@deckbell.com and a human replies.

What does an issue import bring across?

Issues with their title, description, status, priority, assignee, labels and estimate. Imports straight from Linear, Jira and ClickUp also bring comments, sub-tasks and relations, and Linear cycles. Assignees are matched to teammates by email; anyone who can’t be matched is left unassigned and listed in the report. Labels the project doesn’t have yet are created.

Do issue IDs change?

Yes. Imported issues get new Deckbell keys, like WEB-42. The old ID can be kept as the source ID, and rows that repeat an ID are skipped as duplicates.

Can we keep working while an import runs?

Yes. Imports run in the background: close the dialog and keep working, and the board fills in when it’s done. The report then shows what was created and what was skipped, and why.

Are our API keys and tokens stored?

Only while an import runs. Deckbell stores them encrypted when you start the import and deletes them when it finishes.

Can we bring Slack DMs and private channels?

Yes, when they're in your Slack export. Which conversations an export includes depends on your Slack plan and its export settings. You choose which of them to import.

Do you help with large migrations?

Yes. Write to sales@deckbell.com and we’ll help plan the move for larger workspaces.

Bring your team over.

Free for up to 5 members, no credit card. Import when you're ready.

Start for freeTalk to sales