-
Notifications
You must be signed in to change notification settings - Fork 2.9k
[#65583] We have published a dedicated working document on migrating … #20964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
MayaBerd
merged 4 commits into
release/16.6
from
key-result/65583-we-have-published-a-dedicated-working-document-on-migrating-from-jira
Nov 17, 2025
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
101 changes: 101 additions & 0 deletions
101
docs/installation-and-operations/jira-migration/README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,101 @@ | ||
| --- | ||
| sidebar_navigation: | ||
| title: JIRA migration | ||
| priority: 90 | ||
| --- | ||
|
|
||
| # Migrating from JIRA and Confluence to OpenProject | ||
|
|
||
| > [!NOTE] | ||
| > | ||
| > This page is a work in progress. The OpenProject team is actively developing an upcoming JIRA and Confluence migration tool. Information on this page may change as new migration options become available. | ||
| > | ||
| > Last edited on: November 11, 2025. | ||
|
|
||
| ## Overview | ||
|
|
||
| This guide provides an overview of the current options for migrating data from Atlassian JIRA or Confluence to OpenProject. It also describes ongoing community and in-house development efforts for dedicated migration solutions. | ||
|
|
||
| With the [end of life for JIRA Data Center](https://www.openproject.org/blog/jira-alternative-end-of-data-center/), many organizations are evaluating OpenProject as a secure, open-source, and self-hosted alternative for project management and collaboration. | ||
|
|
||
| ## Migration Options | ||
|
|
||
| ### 1. OpenProject migration tool | ||
|
|
||
| OpenProject is developing a solution for migrating from JIRA and Confluence. You can follow the progress of OpenProject's [JIRA migration Stream](https://community.openproject.org/projects/jira-migration) and provide feedback. This tool will simplify data import for JIRA projects, including: | ||
|
|
||
| - Issue types | ||
| - Users and groups | ||
| - Fields and custom fields | ||
| - Attachments | ||
| - Workflows | ||
|
|
||
| > [!IMPORTANT] | ||
| > This feature is under active development and not yet available for production use. | ||
|
|
||
| **Contributing and data donation** | ||
|
|
||
| To support the development of the official migration tool, we are collecting anonymized data samples. This data helps test and validate import capabilities across different JIRA and Confluence configurations. | ||
|
|
||
| > [!TIP] | ||
| > Please reach out to us if you want to donate your data, we will sign an NDA to ensure confidentiality. | ||
|
|
||
| ### 2. API | ||
|
|
||
| Use the [OpenProject REST API](https://www.openproject.org/docs/api) to migrate data programmatically. This option provides full flexibility and supports most OpenProject entities, such as: | ||
|
|
||
| - Work packages | ||
| - Users | ||
| - Comments | ||
| - Attachments | ||
|
|
||
| > [!NOTE] | ||
| > The API-based approach requires technical expertise and scripting or integration development to map JIRA and Confluence data structures to OpenProject. | ||
|
|
||
| ### 3. Excel synchronization | ||
|
|
||
| The [Excel synchronization integration](https://www.openproject.org/docs/system-admin-guide/integrations/excel-synchronization) allows you to import and export tabular data between JIRA, Confluence, and OpenProject using spreadsheets. | ||
| This method is suitable for small- to medium-sized migrations and provides an opportunity to review and clean data manually before import. | ||
|
|
||
| ### 4. Confluence → Markdown → Wiki | ||
|
|
||
| You can migrate Confluence content into OpenProject using Markdown export and manual import: | ||
|
|
||
| 1. Use a Markdown export app such as [Markdown Exporter for Confluence](https://marketplace.atlassian.com/apps/1221351/markdown-exporter-for-confluence). | ||
| 2. Copy and paste the exported Markdown into the OpenProject Wiki module. | ||
| 3. Verify formatting and structure after import. | ||
| 4. Upload attachments manually (these are not included in the Markdown export). | ||
|
|
||
| This approach preserves most layout elements and is recommended for documentation or knowledge base content. | ||
|
|
||
| ### 5. Community-developed JIRA importer | ||
|
|
||
| A community-developed tool, the [OpenProject JIRA Importer](https://github.com/dotnetfactory/openproject-jira-importer) provides additional import capabilities. | ||
| It supports importing JIRA issues into OpenProject and is available as open-source software. | ||
|
|
||
| Refer to the [JIRA migration community development blog article](https://www.openproject.org/blog/jira-migration-community-development/) for background information and usage guidance. | ||
|
|
||
| ## Recommended migration workflow | ||
|
|
||
| ### 1. Preparation | ||
|
|
||
| - Document your existing JIRA and Confluence configuration (projects, issue types, workflows, fields, spaces). | ||
| - Identify which data to migrate and which to archive. | ||
| - Clean up legacy data before starting. | ||
|
|
||
| ### 2. Testing | ||
|
|
||
| - Set up a test instance of OpenProject. | ||
| - Migrate a small subset of data using one of the methods described above. | ||
| - Verify field mappings, attachments, and relationships. | ||
|
|
||
| ### 3. Execution | ||
|
|
||
| - Perform the full migration after successful testing. | ||
| - Validate data integrity after import. | ||
| - Recreate workflows, permissions, and boards in OpenProject as required. | ||
|
|
||
| ### 4. Post-migration | ||
|
|
||
| - Provide training to users. | ||
| - Archive or decommission the legacy systems if applicable. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.