How the migration will affect your Atlassian apps

Every Atlassian App works a little differently with Teams. Here’s what you need to know for each App you use, so there are no surprises during your migration.

Managed Teams connected to a Group will be automatically assigned

For more information on Managed Teams, see here.

If your Managed Team is connected to a Group, it will automatically be assigned to the same site as that Group - no extra steps needed.
If your Managed Team is connected to Workday, you’ll need to manually assign that Team to a site during the migration.

Teams are automatically copied across sites in Jira Service Management

To help you avoid extra work in complex Jira Service Management setups, we have made it easier to keep your Teams and their connections up to date across multiple sites.

If you assign a Jira Service Management (JSM) Team to a site, and that JSM Team is already being used in other JSM sites:

Your Team and its members will be automatically copied to every site where it’s already in use.
All connections to that Team such as schedules, alerts, and other JSM objects will be updated in those sites too.

You’ll see a helpful note about this in the migration tool when you assign a JSM Team that’s used in multiple sites.

Automations with JSM may be impacted

We recommend that you double check any automations you have set up with JSMOps Teams. To ensure minimal disruption to your automations.

Ensure your Team belongs to the site or instance of the product where the automation is run.
If it does not, create a copy of the Team in the sites or products you need the automation, and set that automation up for that site.

Copy Teams over to or from sandbox sites before migration

Today, your sandbox and production sites share the same copy of a Team. When you assign a Team to a specific site (production or sandbox), it will only be available in that site and will no longer appear in the other sites.

In order to make sure you have the teams you need in the desired sites, we recommend the following:

	Instruction	Example
1	Before you assign the Team to a site, create a copy of that Team in other sites where you need it. We suggest using an identifiable prefix or a unique header image to distinguish each copy of the Team.	You want to use `Team A` in both`engineering.vitafleet.net` and `engineering-sandbox.vitafleet.net`. Create a new copy of the Team in `engineering-sandbox.vitafleet.net` . Name it `[sandbox] Team A` for easy identification (you can rename it to `Team A` after when you’re done with assigning the Teams to a site).
2	Wherever required, update work and references to point to the new copy of the Team. For Jira issues, use the bulk update functionality to update the Team field efficiently.	Update work that needs to be connected to `engineering-sandbox.vitafleet.net`. For any Jira issues that need to be connected to the new copy, bulk update them and assign them to `[sandbox] Team A`.
3	Assign each Team copy to it’s respective site using the Team assignment panel. If you have any references of the Team in other sites, they will no longer appear (see references to the Team). You can change the team assignment as needed during the migration window.	In the team assignment panel: Assign `Team A` to `engineering.vitafleet.net` Assign `[sandbox] Team A` to `engineering-sandbox.vitafleet.net.`
4	Once assigned, each Team will only be visible in its assigned site.	Rename `[sandbox] Team A` to `Team A` You now have a copy of `Team A` in both `engineering.vitafleet.net` and `engineering-sandbox.vitafleet.net`. Note: These are not the same copies and may diverge.

This approach ensures you don’t lose access to important Teams in your sandboxes or production environments during the migration.

References to the Team will no longer appear in sites it’s not assigned to

The original site is where your Team was first set up (the "source site"). The new site is where you’re now assigning your Team (the "target site").

When you make this change, your Team and its connections (like mentions, schedules, or permissions) will move to the new site. The Team will no longer be visible or available in the original site, and any references to it there may stop working.

	Product	What happens to old references of the Team after assigning it to a different site? My Team was also used in `engineering.vitafleet.net`. I’ve assigned it to `marketing.vitafleet.net` as this is where it’s used the most. What happens to any links to my Team `engineering.vitafleet.net` after?
1	Jira	Atlassian Team field You will no longer be able to assign Jira work items to this Team. Old references to the Team will still show up but you will not be able to view the Team profile page as the Team no longer exists in this site. JQL queries for this Team will no longer work.
2	Jira	Atlassian Teams in Jira Plans You will no longer be able to assign items to this Team. All references to the Team (including gadgets and capacity planning) will no longer show up in the site.
3	Jira Service Management	There should be no impact as your Team will be copied to all sites that have used that Team before. However, please double check if you are using automations with Jira Service Management Teams and ensure you set these up in multiple sites if needed. Learn more about the behaviour for Jira Service Management’s Operations Teams.
4	Confluence	Team mentions in Confluence Existing Team mentions will continue to appear. However, since the Team no longer exists on the site, users won’t be able to see the Team name or visit its profile page. This will look the same as a smart link (row 7).
5	Atlassian Projects	You will no longer be able to assign Atlassian Projects to this Team. Old references to the Team in Atlassian Projects will be removed. If you have private projects where you granted access via Teams, those permissions will still be respected.
6	Atlassian Goals	You will no longer be able to assign Atlassian Goals to this Team. Old references to the Team in Atlassian Goals will be removed.
7	Platform experiences	Team smart links Existing Team smart links continue to appear. However, since the Team no longer exists on the site, users won’t be able to see the Team name or access the Team profile. Instead, the link will show the Team’s old URL. Team mentions Existing Team mentions will continue to appear. However, since the Team no longer exists on the site, users won’t be able to see the Team name or visit its profile page. This will look the same as a smart link (row 7). Team automations We are building automation triggers called ‘user added to Team' and ‘user removed from Team’ - this will be released October 2025. To avoid disruption, we recommend you only implement these triggers after assigning all your Teams to a site. If you are using other automations with Teams such as using the `teamId` in JSON, depending on the scope of the automation rule, these may not work if the Team is assigned to a site that is different to the automation rule. Please ensure you copy this Team to different sites and set up the automation rules as needed within the required scopes.

Was this helpful?

It wasn't accurateIt wasn't clearIt wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community