Knowledge Base Articles
Knowledge Base Articles
Breadcrumbs

Cloud-to-Cloud Migrations Tempo Products - Timesheets

Cloud-to-Cloud (C2C) migrations pose unique challenges, especially when dealing with third-party add-ons like Tempo products, such as Timesheets. This document outlines the manual migration process for Tempo worklogs using APIs between Jira Cloud instances. Since Tempo stores its data separately from Jira, standard C2C migrations will not automatically display data in the destination instance without specific actions. Below, we will detail the steps necessary for a successful migration.

Understanding Tempo Cloud Data Storage

Tempo products store data in a separate database from Jira. When migrating, it is crucial to note:

  • Standard C2C Migration Limitations: Worklog data is not automatically transferred due to separate data storage.

  • Future Enhancements: Tempo has planned features for backup and restore processes, though no definitive timeline is available.

  • Third-Party Migration Services: Some Tempo Platinum Partners offer services to assist with these migrations. The Tempo Partner Directory can help locate a suitable partner.

Migration Process

Order of Entity Creation

To ensure a comprehensive and conflict-free migration, it's important to first establish the fundamental structures in your Tempo setup before importing worklogs. Approach the creation of entities in the following order:

  1. Tempo Teams: Define and create teams to ensure they are available when associating worklogs.

  2. Accounts: Set up accounts to link financial or project-related data to worklogs.

  3. Workloads: Specify and establish workload schemes for your resources.

  4. Holiday Schemes: Configure holiday schemes applicable to teams and personnel within your organization.

  5. Work Attributes: Create work attributes for tracking additional details in your worklogs.

  6. Worklogs: Only after the above entities are established, proceed with importing worklogs to ensure a smooth correlation with the previously set entities.

  7. Plans

Key Steps for Migration

  1. Preparation for Migration:

    • All Jira standard worklogs will migrate to the target instance, which will lead to duplicates unless addressed.

    • Delete these existing worklogs on the destination using the Jira REST API.

  2. Export Tempo Worklogs:

    • Utilize the Tempo REST API for Timesheets to export worklogs from the source Cloud instance. This method allows for the inclusion of worklog owners and descriptions, essential since Jira retains only limited, anonymized worklog data.

  3. Delete Duplicate Worklogs on Target Instance:

    • Ensure all migrated Jira worklogs are removed from the target instance before importing Tempo data, using the Jira REST API to manage duplicates effectively.

  4. Import Tempo Worklogs:

Using APIs Effectively

  • Tempo REST API: For exporting and importing Tempo-specific worklogs.

  • Jira REST API: To manage Jira worklogs that are duplicated during standard migrations.

  • CSV Import: Provides an alternative import method if REST APIs present challenges.

Conclusion

Though the process requires manual intervention using APIs, following these steps ensures a smooth transition of Tempo data during a Cloud-to-Cloud migration in Jira. Engaging with Tempo partners when necessary can leverage expert assistance for complex migrations. As Tempo develops additional features, the process may become more streamlined, enhancing user autonomy and data consolidation across instances.