Migrate from Jira to OpenProject — without losing data, history, or momentum
Stop paying rising per-seat Atlassian fees for a tool your team has outgrown. We move your projects, issues, and history to self-hosted, open-source OpenProject — fully validated before you switch off Jira.
Get a Free Migration AssessmentWhy now: Jira Data Center ends on 28 March 2029
Atlassian has set an end-of-life date for Jira Data Center. After 28 March 2029 Data Center subscriptions and Marketplace apps expire and, according to Atlassian, instances turn read-only with no further support or security fixes; extended maintenance beyond that date is offered only by exception. Sales to new customers already ended on 30 March 2026, and existing customers can no longer expand after 30 March 2028. Jira Server already ended in February 2024.
For a self-hosted team without such an exception that means one of two migrations — into Atlassian's cloud, or out to a platform you run yourself. A migration planned two years ahead is a project; one started in the last quarter is an emergency.
Why teams are reconsidering Jira
Rising costs
Per-seat Atlassian pricing keeps climbing as your team grows, with little control over the roadmap.
Data ownership
OpenProject is self-hosted: your project data, attachments, and history stay on infrastructure you control.
No vendor lock-in
Open-source core, transparent licensing, and no forced feature paywalls down the line.
All-in-one PM
Agile boards, Gantt charts, time tracking, budgeting, and wikis in one tool instead of a plugin sprawl.
What we migrate
Projects & issues
Epics, stories, tasks, bugs, and sub-tasks mapped to OpenProject work packages.
Workflows & statuses
Statuses and types come across directly; the transitions between them and per-role rules are rebuilt by hand in OpenProject's workflow engine.
Comments & history
Full activity history and comment threads preserved, with original authors and timestamps.
Attachments
Files, screenshots, and documents carried over and linked to the correct work package.
Custom fields
Custom fields, labels, and components mapped to OpenProject equivalents.
Users & permissions
Accounts, roles, and group permissions recreated so access control carries over cleanly.
Sprints & boards
Sprint assignments and Scrum/Kanban boards reconstructed in OpenProject's backlog and board views — not yet covered by the official importer, so scripted by us.
Time tracking
Logged work and estimates migrated so historical reporting stays intact.
The official importer, and where we come in
OpenProject now ships its own Jira Migrator, in beta since OpenProject 17.4 (May 2026). We use it where it is good, and do the rest ourselves. Being honest about the split is the point — if your instance only needs what the importer already does, you may not need us at all.
| Part of the migration | Official Jira Migrator (beta) | Our work |
|---|---|---|
| Projects, issues, descriptions | Yes | Mapping review, identifier strategy |
| History, comments, attachments | Yes | Volume testing, validation against the source |
| Users and groups | Yes | LDAP/SSO alignment, de-duplication |
| Statuses and types | Yes | — |
| Custom fields | A subset | The rest, mapped or migrated to equivalents |
| Issue relations (blocks, relates, epic links) | Not yet | Scripted via the Jira REST API |
| Sprint assignments, boards | Not yet | Rebuilt in backlogs and boards |
| Workflows, permissions, schemes | Planned for later | Rebuilt from your Jira configuration |
| Jira Cloud as the source | Not supported | Migrated through the REST API / Cloud export |
| Jira versions | Server / Data Center 10.x and 11.x | Older versions upgraded or exported first |
Importer scope as published by OpenProject, May 2026; it is still being extended release by release, and we re-check it at the start of every engagement.
Our migration process
- Assessment — we audit your Jira instance: projects, custom fields, plugins in use, and data volume, then scope the migration.
- Test migration — a full trial run into a staging OpenProject instance so your team can review the result before anything is final.
- Gap review with your team — walk through the staging instance together and adjust field mappings or workflows as needed.
- Full migration — the production cutover, run during a scheduled maintenance window to minimize disruption.
- Validation — record counts, spot checks, and history verification against the original Jira data.
- Team onboarding — a short training session so your team is productive in OpenProject from day one.
Jira vs. OpenProject at a glance
| Aspect | Jira | OpenProject |
|---|---|---|
| Hosting | Cloud; Data Center self-hosting ends 28 March 2029 | Self-hosted or managed — your choice, with no end date |
| Pricing model | Per-seat, increases with team size | Open-source core; paid tiers optional |
| Data control | Stored on Atlassian's infrastructure | Stored on your own infrastructure |
| Gantt & roadmaps | Requires paid add-ons | Built in |
| Time & budget tracking | Requires paid add-ons | Built in |
| Customization | Marketplace plugins | Open-source, self-hostable extensions |
Frequently asked questions
When does Jira Data Center stop working?
Atlassian has set its end of life for 28 March 2029. After that, Data Center licences and Marketplace apps expire and Atlassian says instances become read-only, with no further support or security fixes; extended maintenance is offered only to certain customers by exception (Atlassian’s end-of-life page).
Doesn't OpenProject have its own Jira importer?
Yes — the Jira Migrator, in beta since OpenProject 17.4. It covers projects, issues, history, comments, attachments, users, groups, statuses, types and some custom fields from Server/Data Center 10.x–11.x. Relations, sprints, workflows, permissions and Jira Cloud are not covered yet; see the table above for what that leaves.
Can you migrate from Jira Cloud?
Yes, though not with the official importer, which supports Server/Data Center only. Cloud migrations go through the Jira REST API or a Cloud export, mapped into OpenProject with our own scripts.
How long does it take?
Data volume and customisation decide it, not team size. A small instance with standard workflows is typically a matter of days; a large one with many custom fields, plugins and years of attachments takes weeks — most of it test migration and validation, not the cutover.
Will Jira be down during the migration?
Only for the final cutover, in a scheduled window. Every trial run goes into a staging OpenProject while your team keeps working in Jira.
What do you need from us to scope it?
The Jira version and deployment type (Server, Data Center or Cloud), roughly how many projects, issues and users, the list of installed Marketplace apps, and which custom fields and workflows actually matter to your team.