Scoped Migration of Tempo Accounts and Teams

When you migrate from Data Center to Cloud using the Jira Cloud Migration Assistant (JCMA), you select which Jira spaces to migrate.

By default, Tempo migrates all Accounts and Teams from your Data Center instance, regardless of which spaces you select in JCMA.

With scoped migration, Tempo migrates only the Accounts and Teams associated with the specific Jira spaces included in the current migration batch.

Scoped migration is useful, for example, when different business units share a Jira Data Center instance but are migrating to separate Cloud sites. It helps keep each Cloud site limited to the Accounts, Teams, and team members used by the business unit migrating to that site.

Scoped migration is optional. If you are migrating your entire Data Center instance to a single Cloud site and want all Accounts and Teams to migrate, you do not need to enable it.

Scoped migration is not enabled by default. Contact Tempo Support before you start your migration to enable it for your Cloud site.

Understanding migration scenarios:

When splitting one Data Center instance into multiple Cloud sites, scoped migration helps keep each Cloud site limited to the Accounts and Teams associated with the spaces migrated to that site.
When migrating one Data Center instance to a single Cloud site in waves, each wave is independent. Tempo migrates only the Accounts and Teams associated with the spaces selected for that specific wave. Data from previous waves is not re-evaluated or included in subsequent batches.

How scoped migration works

With scoped migration enabled, an Account or Team is migrated when it is associated with the Jira spaces included in the migration.

Teams

A Team is migrated if at least one of the following is true:

The Team is linked to a space that you selected for migration.
The Team is set in the Team field on a work item in a selected space.
The Team is used in a qualifying plan that is being migrated. A qualifying plan is any Capacity Planner allocation whose plan item (the issue or project itself) belongs to a selected project.

Tempo does not automatically link Teams to Jira spaces. Most Teams in Data Center are not linked to a space unless you use Capacity Planner.

If a Team is not linked to a selected space, is not set on a work item in a selected space, and is not used in a qualifying migrated plan, it is not migrated, even if it has active members.

You cannot add an unused Team to the migration by simply listing it. Link the Team to a space included in the migration, or recreate the Team in Cloud after migration.

Accounts

An Account is migrated if at least one of the following is true:

The Account is linked to a space that you selected for migration.
The Account is set in the Account field on a work item in a selected space.

This also applies to global Accounts. A global Account is migrated automatically when a work item in a selected space uses it.

If you need to migrate a global Account that is not used by any work item in your selected spaces, you can provide Tempo Support with a list of those Accounts before migration. See Provide a list of global Accounts.

The Account list applies only to global Accounts. A non-global Account that is not linked to a selected space and is not used on a work item is not migrated. Link it to a selected space or recreate it in Cloud after migration.

What happens to links, work items and worklogs?

Links

Links between Accounts or Teams and Jira spaces are migrated as they are configured in Data Center.

You do not need to recreate those links in Cloud.

Work item fields

Account and Team field values are preserved on migrated work items.

Because an Account or Team used by a migrated work item is included in the migration, the corresponding field remains populated after migration.

Worklog attributes

If a worklog contains an attribute that references an Account that is not migrated, that attribute value is not included in the migrated worklog.

Team permissions, and memberships

Team permissions, and memberships are migrated only for Teams that are themselves migrated.

Prepare for a scoped migration

Complete the following steps in your Data Center instance before starting the migration in JCMA.

If you are migrating in batches, remember that scoped migration applies only to the current batch. Ensure that all Accounts and Teams required for a specific set of projects are correctly linked before starting that batch's migration.

1. Enable scoped migration

Contact Tempo Support and request that scoped migration of Accounts and Teams be enabled.

Provide the URL of the Cloud site you are migrating to.

If you need to migrate global Accounts that are not otherwise used by your selected spaces, you can also provide a CSV list of those Accounts to Tempo Support. See [Provide a list of global Accounts].

Wait for Tempo Support to confirm that scoped migration is enabled before starting your migration.

2. Link Teams to spaces

Review the Teams you want to migrate and make sure they meet at least one of the migration criteria.

To ensure that a Team is migrated, link it to a Jira space that you plan to migrate.

A Team that is linked only to a board does not meet the space-linking criterion.

3. Link Accounts to spaces

Review the Accounts you want to migrate and make sure they meet at least one of the migration criteria.

To ensure that an Account is migrated, link it to a Jira space that you plan to migrate.

Global Accounts cannot be linked to spaces. To migrate a global Account that is not used by a work item in a selected space, add it to the global Account list described below.

4. Provide a list of Global Accounts

This step is optional.

If you have global Accounts that you want to migrate but that are not used by any work item in your selected spaces, provide a list of those Accounts to Tempo Support before starting the migration.

Create a CSV file containing the global Accounts you want to migrate and attach it to your Support request. No comma is required since the list will consist of a single column, but the file must be saved with .csv file extension to be recognized by our system. The first row is skipped, so be sure to add an “Account Key” header to avoid any issues. For example:

JavaScript

Account Key
ACCOUNT1
ACCOUNT2
ACCOUNT3

You can configure only one global Account list per Cloud site, and that list applies to every migration to the site.

If you are migrating in batches, include all global Accounts required across all batches.

Wait for Tempo Support to confirm that the list has been configured before starting your migration.

The list applies only to global Accounts. A non-global Account cannot be migrated by adding it to this list. Link a non-global Account to a space you are migrating instead.

Migrating in batches

When you migrate projects in multiple batches or waves, scoped migration applies independently to each batch. Only the Accounts and Teams meeting the criteria for the projects currently being migrated will be included.

Batch 1: Space A — Tempo migrates only Accounts and Teams associated with Space A.
Batch 2: Space B — Tempo migrates only Accounts and Teams associated with Space B.

The global Account list applies to every batch for the Cloud site. You can configure only one list per Cloud site, so include every global Account you need across all batches.

What if I want to migrate everything?

You do not need scoped migration if you want all Accounts and Teams from your Data Center instance to migrate.

Without scoped migration, Tempo continues to migrate all Accounts and Teams from the Data Center instance.

With scoped migration enabled, selecting every space does not necessarily migrate every Account and Team. Accounts and Teams that do not meet the migration criteria remain in Data Center.

Before you start the migration

Use this checklist to confirm that your migration is ready:

Tempo Support has enabled scoped migration for your target Cloud site.
The Accounts and Teams you want to migrate are linked to selected spaces or otherwise meet the migration criteria.
Any required global Accounts are included in the list provided to Tempo Support.
You have received confirmation from Tempo Support that the global Account list is configured.
If you are migrating in batches, you have confirmed that all necessary Accounts and Teams are associated with the specific spaces selected for this migration batch.