Migration is available for versions 3.2.0 (Data Center)/2.0.9 (Server) and later.
We highly recommend that you first move to a test cloud instance.
The migration service is in early access. To enable it, please write to us at email@example.com. Be sure to include the URL-address of your Jira Cloud instance.
- Install/upgrade the Timeline to version 3.1.6 (Data Center)/2.0.9 (Server) or higher.
- Install the "Timeline for Jira" in your new cloud instance.
- Enable the migration feature option by writing to us at firstname.lastname@example.org.
- Update Cloud Migration Assistant to the latest up-to-date version.
- Make sure you have admin rights for your cloud instance.
Very detailed information on how to migrate your data from the server version of Jira to the cloud version is described here.
I will give you the short version:
Go to “Migration to Cloud". System → IMPORT AND EXPORT → Migrate to Cloud
Assess “Timeline for Jira" as Needed in Cloud.
Connect your cloud instance to your server instance. Make sure you are logged in as a user who has admin rights to the cloud instance.
Create a new migration. Specify the address of your server jira, from which the data will be transferred.
Select the necessary migration options. The last one is important for us, the application migration option. The timeline supports both complete and partial migration. In other words, if additional data suddenly appears in the server version that must be transferred, you must repeat the process, select the application migration option, and skip the remaining options.
It is important for the timeline that all custom fields that are used are transferred.
If they are not there, the timeline will be migrated, but after the migration you will need to select new field names.
In the last status, the migration assistant offers to check if there are any errors. If they are not there, feel free to start the process.
After a successful process, all timeline data will appear in your cloud instance. When checking whether everything is in place, log in with the same user that was authorized in the server version of the jira, and if it is not there, then any administrator of the jira.