Rovo Data Center Connectors with inactive DC license

[Rebekka Heilmann _viadee_]

Does the Data Center license need to be active for the Jira/Confluence Data Center Rovo connectors to work?

For companies who don't want to migrate their legacy data to Cloud, this could be an ideal setup: While the DC instance remains available in Read Only mode (no active DC license), the Data is accessible via Rovo.

According to Atlassian's Support Rovo, the connection would have issues with an inactive license due to connectivity issues. Does anyone have any experience with this?

Any other experience regarding the connector? Does it work well?

[Viswanathan Ramachandran]

hi @Rebekka Heilmann _viadee_ 

No personal experience. 

But in my opinion the key distinction is between the Cloud and Data Center licences. 

It may continue to work for read/search use cases, but I would not build an archive strategy on that assumption. The connector still depends on the DC instance, its APIs, authentication, and plugin compatibility remaining available and an expired instance receives no support or security updates. 

Please confirm support with Atlassian for your exact versions. 

Strategically, use Rovo as a discovery layer, not as the sole preservation plan and retain an independent archive or backup of the legacy data.

If it helps, see

https://www.atlassian.com/migration/rovo-connectors-data-center

https://support.atlassian.com/organization-administration/docs/connect-jira-data-center-to-teamwork-graph/

https://www.atlassian.com/licensing/data-center-end-of-life#data-center-eol-general-questions

[Rebekka Heilmann _viadee_]

I've never mentioned an archiving strategy to be fair. I see this as a temporary bridge between Cloud and DC while the company is working on the Transformation. 

But: temporary could mean a few years when dual licensing is long expired.

The articles are not helpful as they don't answer my question explicitly.

[Viswanathan Ramachandran]

You’re right, I didn’t answer your question directly. I can't find docs on this.

I'd assume an active DC licence is needed for a supported bridge.

For yours, I’d ask Atlassian to confirm this in writing for your versions.