Remote License Migration

This article guides you through the steps to take for the migration of a synchronization making use of a remote license.

Prerequisites

• You are synchronizing to another instance which has a remote license.

  • You are moving to Jira cloud
    or

  • Your partner is moving to Jira cloud

• There are no errors in the troubleshooting tab of the configuration. If you do, please solve these first.

Migration Steps

Use case 1: 

1. You (the instance with the remote license installed) are moving to cloud

2. The partner instance is on server/DC

Please follow the steps described here to migrate to cloud: Server (with Backbone) to Server → Cloud (with Backbone) to Server
Important: you need a new remote license file for cloud, please reach out to help@k15t.com.

Use case 2: 

1. You (the instance with the remote license installed) are moving to cloud

2. The partner instance is on cloud

Please follow the steps described here to migrate to cloud: Server to Cloud → Cloud to Cloud (you can skip step 4.2)
Important: you need a new remote license file for cloud, please reach out to help@k15t.com

Use case 3: 

1. You (the instance with the remote license installed) are staying on server/DC

2. The partner instance is moving to cloud

Please follow the steps described here to migrate to cloud: Server to Server (with Backbone)→ Cloud to Server (with Backbone)
Important: be aware that in the article (prerequisites) "you" is referring to the instance moving to cloud. 

Use case 4: 

1. You (the instance with the remote license installed) are staying on Cloud

2. The partner instance is moving to Cloud

Please reach out to our support at help@k15t.com to guide you through the migration.

Still Unclear? Reach Out to Us

If you need help with any of these migration steps, reach out to us via help@k15t.com.