To migrate from Jira, export your issues to CSV, clean the file, run a trial import into a test project, check the result, then import for real and switch the team over on a set day. That is the whole method. This guide walks through each step, the mistakes to avoid, and how AlianHub's AI helps once you land.
Key takeaways
- A migration is a people project with a file in the middle.
- Clean the export before you import it. Never after.
- Run a trial import and treat it as disposable.
- Pick one cut-over day and stop editing in Jira after it.
- Use the move to set up AI agents properly, not to copy old habits.
Before you start
AlianHub lists Jira, ClickUp, Trello, Asana, Monday.com and CSV spreadsheets among the sources you can move in from, and imports can be undone. This guide uses a CSV export because it works with any Jira setup and lets you see every field before it moves.
If you are still deciding whether to switch, read our Jira alternative guide for small teams first.
Do these three things before exporting:
- Invite your team to AlianHub with the same email addresses they use in Jira, so assignees can be matched.
- Pick an owner or admin to run the import.
- Decide what not to move. Closed issues from years ago may belong in an archive, not your new workspace.
Step 1: Export from Jira to CSV
In Jira, open a filter or search that returns the issues for one project, then use its export option to download CSV with all fields. Jira's menus change between versions and editions, so check Atlassian's own docs if yours look different.
Export one project at a time. Smaller files are easier to check.
Step 2: Clean the file
Open the CSV in a spreadsheet and tidy it:
- Remove columns you will not use.
- Make status names consistent.
- Check dates are in one format.
- Confirm assignee emails match your AlianHub members.
| Jira column | Where it should land in AlianHub |
|---|---|
| Summary | Task name |
| Description | Task description |
| Status | Status |
| Assignee | Assignee |
| Priority | Priority |
| Labels | Tags |
| Due date | Due date |
| Custom fields | Custom fields |
Treat this table as a planning aid. The import preview tells you what AlianHub actually recognises.
Tip: keep a copy of the original export untouched. If something goes wrong, you start again from the original, not from a half-edited file.
Step 3: Run a trial import
Create a test project and import into it first.
- Open Settings, then Import & export, and press Start an import (owners and admins).
- Choose the source and pick your file.
- Choose where the tasks should go.
- Read the preview: statuses, tags, assignees, skipped rows and columns not recognised.
- Import, then read the summary before pressing Done.
The trial import is for finding problems, not for keeping. Undo it when you are done.
Step 4: Check the result
Open the test project in List, Board and Table views and check:
- Do task counts match the export?
- Are assignees correct, or left unassigned?
- Did statuses and tags come across as expected?
- Do dates look right?
Fix the file, not the tasks, then run the trial again if needed.
Step 5: Cut over
Pick a day. Do the real import, tell the team, and set Jira to read-only for the migrated projects if you can. Two live systems for the same work is the most common way migrations fail.
How AlianHub's AI helps after you migrate
Moving is a good moment to stop doing the busywork Jira made normal.
How to do this in AlianHub
- Ask what came across. In the Ask box, scope to the new project and ask "What is overdue or blocked?" to find import gaps fast.
- Turn on the Engineering & QA pack. Its role agents start paused, and the pack can be undone.
- Start a Bug Triager at L1. It proposes changes. Moves between lists and assignments wait in the AI Inbox.
- Add a weekly digest. Assign a Reporter agent the digest skill so the team sees what moved and what is stuck.
- Connect your own AI. Open AI, then Connect your AI, and add the address to Claude or Claude Code so developers can ask about tasks without leaving their editor.
- Link code. Connect GitHub or GitLab from the Marketplace so pull requests link to tasks.
A business scenario
A small software team moves two projects off Jira. In the first week, the Ask box flags imported tasks with missing dates, and the Bug Triager proposes priorities for the backlog that came across.
Instead of a "cleanup sprint", the lead approves proposals in the AI Inbox between meetings. The team is planning new work within days, and fewer tickets fall through the gap between the old tool and the new one.
Migrate the work, not the clutter.
Common Jira migration mistakes
| Mistake | What happens | Fix |
|---|---|---|
| Inviting people after the import | Tasks left unassigned | Invite first |
| One giant export | Hard to check | One project at a time |
| No cut-over day | Two sources of truth | Set a date, go read-only |
| Copying every workflow | Old complexity moves too | Start simple, add later |
More import details, including how undo works for ClickUp, are on the moving from ClickUp guide. Running your own instance? See the admin guide.
FAQ
Can I migrate from Jira for free?
AlianHub is free and open source under AGPL-3.0, with no per-seat pricing. You can export from Jira and import into a self-hosted AlianHub yourself.
Can I undo an import if it goes wrong?
AlianHub says imports can be undone. Run a trial into a test project first anyway, so the real import is a formality.
Will my sprints come across?
Check the import preview for what your file carries. AlianHub supports sprints, so you can recreate active ones after the move if needed.
Can AI help clean up after the migration?
Yes. Use the Ask box to find gaps, and agents at L1 to propose fixes that a person approves in the AI Inbox.
Ready to try it? Do a trial import in the live demo or self-host AlianHub for free, and share this plan with whoever owns your Jira admin today.