---
title: "Timesheets for Jira: Data Center to Cloud migration guide"
canonical: "https://support.appfire.com/space/SUPPORT/3467182381/Timesheets%20for%20Jira%3A%20Data%20Center%20to%20Cloud%20migration%20guide"
format: markdown
---
## Overview

This article explains the available migration options for customers using Timesheets for Jira on Jira Data Center who are planning to migrate to Jira Cloud. It also describes which configurations require manual recreation and provides SQL queries that administrators can use to assess their existing configuration before migration.

## Migration support

There's no direct Jira Cloud Migration Assistant (JCMA) migration path for Timesheets for Jira (Data Center) to Timesheets for Jira (Cloud).

This means that:

- Report configurations aren't migrated automatically.
- App settings aren't migrated automatically.
- Calculated fields and report configurations must be reviewed and recreated manually in Cloud.

## Available migration options

### Option 1: migrate using Reports and Timesheets for Jira (supported)

If you require a supported JCMA app migration path, use the following approach:

1. Install Reports and Timesheets for Jira on your Jira Data Center instance.
2. Manually recreate your existing Timesheets for Jira reports within Reports and Timesheets for Jira.
3. Use the supported JCMA migration path for Reports and Timesheets for Jira.

Note: Installing Reports and Timesheets for Jira doesn't automatically convert or import existing Timesheets for Jira reports or configurations.

### Option 2: migrate directly to Timesheets for Jira Cloud

If you migrate directly from Timesheets for Jira (Data Center) to Timesheets for Jira (Cloud), there's no supported app migration path. All reports, calculated fields, and app configurations must be recreated manually after migration.

## What migrates and what doesn't

| Area | Current status | Guidance |
| --- | --- | --- |
| Timesheets for Jira DC > Cloud | Not supported | No direct JCMA-based app migration path is available. |
| Reports and Timesheets for Jira DC > Cloud | Supported | JCMA app migration support exists for this app path. |
| Existing Timesheets reports on DC | Manual | Reports must be reviewed and recreated manually. |
| Calculated fields | Manual | Identify usage and recreate the configuration in the target app. |

## Recommended migration approach

- Installing Reports and Timesheets for Jira on Data Center doesn't automatically convert existing Timesheets for Jira data.
- Timesheet reports, report pages, and calculated field references won't appear in Cloud unless manually recreated.
- Before the migration window, inventory all reports, owners, report pages, and calculated fields to estimate the rebuild effort.

## Assess existing configuration (SQL discovery)

For discovery purposes, administrators can use read-only SQL queries on the Data Center database to inventory reports and owners.

> ⚠️ These queries are for investigation only and aren't a supported migration mechanism.

### List report owners

```
SELECT
    u."ID" AS owner_id,
    u."ACCOUNT_ID" AS account_id,
    au.lower_user_name AS username,
    COUNT(r."ID") AS total_reports
FROM "AO_D9F874_AIO_USER" u
JOIN "AO_D9F874_AIO_REPORT" r ON u."ID" = r."OWNER_ID"
LEFT JOIN app_user au ON u."ACCOUNT_ID" = au.user_key
WHERE r."CANNED" IS NOT TRUE
GROUP BY u."ID", u."ACCOUNT_ID", au.lower_user_name
ORDER BY total_reports DESC;
```

### Identify calculated field usage in reports

```
SELECT DISTINCT
    cf."NAME" AS calculated_field_name,
    cf."FIELD_ID" AS field_internal_id,
    r."ID" AS report_id,
    r."NAME" AS report_name,
    u."ACCOUNT_ID" AS report_owner_account_id,
    au.lower_user_name AS report_owner
FROM "AO_D9F874_AIO_CALCULATED_FIELD" cf
JOIN "AO_D9F874_AIO_REPORT_PAGE" rp
    ON rp."COLUMN" LIKE '%' || cf."FIELD_ID" || '%'
    OR rp."ROW" LIKE '%' || cf."FIELD_ID" || '%'
    OR rp."DATA" LIKE '%' || cf."FIELD_ID" || '%'
JOIN "AO_D9F874_AIO_REPORT" r ON rp."REPORT_ID" = r."ID"
LEFT JOIN "AO_D9F874_AIO_USER" u ON r."OWNER_ID" = u."ID"
LEFT JOIN app_user au ON u."ACCOUNT_ID" = au.user_key
WHERE r."CANNED" IS NOT TRUE
ORDER BY cf."NAME", r."ID";
```

## Frequently asked questions

<details>
<summary>Frequently asked questions</summary>

### Can we migrate Timesheets for Jira from DC to Cloud with JCMA?

No. There's currently no direct JCMA migration path for Timesheets for Jira DC to Cloud.

### Can we export/import or script report recreation?

No automated export/import or scripting method is supported.

### Can SQL migrate reports?

No. The SQL queries in this article help inventory existing reports and calculated fields for migration planning. They aren't a supported migration method.

### Are the SQL queries supported?

The SQL queries are read-only discovery tools to assist migration planning. Don't use them to modify the database; they don't replace a supported migration process.
</details>