Merge migrated Opsgenie teams with Atlassian teams
When you migrate from Opsgenie to Jira Service Management, duplicate teams may be created if a team with the same name already exists in your Atlassian organization. This duplication can cause confusion in team assignments, tagging, and management.
After completing your migration, you can use the Merge teams tool to merge your migrated Opsgenie teams with existing Atlassian teams.
You must be an app admin, operations global admin, or organization admin to merge teams. Only organization admins can merge managed teams with migrated Opsgenie teams. Read more about managed teams.
Once a merging is completed, the Opsgenie team and all its configurations are permanently deleted and cannot be recovered.
Merging only works between a migrated Opsgenie team and an Atlassian team. You can’t merge two migrated Opsgenie teams.
Merge teams
Before merging a migrated Opsgenie team:
Make sure your migration to Jira Service Management is completed.
Review Teams after migration to understand how Opsgenie teams are affected after migration.
Identify which teams you wish to merge and communicate with your team members about upcoming changes.
Once you complete your migration:
In Jira Service Management, go to Operations > General configuration.
Select Merge team.
In the search field, find the Migrated Opsgenie team that you want to merge.
Select the Atlassian team to merge with the migrated Opsgenie team.
Set the Final name of the team.
Select Confirm.
Repeat these steps for any additional teams you want to merge.
When finished, select the checkbox acknowledging the merge consequences, then select Merge.
Review the confirmation message and details of the teams being merged. This action can’t be undone.
Select Confirm to complete the merge.
After merging, you can review the changes in Operations > General configuration > Audit logs.
What happens during merge?
During a merge the target Atlassian team’s Operations configurations are replaced by the source Opsgenie team’s configurations. Meanwhile, target team’s platform information remains as is.
The final team includes all members from both the source and target teams. Operations configurations, such as on-call schedules and integrations, are taken from the source team. Other team information, including activity history, linked work items, team connections and mentions, team links, about section, description, and header image, remains from the target team and won’t be merged with data from the source team.
Once the merge is complete, the source team is permanently deleted.
Team data | What happens after merge? |
|---|---|
Team members | Combined from both source and target teams |
Operations configurations (On-call schedules, integrations, policies, heartbeats…etc.) | Replaced with configurations and data from the source team. |
Atlassian platform data and team profile (activity, linked work items, team connections and mentions, team description, header image…etc.) | Retained from the target team |
Source team | Permanently deleted after the merge |
Managed Atlassian teams
Managed team is a type of Atlassian team where its members are managed by an external source of truth (like Okta, or OneConnect). Read more about managed teams.
If you want to merge a migrated Opsgenie team with a managed team, both teams must have exactly the same members, and the member count must match.
If there is any mismatch, the merge won’t be allowed.
After the merge, the managed team’s name will be used as the final team name.
Changes to the Team APIs
Once merging is complete, your legacy Opsgenie Team Update and Delete APIs will stop working. Instead, you can start using Platform Team APIs for the same purpose.
Was this helpful?