Aha! Roadmaps | Migrating records or servers

In most cases, once you save your Jira integration configuration in Aha! Roadmaps, you are ready to go — no further configuration needed.

In case you do run into trouble, we have gathered some of the most common issues involved with migrating records (or entire servers!) here, along with recommended solutions.

Often the best place to start in most of these situations is the integration log messages for your configuration. Those messages will help diagnose and solve the problem.

Click any of the following links to skip ahead:

Migrate Jira records


You have an established integration between Aha! Roadmaps and Jira but you need to change Jira servers or your Jira domain. Since the integration is between an Aha! Roadmaps workspace and a Jira project, you are worried that your Jira update will affect the integration.

Read this article if you are attempting to migrate from Jira Server to Jira Cloud.


This can raise a few concerns on the Aha! Roadmaps end due to the tightness of integration between the two applications.

The first concern is that Aha! Roadmaps stores the URL of the Jira issue. This URL will be different after your migration, so clicking on the link to the issue in the user interface won't work. However, this is purely a cosmetic problem. Aha! Roadmaps uses the URL from the integration configuration when communicating with Jira to perform syncing. So links to existing issues will appear to be broken in the UI, but the issues will continue to sync correctly.

The second concern is a bit more complicated. Aha! Roadmaps stores the unique identifier for each linked Jira issue. This identifier is an integer and is not normally visible in the Jira UI. The identifier is necessary because it is possible for the issue key (like APP-123) to be changed. Some methods of moving from one Jira instance to another will change these identifiers and so Aha! Roadmaps will no longer be linked to any issues — even though the issues appear to have the same key in the user interface.


The issue ID is a somewhat hidden field in Jira. The easiest way to find the ID is to open an issue and hover over the Edit option. The status bar on the bottom of your browser will display the URL with the issue ID.

If you know that your Jira migration will cause existing issue IDs to change, the integration will break for any previously linked Aha! Roadmaps record. There are three ways to fix this issue, beginning with the easiest:

  1. Delete all the previously linked features from Aha! Roadmaps and reimport from Jira.

  2. Do the opposite and delete the issues from Jira and resend everything from Aha! Roadmaps.

  3. If you have a very small number of features and issues, you can also manually link each Aha! Roadmaps feature to a Jira issue under the Integrations dropdown in the Overview tab in each individual feature. Note: This option will manually link only features and not requirements.

If you want to update the reference URLs in Aha! Roadmaps, you will need to follow this same process.

Remember, Aha! Roadmaps does not propagate data deletions through the integration. This means if you delete a record in Aha! Roadmaps or in Jira, the associated record would not be deleted in the other tool.


Migrate Aha! Roadmaps records


You have an established integration between Aha! Roadmaps and Jira, but you need to move Aha! Roadmaps records to a new workspace. Since the integration is between an Aha! Roadmaps workspace and a Jira project, you are worried that your Aha! Roadmaps update will affect the integration.


Even if you have all of your Aha! Roadmaps workspaces set up to integrate with projects in Jira, moving Aha! Roadmaps records to another workspace will break the integration link. And if you try to resend records after moving them, you risk creating duplicate records in Jira.


If you want to move Aha! Roadmaps records, you can, but you might need to do some manual work to maintain that integration link.

We cover several specific scenarios related to moving Aha! Roadmaps records in one of our integration guides.

You have three options:

  1. Relink each record manually. Note: Not available for requirements.

  2. Delete the Jira issues and send the Aha! Roadmaps records over to Jira again to recreate the link to new issues.

  3. Delete the Aha! Roadmaps records and import the issues from Jira to Aha! Roadmaps to recreate the link to new records.

The first option maintains all data in both systems but is manual and best suited for a small volume of records. To relink a record, click the More options button next to the Integrations field on the Overview tab, then click Resend all fields.

This will not re-link requirements.

The second option will allow you to recreate the issues in Jira in the correct versions with the click of a button. This is the easiest approach.

The third option requires multiple imports from Jira so that you end up with records correctly grouped — features grouped in the correct releases, for example. If the records in question are currently being developed and it's important for developers to see all of the commenting back and forth, you may wish to keep the Jira issues and reimport them.


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

Suite overview
Aha! Roadmaps
    Account management
      Aha! Ideas
      Aha! Whiteboards
      Aha! Knowledge