Importing issues

Moving to Deckbell from another tracker? Export your issues as a CSV file and import them into a project. Deckbell reads the file, suggests how its columns and statuses fit your project, and creates the issues in the background.

Using Linear, Jira Cloud or ClickUp? You can skip the export and connect them directly instead, which also brings over comments, sprints and links between issues. See Importing from Linear, Importing from Jira and Importing from ClickUp. Every way to import, including Slack history, is under Settings → Import.

Before you start

Export your issues from your current tool as CSV:

• Jira — from an issue search, choose Export → Export CSV (all fields).
• Linear — Settings → Import / Export → Export CSV.
• GitHub Issues — export with the GitHub CLI or any "issues to CSV" tool; a file with title, body, state, labels and assignees columns works.
• Trello — export the board to CSV (for example with a CSV export Power‑Up).
• ClickUp — open a list or space view, click ⋯ → Export, and choose CSV with all columns. Tags and assignees written like [a, b] are understood, and subtasks stay under their parent (Parent ID).
• Asana — open the project, click the project name's menu and choose Export → CSV. Sections become statuses, Assignee Email is used for matching, and subtasks stay under their parent task.
• Anything else — any CSV with a header row. You choose which column is which.

A file can have up to 5,000 issues and be up to 10 MB. Split larger exports into several files.

Start an import

1. Open the project's board.
2. Click ⋯ in the header and choose Import issues.
3. Drop your CSV file on the dialog, or click Choose file.

You can also start from Settings → Import: choose the board under CSV file and click Upload a CSV.

You need permission to manage issues to import.

Match the columns

Deckbell recognises the usual column names from Jira (Summary, Issue key, …), Linear (Title, ID, …), GitHub (title, body, state, …), Trello, ClickUp (Task Name, Task ID, …) and Asana (Name, Section/Column, …), and fills in the mapping for you. Check it, and change any column with its dropdown:

Field	What it's used for
Title	The issue title. Required — rows without one are skipped.
Description	The issue description.
Status	Which board column the issue lands in (see below).
Priority	Urgent, High, Medium, Low or No priority. Values like Highest, Critical, P1, Minor or Linear's 0–4 are understood.
Assignee	Matched to a teammate by email address or name, or to one of the project's agents by name. Unknown people are left unassigned.
Labels	Comma‑separated labels. Labels the project doesn't have yet are created.
Estimate	A number, such as story points.
Source ID	The issue's ID in the old tool. Rows that repeat an ID are skipped as duplicates, and for Jira, Linear, ClickUp and Asana files, issues imported before are skipped too.
Parent	The parent issue's ID (or, for Asana, its name). The issue becomes a sub-issue of it.
Completed at	A completion date. Rows that have one go to a done column, whatever their status.

Choose Don't import for any field you want to leave out. A sample value from the first row shows next to each field so you can check the match.

Match the statuses

Every status found in the file is listed with how many issues have it, and the column it will go to. Deckbell picks a column with the same name (for example In Progress), or else one of the same kind — Closed or Resolved go to a done column, Won't do to a canceled one, Open to Todo, and so on.

Change any of them, or choose Don't import to leave those issues out (for example, old canceled work). Issues with an empty status go to the column you pick under Issues with no status go to.

Run it and read the report

Click Import N issues. Deckbell creates the issues in the background — you can close the dialog and keep working; the board fills in when it's done.

When the import finishes, the report shows:

• how many issues were created and how many rows were skipped,
• the row number and reason for each skipped row (missing title, duplicate ID, or a status you chose not to import),
• people who couldn't be matched to a teammate (those issues are unassigned),
• labels that were created.

Your plan's limits apply. On the Free plan the import stops when the workspace reaches its issue limit, and the rest of the rows are listed as skipped with the reason. See Plans & billing.

Imported issues get new Deckbell IDs (for example WEB-42) in the order they appear in the file, and are added below the issues already in each column.