If you are currently using Timepiece - Time in Status on Jira Server or Jira Data Center and are planning to migrate to Jira Cloud, this section explains everything you need to know to ensure a smooth transition.
Timepiece does not store your issue data, all reports are generated directly from Jira issue histories. This means the core of your data migrates as part of the standard Jira migration process. However, Timepiece does maintain its own app-specific settings that need to be carried over, including custom calendars, access permissions, date format settings, saved parameter sets, and dashboard gadgets.
This section covers three topics:
Migration with Jira Cloud Migration Assistant (JCMA)
The recommended migration path is to use Atlassian's Jira Cloud Migration Assistant (JCMA), which has built-in support for Timepiece. When used with Timepiece version 6.3.1 or later on Data Center, JCMA can automatically migrate your calendars, access settings, format settings, and saved parameter sets to the Cloud instance.
See Server/DC to Cloud Migration with JCMA for the full guide including prerequisites, what gets migrated, override behavior on repeated migrations, and post-migration validation steps.
Manual Migration
If you prefer to migrate without JCMA, or need to handle parts of the migration that JCMA does not cover, such as dashboard gadgets and REST API integrations, the manual migration guide provides a step-by-step checklist. It covers how to manually transfer calendars, access settings, and format settings through the Jira Admin UI, how to identify users who have saved parameter sets using a database query, and how to locate and re-create Timepiece gadgets on dashboards in the new Cloud environment.
See Server/DC to Cloud Manual Migration for the full checklist.
Feature Comparison
Almost all features of Timepiece are available on both Server/DC and Cloud. However, there are a small number of differences.
See Server/DC and Cloud Feature Comparison for the full feature-by-feature comparison table.