Before you begin
Anyone who can search the issues.
In Crittiks, open Settings › Migration and choose Jira. Keep a copy of the original export. Invite the teammates who should own the imported records before matching owners.
Prepare your files
A CSV export of an issue search (all fields).
Export an issue search
In Jira open Filters > Search work items, filter to the project, then Export > Export CSV (all fields).
Drop the file in Crittiks
Each Jira project becomes a project, statuses are matched or created, and sub-tasks sit under their parent issue.
What moves
- Each Jira project as a project
- Issue statuses
- Issues as tasks, sub-tasks as subtasks
- Assignees, priorities, labels and due dates
What stays in your old tool
- Email bodies and attachments
- Automations and workflows
- Reports and dashboards
- Sprints, boards and versions
- Comments, attachments and issue links
Preview and test in Crittiks
- Upload your export files in Settings › Migration and choose Read my files.
- Review the proposed record types, field mappings, owners and stages. Resolve warnings and save any changes.
- Choose Test with 25 of each. Inspect the imported sample in the relevant customer, Sales or Projects screens.
- Choose Undo the test if the result needs correcting. When it looks right, choose Import everything and review the confirmation.
- Read the final report and check representative records, their relationships and record counts.
After the import
The run’s report shows any records that need attention. Undo is available for 30 days; records edited or linked since the import may be kept and listed instead of being overwritten.
Sprints and versions stay in Jira.