Moving from Jira to Redmine is mostly preparation: knowing what you have, deciding what to keep and checking the result with your team. This checklist walks you through a migration before, during and after the switch, whether you do it yourself or with us.
Prefer to hand it over? See our Jira migration service: we migrate your data to your own server, to a server managed by us, or to RedmineUP Cloud.
Why teams are moving now
Atlassian is retiring Jira Data Center. New Data Center licenses have not been sold since March 30, 2026, existing customers can renew or add users only until March 30, 2028, and on March 28, 2029 all Data Center subscriptions and their Marketplace apps expire. Jira Server support already ended in 2024. Read the full timeline and your options in Jira Data Center alternatives.
Jira to Redmine migration checklist
1. Before you start
- Take inventory. Count users, projects, issues and the size of attachments. Note your Jira version (Data Center, Server or Cloud).
- List your customizations. Custom fields, workflows, issue types, permission schemes, automation rules and dashboards.
- List Marketplace apps and integrations. Write down what each app does, who uses it and which Redmine feature or plugin could replace it. Include integrations such as Git, CI and chat.
- Clean up. Archive old projects, close stale issues and remove unused custom fields, so you do not migrate clutter.
- Decide where Redmine will run. Your own server, your server managed by us or RedmineUP Cloud. See the delivery options.
- Make a backup. See "Back up your Jira data" below.
2. Run a test migration
- Pick one or two real projects. Choose projects with typical issues, attachments and custom fields.
- Migrate them into a test Redmine. Use a free RedmineUP trial, or ask us to move the projects into it.
- Check the result with your team. Compare issue counts, statuses, authors, comments, attachments and custom fields with Jira.
- Write down the gaps. Anything that did not transfer or needs a different approach goes on the list for the full migration.
3. Run the full migration
- Agree on the mapping. Issue types to trackers, Jira statuses and priorities to Redmine ones, project roles to Redmine roles (see the mapping table below).
- Freeze Jira for the final move. Pick a quiet window and ask the team not to change issues in Jira while the data is moved.
- Migrate all agreed data. Projects, issues, comments, attachments, users and the rest of the list below.
- Set up workflows, roles and plugins. Recreate the boards, service desk and other tools your team relies on.
4. Go live
- Verify the result. Spot-check key projects and compare issue counts with Jira.
- Check permissions and notifications. Make sure each team sees only its projects and that email notifications work.
- Reconnect integrations. Point Git, CI and chat tools at Redmine.
- Train the team. Give people a short walkthrough of boards, filters and time tracking.
- Keep Jira read-only for a while. Leave it available for reference, then switch it off once the team has moved.
How Jira concepts map to Redmine
| In Jira | In Redmine |
|---|---|
| Project | Project |
| Issue type (Bug, Task, Story) | Tracker |
| Status | Status, with workflow per tracker and role |
| Priority | Priority |
| Epic, sub-task | Parent task and subtasks |
| Component | Issue category |
| Fix version | Version |
| Sprint, board | Agile plugin boards and sprints |
| Issue link | Issue relation (related, blocks, duplicates) |
| Project role, group | Role, group |
| Worklog | Time entry |
| Confluence space | Project wiki |
What we migrate from Jira
| Data | What is included |
|---|---|
| Projects | Project structure, names and descriptions |
| Issues | Summary, description, status, priority, assignee, issue type and dates |
| Versions | Releases and fix versions |
| Custom fields | Field definitions and values, mapped to Redmine custom fields |
| Comments | Full comment history on each issue |
| Attachments | Files attached to issues |
| User accounts | Users, so every issue and comment keeps its author |
| Groups and roles | Groups and project roles, mapped to Redmine permissions |
| Time entries | Logged work on issues |
What needs a separate decision
Some Jira data has no direct equivalent in Redmine or depends on third-party apps. Boards and saved filters, dashboards, complex workflows, Confluence pages and data from Marketplace apps are reviewed during the migration plan: we either recreate them with RedmineUP plugins or agree on how to handle them before the move.
Back up your Jira data
Make a full backup of your Jira so nothing is lost and the migration works from a consistent copy.
- Jira Data Center or Server: back up the Jira database with your database tools and copy the attachments folder from your Jira home directory. See Atlassian's guide Backing up data.
- Jira Cloud: create a backup in Settings → System → Backup manager, including attachments, and download the file.
Not sure what to export? We will tell you exactly what we need when we prepare your migration plan.
Want us to do it for you?
We migrate Jira projects, issues, comments and attachments to Redmine and set everything up. See the Jira migration service or request a free migration plan.