Current Situation

Currently, Customers with an active instance of Jira Service Management Operations, i.e. one with teams configured with Operations, cannot merge their Standalone Opsgenie instance from another Atlassian site. 

This situation covers:

• Customers who have had some teams using Jira Service Management Operations and now need to migrate a Standalone Opsgenie instance
• Customers who need to consolidate/merge multiple Standalone Opsgenie instances into a singular Jira Service Management instance

Suggested Solutions

The Opsgenie to Jira Service Migration tooling should allow customers to specify an additional migration path: populating an existing Jira Service Management Operations instance with the migrated Standalone Opsgenie details.

Current Workarounds

The partial workaround for this requires customers to explicitly delete any Atlassian team that had operations enabled, and request from Atlassian Support to do a de-consolidation and site-to-site migration of their Opsgenie instance. This does NOT allow any existing Operations configuration to be kept, but will allow an Opsgenie instance to be migrated to a particular Jira Service Management instance. This will require all existing configuration in the Jira Service Management Operations instance to be purged and replaced - it does not support any merging of Operations and Opsgenie configuration, and Teams deleted as part of this can't be restored post-migration.

Customers cannot delete and restore Atlassian teams to bypass the purging of the existing Operations instance, as they are tightly coupled - any team with operations configured must be deleted permanently and this workaround is not suitable for customers with extensive Team connections into their Jira and Confluence apps.