Migrating data with 3rd party add-ons

Still need help?

The Atlassian Community is here for you.

Ask the community

Whether you’re scaling your organization, simplifying maintenance for hardware and licensing, or taking an extra step to validate all changes coming into JIRA, we want to ensure there’s a clear path for you to migrate data. That's why we teamed up with two of our Atlassian Verified vendors, Adaptavist and Botron, who each offer an add-on to help you transfer projects, configuration, and the desired accompanied data from one JIRA instance to another. Why two vendors? While both ensure the same goal, they each offer a different approach to get there. Read more to choose the one that works best for your team. 


Promoting changes in JIRA

Whether it's a big change to your workflows or just a new custom field, take it from development through staging to production to make sure it's all checked up. And regret no more.

Adaptavist: Promoting JIRA configuration

Botron: Promoting JIRA configuration



Consolidating JIRA instances

You can never get too much of JIRA, but too many instances might sometimes feel overwhelming. When moving to a single JIRA, don't leave your data behind.

Adaptavist: Consolidating JIRA instances

Botron: Consolidating JIRA instances




Migrating JIRA projects

If your projects are living out of a suitcase, you can at least make sure it's the one with wheels. Move them freely between one JIRA and another.

Adaptavist: Migrating JIRA projects

Botron: Migrating JIRA projects

Last modified on Oct 17, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.