If someone intends to migrate from Time Tracker to Timesheets
To clarify, Time Tracker and Tempo Timesheets do not share the same database.
-
Tempo Timesheets stores data in its own database.
-
Time Tracker does not have a separate database—it reads and writes data directly from Jira’s database.
What This Means for You:
✅ Your worklogs and time tracking data will still be available in Time Tracker since all tracking data is stored in Jira’s database.
❌ However, Tempo-specific features like Accounts, Plans, and Approvals will not be carried over, as they are exclusive to Tempo.
In summary: There’s no migration needed—all time-tracking data stored in Jira will be accessible in Time Tracker.
Migration DC/Cloud
At the moment, Time Tracker doesn’t have an automated migration path and isn’t migrated through JCMA. Here’s a quick overview of how the process works:
-
Data safety: All Time Tracking and Issues data are stored in your Jira database, so no data will be lost. For more details, you can refer to this KB: [How intrusive is Prime Timesheet plugin in JIRA?].
-
Migration process: Since your data is stored within Jira, the migration is essentially as straightforward as migrating Jira Software itself. Atlassian should handle this part automatically.
-
App reinstallation: The Time Tracker app/add-on will need to be installed in your Cloud environment, and any dashboard gadgets or email subscriptions will need to be reconfigured manually. You can find more information in this KB: [Cloud/Server Moving/Migration].
-
Licensing: Please note that licenses for Prime plugins for Jira Cloud need to be purchased separately.