Issue Summary

Currently, during migrations, when an organization has a mismatched scope (e.g., a non-vortex organization with org-scoped teams), the migration process respects the organization's vortex status rather than the team's scope. This leads to the creation of duplicate teams in the target site for org-scoped teams. 

Steps to Reproduce

1. Run C2C migration.
2. The team fields are duplicated.

Expected Results

1. Team scope is respected during migration

• • When migrating teams, the migration logic uses the team’s own scope mode (site-scoped / org-scoped) rather than the organisation’s vortex status.

• • For org-scoped teams, if an equivalent team already exists in the target site, that team is reused/linked instead of creating a new duplicate.

1. No duplicate teams created in target sites

• • Running migrations (including repeated or incremental migrations) does not create additional duplicate teams for the same underlying team.

• • Existing teams remain stable and are not fragmented across multiple team records.

1. Cleaner post‑migration state

• • After migration:

• • • Teams used on Jira boards and across products correctly reference the intended single team.

• • • Customers do not need to perform large-scale manual cleanup of duplicate teams.

Actual Results

• Data Duplication: Creates redundant team entries, leading to clutter and potential confusion.

• Manual Clean-up: Requires manual identification and deletion of duplicate teams, increasing administrative overhead.

• Migration Inefficiency: Adds complexity and post-migration tasks to the team migration process.

Workaround

• Self-service cleanup: The customer can delete duplicate teams directly if they can identify them (especially those causing issues on Jira boards).

• Assisted cleanup: If the customer cannot identify duplicates, Atlassian support can provide a list of duplicate teams for them to confirm, and then clean them up.

• Long-term: Ensure teams and org are scope aligned via the UI https://admin.atlassian.com/o/<orgid>/team-site-assignment , which eliminates the root cause entirely.