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:

Overview

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 the Jira Cloud Site Import as your migration tool.

  • 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.

This process is simple, quick, and painless — within minutes after your migration, your integration with Aha! Roadmaps will be up and running just as you left it.

Top

Jira migration pathways

There are three main ways to migrate your Jira Server data to Jira Cloud. All three will move your Jira Server data into your new account, but only one of them will do so without giving your Jira issues new identifiers.

Your Aha! Roadmaps integration relies on Jira issue IDs to retain links between Aha! Roadmaps records and those Jira issues. If you migrate your Jira data in such a way that it receives new IDs, Aha! Roadmaps will assume you have created brand new issues. This will cause any links to existing issues to be broken.

  • The CSV import is the simplest way to migrate your data but it is not recommended for this use case. The import is a fairly manual process so you risk human error. It will create new issues in Jira Cloud for you, removing links to existing integrated Aha! Roadmaps records.

  • The Jira Cloud Migration Assistant, available for Jira or Confluence users, was built by Atlassian for this migration. It lets you choose the data you would like to migrate so that you do not need to migrate your entire Jira Server account to Jira Cloud. But in doing so, it gives your Jira issues new identifiers and breaks links to existing integrated Aha! Roadmaps records. For this reason, we do not recommend that you use the Jira Cloud Migration Assistant.

  • The Jira Cloud Site Import was created to help you back up and restore your Jira account. It can be used to back up your Jira Server account and "restore" it to your new Jira Cloud account. The tool backs up your entire account, but as a back up, it retains your Jira issues' original IDs.

We strongly recommend the Jira Cloud Site Import if you would like to migrate to Jira Cloud without breaking your Aha! Roadmaps integration. If you use this tool, then after a few quick adjustments to your Jira integration configuration in Aha! Roadmaps, your integration will be pointed at your new Jira Cloud instance.

Top

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.

Top

Review your mappings

Next, click to the Mappings step of your Jira integration configuration. While the Jira Cloud Site Import tool should retain all your record and field mappings between Aha! Roadmaps and Jira, this is an excellent time to make sure you like your current mappings.

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

Top

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.

Top

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.

If you use the Jira Cloud Site Import tool, then no — links between Aha! Roadmaps and Jira records will be retained and your integration will function as normal.

Will my record IDs change?

If you use the Jira Cloud Site Import tool, then no. Your Jira issues will retain their same record identifiers, and your integration will function as normal.

Top

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

Aha! Roadmaps
    Strategic roadmaps
    Integrations
      Aha! Ideas
      Aha! Develop
      Announcements
      © 2021 Aha! Labs Inc.All rights reserved