Migrating to Jira Cloud

The options for Behave Pro customers migrating from Jira Server or Data Center to Jira Cloud

Alan Parkinson avatar
Written by Alan Parkinson
Updated over a week ago

Behave Pro has always been available in Jira Cloud, and this long history means we a strong and mature offering in Jira Cloud with 100% feature parity when compared to Server and Data Center.

There are a number of different ways you can migrate Behave Pro from Jira Server or Data Center to Jira Cloud, but the deciding factor on which route to take is what features of Behave Pro you are using.
Our support team would be happy to provide advice on migrating (a discussion can be started with the blue widget in the bottom right-hand corner) but to make a decision using this guide or the support team you will need the following information:

  • How many Jira projects do you need to migrate?

  • Do your Jira projects using Behave Pro use the Git integration?

  • Will your Git repository be available in the Cloud at the time of migration?

  • Do you need to migrate any Exploratory Test Session data with your project?

Migration routes

Projects using the Git Integration and the Git repository will be available in the Cloud versions of GitHub, Bitbucket or GitLab

When a project uses Behave Pro's Git integration the data is stored in the Git repository. To migrate these types of projects, firstly migrate the Git repository to the Cloud, and then configure Behave Pro on the Jira project.

During the project setup process configure Behave Pro to connect to the cloud Git repository and Behave Pro will automatically import all the data into the project.

Projects using the Git Integration and but the Git repository will not be available in the Cloud

Due to firewall permissions and other security considerations, it isn't possible for the Jira Cloud version of Behave Pro to interact with the server versions of Bitbucket.

It is still possible to migrate the Behave Pro projects to Jira Cloud but the Git integration will not be available until the repositories are migrated to a Cloud compatible repository hosting solution. Follow the instructions for Projects not using the Git Integration

Projects not using the Git Integration

Note: If you are using the Cloud versions of GitHub, Bitbucket or GitLab at the time of migration it is worth considering migrating to the powerful Git Integration feature as part of your overall cloud migration strategy as it only adds minimal additional work and provides a big productivity gain for teams.

Using Behave Pro's API each project can be exported to a ZIP and then the contents can be unzipped and imported once Behave Pro is enabled for the Jira project. When all the required materials are prepared a project can be migrated in under 5 minutes.

Downloading the ZIP file for a project

The API uses Basic Auth credentials, this will be your Jira username and password or API key if you use SSO. To use the API you will also need the numeric Id of the Jira project and this can be found on the Behave Pro settings page for the project

Now we have our authentication details, you're ready to download the features zip over HTTP using a tool such as wget or curl, or programmatically using your favourite language.

The API endpoint


Where {Jira} is your Jira instances URL and {projectId} is noted from the previous step.

A complete URL could look like this:



$ curl --fail -u {user}:{pass} "https//:{Jira}/rest/cucumber/1.0/project/{projectId}/features?manual=true" --output features.zip


$ wget "https//:{Jira}/rest/cucumber/1.0/project/{projectId}/features?manual=true" --user={user} --password={pass} --auth-no-challenge

Where {user} and {pass} are the username and password noted earlier.

This should successfully download a ZIP containing files with the ".feature" exention. This is all the data for your project and it's ready to be imported to its new home.

Importing feature files into a Behave Pro project

Within Jira Cloud, once the Jira issues have been migrated, navigate to the Jira project settings page of the project being migrated and click on "Behave Pro" in the left navigation menu. You will be shown the Behave Pro settings for your Jira project.

To enable your Behave Pro for the project, click on the toggle button in the right top corner.

You will be redirected to the configuration page as shown in the screenshot below, click "Getting Started" at the bottom.

Next, choose the "classic" workflow as shown below.

That's all for setting up a classic Behave Pro for your Jira project.

This will open your project on Beahve Pro's requirements page. At the top of this page is an import button. First unzip all the feature files from your exported ZIP file and then click the import button. Within the import dialog select all the unzipped feature files. Once the files have successfully uploaded then the migration has been completed for the project.

Reconfiguring Build Tools

If you are using Behave Pro's build tools to export your feature files ordinarily for use, you will need to generate a new configuration. Once you get into Jira Cloud, go to the project settings and into Behave Pro; from here click, "Configure" in the "Export API Key" section.

This will show you what the new username and password for your builds will be, if you select, "Generate Config" it will give you the configuration that can be copy-and-pasted into your project.

Along the top you will have configuration options for all the different frameworks that we support with our build tools. Note that what has changed here is not only the username and password but the server will have as well.

Migrating Exploratory Test Session data

At the present time, there isn't the facility to export and import Exploratory Test Session data from projects or Jira. If this is a blocker to your Cloud migration please start a conversation with the support team so we can discuss your requirements and options.

Frequently Asked Questions (FAQs)

Will scenarios still be linked to Jira issues?

If Jira issues are using the same issues keys after the migration to Jira Cloud as before the migration then all scenarios will be linked to their original issues.

Why can't we use the Jira Cloud migration assistant?

Most of our customers use the Git integration Behave Pro offers. The Cloud migration assistant isn't designed for cross-product usage and doesn't know how to migrate a 3rd party DVCS integration to its Cloud equivalent.

Did this answer your question?