Moving from Jira to a lighter tracker
The usual reason to leave Jira is that the tool has grown bigger than the work. Moving costs a week of attention. This guide helps you decide, and then do it with little loss.
When to move, and when to stay
Move if few people use most of the screens, if nobody owns the workflow configuration, or if the board is not where your team looks first. Stay if you depend on custom workflows with rules for each step, on many integrations with other tools, or on reports across many teams. A lighter tracker will not match those, and moving to it for price alone will cost you the first time someone needs them.
- Move: a team of 2 to 15 that uses Jira as a list with columns.
- Move: you want coding agents to read and file tasks, and your current setup makes that hard.
- Stay: other teams depend on your Jira projects, and moving breaks their reports.
- Stay: you use automation rules that run your release process.
- Wait: a release is due within two weeks. Move after it, not during it.
What to export from Jira
Atlassian’s support page on exporting issues says to open the project, select Issues, narrow the list with a filter if you want, then choose Export, then Export CSV (all fields). It says the all-fields export includes comments, each in its own Comment column in order. The page states no limit on the number of issues. Export one file per project, and keep the files until the week of running both is over.
Decide before you export what you leave behind. Closed issues older than a year are rarely read again. Moving them makes the first load slower and the first search noisier. Keep them in Jira, read only.
What BugBoard can import today
BugBoard has a Jira Cloud connector in the import wizard. You give it your site name, your Atlassian email and an API token. It was written from Atlassian’s documentation and tested against a simulated Jira. It has not yet run against a live Jira site, so treat it as a trial and run it on one small project first. It is for Jira Cloud only, not Data Center or Server.
If you prefer not to use it, the CSV route works with a coding agent: give the agent the file and ask it to load the rows with create_tasks, up to 100 tasks per call, then check a sample against Jira. BugBoard does not read the CSV file by itself.
How the pieces map
| In Jira | In BugBoard (connector) | Note |
|---|---|---|
| Issue types | Bug becomes a bug. Story, Epic and Feature become a feature. Task, Sub-task and Improvement become a change. | Any other type becomes a change and appears in the import report. |
| Statuses | Each status becomes a board column, which you can merge in the wizard. | Merge “In Review” and “Code Review” unless you use both. |
| Priorities | Highest, High and Blocker become High; Medium and Major become Medium; the rest become Low. | BugBoard has three levels, so two ends collapse. |
| Epics | A parent task with the epic’s issues as subtasks. | Not an initiative. You create initiatives yourself. |
| Labels and components | Tags. A component becomes a tag named component:<name>. | Tags are per project. |
| Sprints | Not imported. | Start a new sprint after the move, and put the open work in it by hand. |
| Comments | Comments, with their dates. | A comment restricted to a group or role is skipped and listed in the report. |
| People | Matched by email where Jira shows one. | People without a visible email need a decision in the wizard. |
Each imported task also gets a line pointing back to the original Jira key, so a search for PROJ-123 still finds it. Each Jira project becomes a new BugBoard project. An import does not merge into an existing project.
A checklist
Before
[ ] Who still needs Jira after the move? (list them)
[ ] Closed issues older than <N> months left behind
[ ] CSV exported per project, files saved
[ ] Statuses reduced to the ones you really use
[ ] People list matched to emails
Move
[ ] Trial import of ONE small project
[ ] 10 tasks compared with Jira (title, status, assignee, comments)
[ ] Import report read, skipped items noted
[ ] Remaining projects imported
After
[ ] Agents and scripts pointed at BugBoard
[ ] Sprint started, open work placed in it
[ ] Jira set to read only at the end of week oneRun both for a week
For one week, new work goes into BugBoard and Jira stays open for reading. Do not copy changes in both directions. The import is a one-time copy, and running it again resumes it. It does not sync. At the end of the week, ask three questions: did anyone go back to Jira to find something, did anything go missing, and does the board feel faster to use? If two answers are bad, extend the week.
What you give up
- No app marketplace. You get the API, MCP and webhooks.
- No workflow editor with rules for each step.
- No mobile or desktop app. BugBoard is a web app.