Move from Jira, ClickUp, Linear, Asana or monday

You can move whenever you are ready. Many teams first try Jenzo next to their current tool, then bring tickets over.

How an import works

The import runs through your own AI tool, for example Claude Code or Codex, connected to both your old tracker and Jenzo.

1. Connect your old tracker to your AI tool with that tracker’s own connector (Jira, ClickUp, Linear, Asana or monday).
2. Connect Jenzo. See Use Jenzo from Claude Code, Codex, Cursor, claude.ai and ChatGPT.
3. Ask your AI tool, for example: Import all open tickets from our Jira project WEB into Jenzo. Do a dry run first and show me the counts.
4. Check the dry run, then tell it to go ahead.

Run the import as an admin. Admins keep the original created and closed dates, creators and comment authors.

What comes over

Titles, descriptions, status, comments, checklists, links between tickets, parent and sub-tickets, and attachments by link. Large projects are imported in pages and grouped into one batch.

No duplicates

Each ticket remembers its ID from the old tool, for example the Jira key. Running the import again updates tickets instead of creating new ones, so you can sync once more on the day you switch.

Undo

An admin can ask the AI tool to list import batches and undo one. Undo removes what that batch created, and can be reversed again. Changes the import made to tickets that already existed stay.

Missing something from your old tool?

If you relied on a feature in your previous tool that Jenzo does not have, tell us at [email protected]. Features you had in your previous tool get built within 14 days.