Frequently asked questions for OSLC Connect for Jira Data Center customers planning their migration to Jira Cloud.
We know that many of you are existing OSLC Connect for Jira Data Center customers who are concerned about migrating to Jira Cloud. Your OSLC links connect engineering data across Jira, IBM ELM, Siemens Polarion, and they support compliance work that can’t tolerate gaps.
Rest assured, the SodiusWillert team is here to support you on your migration journey. We have assembled a short list of Frequently Asked Questions, to help build your confidence in SodiusWillert and OSLC Connect as part of your Jira Cloud journey.
Does SodiusWillert support migrating OSLC Connect data from Jira Data Center to Jira Cloud?
Yes. We are supporting the migration of critical links from Jira Data Center to Jira Cloud. This includes both the update of data in Jira Cloud as well as your Friended OSLC tools such as IBM ELM, and Siemens Polarion.
What tools are required to perform this migration?
We are letting the Atlassian Jira Cloud Migration Assistant (JCMA) to handle a significant part of the migration of link data from Data Center to Cloud. SodiusWillert provides additional migration tooling to complete the link redirections and tool-specific updates needed.
These are command-line tools that allow you to configure migrations for a single project or for the whole repository. There is a common tool for data migrated from Jira Cloud, and optional tools for each connected OSLC repository.
Every environment is a little different. Please create a support ticket for your migration (Go to Support Portal ↗), so we review your specific scenario and advise on each one individually.
What are the fees for the migration tools?
We have no intention of charging for the standard migration tooling. We will review your environment and provide the appropriate tools to any existing Data Center customer, at no charge.
If you have additional needs beyond a standard migration (rare), or would like priority/premium support during your migration window, we can put together a brief Statement Of Work (SOW) on a case-by-case basis to address your needs.
Is the installation for OSLC Connect for Jira Cloud different than Data Center?
Yes. The deployment for OSLC Connect for Jira Cloud involves more steps than the deployment of OSLC Connect for Jira Data Center. Like Data Center, it includes an app from the Atlassian Marketplace (in this case a Forge app), but Jira Cloud’s extension model doesn’t support the APIs OSLC requires on its own. To bridge that gap, OSLC Connect for Jira Cloud also requires a Broker application, hosted in your own environment.
We recommend reviewing the Installation Guide for OSLC Connect for Jira Cloud for full details before you begin.
Do my existing licenses also work on Jira Cloud?
Your current OSLC Connect license, obtained through the Atlassian Marketplace, is valid only for your Data Center deployment.
To use OSLC Connect for Jira Cloud, you will need a new license from SodiusWillert to enable the Cloud Broker application. You can request on through our Support Portal ↗.
Are there any “dual licensing” options that allow a team to migrate incrementally?
Yes. Working directly with SodiusWillert, we can provide a license agreement and license keys that support OSLC Connect on both Jira Data Center and Jira Cloud simultaneously. This is valuable for teams running an incremental migrations.
If you’d like to pursue this option, please contact SodiusWillert or raise a support request via our Support Portal ↗ ahead of your upcoming license renewal.
Useful links: