Migrate from Jira to Weft
Shed the ceremony. Bring the work.
Jira carries more structure than Weft does — epics, components, custom fields, workflow states. The point of migrating is to leave most of that behind. Keep the active issues, map them to four columns, and let your AI do the triage.
1. Export from Jira
Open Jira ↗- 1Open Jira → Issue Navigator (or Filters) → pick the issues you want to migrate.
- 2Click "Export" → "Export CSV (all fields)".
- 3Save the CSV locally.
- 4Open the CSV and keep only the columns you care about: Summary, Description, Status, Priority, Sprint, Assignee, Story Points.
2. Map the concepts
Jira and Weft name the same things differently. Here is how they line up.
| Jira | Weft |
|---|---|
| Status: "To Do" / "Backlog" / "Open" | Column: Backlog or Todo |
| Status: "In Progress" / "In Review" | Column: Doing |
| Status: "Done" / "Closed" / "Resolved" | Column: Done |
| Priority: Highest / High / Medium / Low / Lowest | Priority: urgent / high / medium / low / none |
| Sprint | Sprint Create the sprint first, then attach tasks. |
| Epic Link | Task description prefix Prepend "[Epic name]" to the task description; Weft does not model epics. |
| Story Points | estimateMinutes Typical conversion: 1 point = 60 minutes. Adjust to your team. |
| Components / Fix Versions | Task description Append as "Component: X" in the description. |
3. Import using your AI
Weft does not need a separate import script — because the MCP server is the import path. Paste your export into Claude, Cursor, Codex, or ChatGPT (after connecting Weft via one of the setup guides), and ask the AI to create the tasks for you. It uses the real create_task, create_sprint, and move_task tools.
Here is a Jira CSV export. Create each row as a Weft task. Compress Jira statuses into Backlog / Todo / Doing / Done. Map priority as Highest→urgent, High→high, Medium→medium, Low→low, Lowest→none. If the row has an Epic Link, prepend "[Epic: {epic}]" to the description. Create sprints as needed before attaching tasks.
No AI connected yet? Use the built-in CSV importer — upload the export, map the columns, and the whole batch lands in one transaction. (AI clients get the same power via the bulk_create_tasks tool: the entire import in a single call.)
Prefer a hands-on migration? Contact support with your export and we will do it for you while Weft is early. No charge.
What does not transfer
- Workflows and custom fields do not exist in Weft — keep anything important in the description.
- Attachments, comments, and version history stay in Jira.
- Sub-tasks come across as separate tasks.
- If you rely on Jira reports (burndown, velocity), Weft does not replicate them today; ask us what you need and we will prioritize.
Still deciding if Jira is the right tool to leave?
Read the honest side-by-side — when Jira wins, when Weft does. We do not run hit pieces; if Jira is better for your shape of team, we will say so.
Start fresh, but bring your work.
Free for 50 tasks — usually enough to test whether Weft fits how you ship.
Moving data from Atlassian? We can help — contact support.