Aha! Roadmaps | Migrate from Jira Server to Jira Cloud

Atlassian plans to end support for Jira Server on February 15, 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 that 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.

❗️Talk to your Atlassian account manager before proceeding with this migration. You will need their help to retain links to integrated records.❗️

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. Atlassian has created a Jira Cloud Migration Assistant, but that solution will assign new Jira record IDs and break existing links between your Aha! Roadmaps and Jira records.

❗️Note: Your team must re-link Aha! Roadmaps and Jira records if you use the Jira Cloud Migration Assistant.❗️

We recommend the following steps:

  • Review this article.

  • Select a migration tool. If possible, use a tool that allows you to migrate your Jira issues with their existing issue IDs 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.

  • If the migration created new record IDs, re-link existing Aha! Roadmaps and Jira records, either manually or through the API.

  • In Aha! Roadmaps, replace the webhook in your Jira integration configuration.


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.

  • Password type: Select API token.

  • Validate certificate: Check this box.

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.


Unless you have worked directly with Atlassian to avoid it, the migration from Jira Server to Jira Cloud will assign new Jira issue type IDs to your records — and thus break the links to Aha! Roadmaps records. There are three ways your team can resolve this problem:

If you have a small number of Jira records, open each one in Aha! Roadmaps and manually link it to its counterpart in Jira Cloud. To do this:

Option 2: Use the Aha! REST API

Ask your development team to re-link records using the Aha! API.

Your Aha! account stores links to integrations in something we call integration_fields. There are two primary pieces of data that are required to properly map a record in Aha! Roadmaps to a record in Jira:

  • The issue type

  • The issue/record ID

These allow your Aha! account to map the records appropriately based on your mapping configurations.

Your team will need to write a script to copy over the integration_fields from the old Jira Server integration to the new Jira Cloud integration. The script updates one record at a time, and uses our API to retrieve and update the integration_fields values.

  1. Get a specific feature (use this to load the integration_fields for a single record)

  2. Create integration fields for a feature (use this to add new integration_fields back to the same record)

As part of this migration, you will also need to update the url and display_link fields. These fields are used to show the URLs within your Aha! account.

Option 3: Delete and re-import

Choose either Aha! Roadmaps or Jira as a source of truth. Delete the formerly linked records from one tool and re-import them from the other. This will create new records and new record links between your Aha! account and Jira Cloud.

Note: Before you delete records in one tool, make sure all of them exist in the tool you intend to re-import from.

  • Consider what data that is only stored in one system. For example, you may have 100 custom fields in Jira and only bring 20 of those into your Aha! account. In that case, it may make more sense to delete from Aha! Roadmaps and reimport from Jira.

  • Historical comments are not imported from Jira, so if you delete from Aha! Roadmaps and reimport from Jira, you will lose visibility into those comments.

For example:

  • Delete records in Jira that have the broken links, and then re-send those records from Aha! Roadmaps to Jira Cloud (e.g. you can send records in bulk).

  • Delete records in your Aha! account that have the broken links, and then import the records from Jira (e.g. using the steps to import data from Jira).


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.


Consider Aha! Develop

If you are looking for an agile develop tool to replace Jira Server you may be interested in Aha! Develop. We created Aha! Develop as a way to bring engineering teams into your Aha! account for a unified product development environment — so that you can connect work to your product roadmap and streamline delivery without an external integration.

Aha! Develop works with teams who follow scrum, kanban, SAFe, or a hybrid development methodology. Both product and development teams share the same Aha! records, but retain their own unique workflows.

The migration process from Jira Server to Aha! Develop is refreshingly simple. If you are curious, please start a trial or schedule a live product demo.


Frequently asked questions

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

No. As of May 2023, 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