Aha! Roadmaps | Migrate from Jira Server to Jira Cloud

Atlassian plans to end support for Jira Server in early 2024. If you are a current Jira Server customer, it is time to start thinking about migrating your account to Jira Cloud.

One part of your migration planning should focus on the integration between Aha! Roadmaps and your Jira Server account. This integration links your product and engineering teams so planned work flows from Aha! Roadmaps to Jira and real-time progress updates flow back to inform your strategic roadmap. If your migration breaks this integration, you will also disrupt the collaboration between those two teams.

In this article, we will walk you through the migration process as it affects your Aha! Roadmaps integration, the changes you need to make to your integration settings, and answers to commonly asked questions.

Click any of the following links to skip ahead:


This migration has more than a few moving parts. If you have not done so already, we suggest that you follow Atlassian's guidance and create a migration plan for you and your team. To avoid breaking the integration between Aha! Roadmaps and Jira, we recommend the following steps:

  • Review this article.

  • Select a migration tool that allows you to migrate your Jira issues with their existing issue and issue type IDs. This will keep existing links between Aha! Roadmaps and Jira records in place.

  • Migrate your account from Jira Server to Jira Cloud.
    Note: This will temporarily disable your Aha! Roadmaps integration.

  • In Aha! Roadmaps, update your Jira integration configuration following the steps listed in this article.

Note: The migration tool you choose must retain the original Jira issue and issue type IDs to avoid breaking your existing record links between your Aha! and Jira accounts.


Update your integration configuration

To adjust your Jira integration configuration, navigate to Settings ⚙️ Workspace, then select the Jira integration or Jira integration template that you want to adjust. You will need to be a workspace owner in Aha! Roadmaps to do this.

On the Configure account step, you need to make three changes:

  • Server URL: Change this to your new Jira Cloud URL.

  • Username: While Jira Server allows you to use a unique username, Jira Cloud requires an email address.
    Note: Your integration will have the same user permissions as the user whose email address you select in this step.

  • Password: While Jira Server allows you to use a password in this field, Jira Cloud requires an API token.

Click Save and continue when you are ready to move on.


Review your mappings

Next, click to the Mappings step of your Jira integration configuration. This is an excellent time to make sure you like your current mappings.

Click Save and continue when you are ready to move on.


Replace the Jira webhook

Finally, click to the Enable step of your Jira integration configuration. You need to set up a new webhook in your Jira Cloud instance that will send updates from Jira Cloud back to Aha! Roadmaps.

Click Enable integration when you are finished.


Frequently asked questions

I use Jira Data Center. Does this migration affect me?

No. As of March 2021, Atlassian has no plans to sunset Data Center products.

The Atlassian migration page offers several migration tools for you to choose one. You must select a tool that will retain the existing record IDs to ensure that links between integrated records will also remain intact.


If you get stuck, please reach out to our Product Success team. Our team is made up entirely of product experts and responds fast.

Aha! Roadmaps
      Aha! Ideas
      Aha! Develop