Learn · Running an organization · 4 min read

Importing from Jira, Linear, Asana & Trello

Leaving a tracker shouldn't mean retyping it. One Jira project, one Linear team, one Asana project, or one Trello board comes into Wodo as one space: issues, comments, attachments, and the structure around them.

Two ways in

Both finish at the same review step you know from Import and export: a preview of everything found, the people-mapping table, then run:

  • In the app: pick your source, paste an API token, and Wodo fetches and builds the space for you. The easy path.
  • The command-line tool — wodo-import, open source. You run it on your own machine and upload the result, so your API token never touches Wodo's servers. The privacy-conscious path.

In the app

Manage Spaces → Import, choose Jira, Linear, Asana, or Trello, and fill in:

  • Linear — an API key and your team key (e.g. WMT).
  • Jira — your site URL (https://you.atlassian.net), email, an API token, and the project key (e.g. MTR).
  • Asana — a personal access token and the project URL (https://app.asana.com/…).
  • Trello — a token and the board URL (https://trello.com/b/…).

Pick the region the new space should live in and Start import. Wodo fetches the project (a few minutes for a large one) and lands you on the same preview and user-mapping screen as a file import. Your API token is used once for that fetch and is never stored.

The command-line tool

wodo-import is open source, with prebuilt binaries for macOS (Apple Silicon), Windows (x64), and Linux (x64 and ARM) on its releases page. Your credentials stay in your shell:

# Linear
LINEAR_API_KEY=lin_api_… wodo-import linear --team WMT

# Jira
JIRA_EMAIL=you@example.com JIRA_API_TOKEN=… \
  wodo-import jira --project MTR --base-url https://you.atlassian.net

# Asana
ASANA_ACCESS_TOKEN=… \
  wodo-import asana --project https://app.asana.com/0/1201234567890/list

# Trello
TRELLO_API_KEY=… TRELLO_API_TOKEN=… \
  wodo-import trello --board https://trello.com/b/abc123xy
Terminal recording of the wodo-import CLI pulling a Linear team and writing a SpaceExport ZIP
wodo-import pulling a Linear team into a wodo-space-export ZIP, ready to upload.

It writes a wodo-space-export ZIP. Upload that through Manage Spaces → Import like any other archive. And because the source is public, you can read exactly what it fetches and where it sends it.

What comes across

  • Issues, tasks, and cards → items, numbers intact where the source has them: WMT-13 stays 13, and a Trello card keeps its number. Asana tasks aren't numbered, so they're numbered fresh in display order.
  • Workflow states → a Status label (Jira and Linear states, Asana sections, Trello lists), and "done" / "canceled" states become completion states automatically.
  • Priority, type, components, and labels → Wodo labels. In Linear, a label group (say "Complexity" with Low / Medium / High) becomes a label with those exact values; ungrouped labels, Asana tags, and Trello labels collect under a single label. Dropdown-style custom fields (an Asana enum field, a Trello dropdown) become labels of their own.
  • Estimates and story points → an Estimate label.
  • Cycles and sprints → Wodo cycles.
  • Structure beyond the flat list: Asana subtasks become sub-items, Asana milestone-tasks become Wodo milestones, dependencies become blocked-by links, and Trello checklists land as task lists in the item's description.
  • Comments, with their original authors; descriptions and rich text (Jira's ADF, Linear's and Trello's Markdown, Asana's rich HTML) rebuilt in Wodo's editor; and attachments, downloaded and restored; link-only attachments collect in a Links section on the item.

What it won't do

  • Jira, Linear, Asana, and Trello, for now. New sources land in the open-source tool first.
  • A Wodo label holds one value per item, so an issue with two components (or a card with three Trello labels) keeps the first and flags the rest as a preview warning rather than guessing.
  • Custom fields mostly don't come across. Asana and Trello dropdowns map, as above; every other custom field (a number, a date, a text field, and all Jira custom fields) is dropped, counted in a preview warning. (The same idea modeled in Linear as a label group does survive.)
  • People who don't match a current member keep their names on comments, but their assignments are dropped rather than guessed. Trello never shares member emails, so expect to do more of that matching yourself in the mapping table.
  • Per-source small print: Trello's due-complete checkmark isn't carried (completion in Wodo follows the Status column), and comments or attachments on an Asana milestone-task are dropped, since Wodo milestones don't hold them.

Nothing is created until you've seen the preview and approved the mapping, the same safety rail as every other import.