Cloud Migration FAQ

To ensure a successful migration of Tempo data to the Cloud environment utilizing the Jira Cloud Migration Assistant (JCMA), the following prerequisites must be met:

• Tempo App Version: The Tempo apps installed in the Server/Data Center environment must be version 16.0 or higher.

• Valid Licenses: Active and valid Tempo licenses are required for both the on-premise (Server/Data Center) instance and the target Cloud instance.

• Cloud App Installation and Functionality: The corresponding Tempo apps must be installed within the Cloud environment and verified to be functioning as expected before starting the migration process.

In addition to the minimum requirements, verifying the following aspects is crucial for a successful migration:

• User Migration: Ensure that all relevant users are successfully migrated to the Cloud instance before migrating Tempo data. A complete user migration is essential for maintaining data integrity and proper user access within Tempo.

• Tempo and Project Co-Migration: Always migrate Tempo apps and associated projects together. Migrating these elements in isolation can lead to data inconsistencies and functional issues.

• Time Zone Synchronization: Verify that the time zone settings in both the Server/Data Center and Cloud environments are consistent. Time zone discrepancies can result in incorrect time reporting and scheduling.

• Dynamic Dropdown Custom Fields: If you are using custom fields of the 'Dynamic Dropdown' type, be aware that these are not supported in Tempo Cloud. Before migrating, you must adjust these fields and replace them with static lists or alternative supported field types. Failure to do so may result in data loss or functionality issues related to those custom fields.

The duration of a Tempo Cloud migration is variable and depends on several factors. Consequently, a fixed Estimated Time of Arrival (ETA) cannot be provided. Key factors influencing the migration timeline include:

• Server/Data Center Hardware: The performance and capacity of the hardware hosting the Server/Data Center instance can significantly impact migration speed.

• Network Infrastructure: Network bandwidth and stability between the on-premise and Cloud environments play a crucial role in the rate at which data can be transferred.

• Data Volume: The most significant factor is the volume of Tempo data being migrated, including worklogs, accounts, plans, and associated configurations. Larger datasets naturally require more time to migrate.

Due to these variables, it is recommended to perform a test migration to estimate the duration for your specific environment and data volume. This will provide a more realistic understanding of the time required for the full production migration.

No, this is the expected behavior. While the initial migration process may show as 100% complete, several post-migration synchronization tasks are required before Tempo can fully display your data. A critical task is the automated worklog synchronization, which begins immediately after the migration reaches 100%.

Please be aware that this synchronization process can take a significant amount of time, potentially ranging from hours to days, depending on the volume of worklogs being synced.

Estimated Sync Time: Currently, you can expect the worklog sync to take up to 24 hours per million worklogs. The duration is primarily limited by rate limits imposed by Atlassian and their API restrictions on the Cloud platform.

We recommend monitoring the progress of the synchronization process. While it is running, please refrain from making significant changes to Tempo settings and past data (migrated worklogs) to avoid potential conflicts. Once the worklog synchronization is complete, your worklogs should be visible in Tempo Cloud.

The answer is both yes and no. While it is technically possible to migrate Tempo independently of your Jira projects, doing so will result in a loss of data linkages and may render certain data elements unusable.

Specifically:

• Partial Migration Possible: You can migrate Tempo-specific configurations, such as Teams, Accounts, and other settings, to the Cloud environment.

• Loss of Jira Data Linkage: Any data element within Tempo that relies on a link to Jira project data (e.g., issue keys within worklogs) will lose that connection. This means worklogs may not display correctly or be associated with the correct Jira issues.

Recommendation: For a fully functional and accurate Tempo Cloud instance, it is strongly recommended to always migrate Tempo and the associated Jira projects together. Migrating Tempo in isolation should only be considered if you are aware of the limitations and are primarily interested in migrating configuration data without maintaining historical project data relationships.

If you are experiencing missing data in Tempo Cloud more than 24 hours after the migration process has been marked as complete, we recommend the following:

• Contact Tempo Support: Reach out to Tempo Support as soon as possible to report the issue and request further investigation.

• Provide Instance URL: When contacting support, be sure to provide the URL of your Cloud instance to facilitate the investigation.

The Tempo Support team will be able to analyze your migration logs and identify any potential issues preventing the complete synchronization of your data. They can then provide guidance on resolving the problem and ensuring all your data is available in Tempo Cloud.

Currently, the status and updates for the synchronization process are not directly visible within the Tempo Cloud interface.

To obtain information about the progress of the synchronization, please contact the Tempo Support team. They have access to the necessary tools and logs to monitor the synchronization process and can provide you with the latest updates. The Tempo Support team will keep you informed about the status and any relevant details regarding the synchronization of your data.

During a Jira Cloud migration using JCMA, Jira migrates project permissions. However, Tempo-specific project permissions, such as "work on issues," "view all worklogs," and "view issue hours," are not migrated by JCMA. This is because these permissions are dynamically added by Tempo when the app is installed and are not recognized by JCMA as standard Jira project permissions.

Impact:

• If users' permissions to view worklogs were granted solely through these project permissions, those users will lose the ability to see worklogs after the migration.

Resolution:

After the migration, you will need to manually re-grant these Tempo-specific permissions. Here's how:

1. Project Permissions:

   • Navigate to the Project Settings for the relevant project.

   • Go to the "Permissions" section.

   • Add the necessary users and groups to the following permissions: "Work on Issues," "View All Worklogs," and "View Issue Hours."

2. Team Permissions and Permission Roles:

   • Team Permissions: You can grant worklog viewing permissions on a per-Team basis within each Team's permission tab.

   • Permission Roles: Alternatively, you can use Tempo's Permission Roles for a more centralized approach. Go to Tempo Settings > Permission Roles. Create or modify permission roles with "Full Access" and add the relevant users to those roles. This will grant them permissions across all Teams.

By re-granting these permissions either at the project level, Team level, or through Permission Roles, you can ensure that users have the appropriate access to view worklogs in Tempo Cloud after the migration.

If you observe either of the following scenarios:

• The progress bar for the Tempo migration has not advanced for more than 24 hours.

• It has been 24 hours since the migration was marked as complete, and you are still missing Tempo data (e.g., Worklogs).

Then, it is recommended to:

• Contact Tempo Support: Reach out to Tempo Support for assistance and investigation.

By contacting Tempo Support, you'll allow them to examine the migration's status, identify any underlying issues, and provide guidance on the appropriate next steps without risking the integrity of your data.

At this point, we do not offer migrations between Tempo Cloud instances as Tempo stores data in a database separated from Jira. Therefore, the usual C2C migration will not display data on the destination unless you perform the steps described below.

We have an open task to implement the backup and restore to enable this, but we're unable to provide you with an ETA for when it will be ready. We aim to give customers full access to their data and the ability to create backups of their systems and restore them if necessary, once the feature is out.

That said, some Tempo Platinum Partners do offer Cloud-to-Cloud migration services. Please refer to our Tempo Partner directory here.

In case you would like to try to migrate Tempo worklogs from the first Cloud instance to the second Cloud instance yourself, you will need to do the following:
Irrespective of which migration method you execute, all Jira worklogs will be migrated to the target Cloud instance from the source Cloud instance.
To avoid duplicate worklogs in Jira, all those worklogs need to be deleted with the JIRA REST API before proceeding with the next steps!

1. Export all Tempo worklogs from the first Cloud instance with the Tempo REST API. The reason for this is that all Tempo worklogs reside in a separate database on Cloud, and very limited, anonymized worklog data is synced back to Jira. (Jira has no information about the worklog owner). The only way to export worklogs with the real worklog owner and worklog description is with the Tempo REST API.

2. Remove all worklogs from Jira that were migrated with the issues to the target instance, using the Jira REST API 

3. Import the worklogs that were exported from Tempo to the target Cloud instance with the Tempo REST API, JIRA REST API, or a JIRA native .csv import.

Similar steps will be needed for all other Tempo data like Accounts, Teams, Work Attributes, etc.