Issue Summary

A better way of handling Atlassian Teams during Server-to-Cloud migration to avoid duplicate Atlassian teams.

If the customer carries out a server-to-cloud migration from the same server site but to two different cloud sites, this will result in the same teams being created twice. 

For example:

•  Server(Jira) has ARJ teams with ids 1,2, and 3.
• Cloud site A has activation id xyz.
• Cloud site B has activation id lmn.
• When the S2C migration is run from server to cloud site A, the following three Atlassian teams are created to represent the ARJ teams (the following are team IDs)
  • xyz-1
  • xyz-2
  • xyz-3
• When the S2C migration is run to from server to cloud site B, three new Atlassian teams are created as follows.
  • lmn-1
  • lmn-2
  • lmn-3
• xyz-1 and lmn-1 are copies of the same ARJ team, so they'll have the same team name.
• The teams are visible throughout the org given that the customer's org is org-scoped.
• So, customers will observe these as duplicate teams.

Workaround

To remove teams in bulk, a REST API endpoint is available. Please review Delete teams from Atlassian Cloud using Postman and REST APIs.