Moving to Jira Cloud when your time report app has no Cloud version

Jira Data Center → Cloud · Marketplace listings and Atlassian's migration documentation checked on 12 September 2026

Short answer. Your worklogs are Jira data, and Atlassian's migration assistant moves them to Cloud. What stays behind is the app: its settings, rates and saved reports. So the history is safe — the job is to export what lives inside the app before you move, and to choose what reads those worklogs on the Cloud side.

1. Which apps this is about

Atlassian ends Jira Data Center on 28 March 2029, so every Data Center site is moving somewhere. On 12 September 2026 the Atlassian Marketplace listed these two time report apps for Data Center with no public Cloud version:

App	Maker	What the Marketplace shows about Cloud
Time Tracking And Billing Reporting	jPlugs	No Cloud listing. In the migration information the maker publishes, the Cloud version is marked private (not on the Marketplace) and the migration path as unknown.
TimeWise-Timesheets with Plan and WorkLog	DragonSoft	No Cloud listing and no migration information published. The same maker's Cloud apps are for other jobs (workflows, reminders, user management).

This changes. If you rely on either app, ask its maker directly — a private Cloud version can be available on request — before you plan around this page.

2. What moves, and what does not

From Atlassian's list of what the Jira Cloud Migration Assistant migrates:

Moves to Cloud	Does not move by itself
Issue work logs and time spent	Marketplace app data — the app's maker has to provide an automated migration path
Users and groups, issues, comments, issue history	Custom fields that belong to apps (Atlassian suggests re-creating them and topping them up by CSV import)

For a time report app, "app data" is usually the part you built up over years: hourly rates, rules for overtime, saved report layouts, and any approvals.

3. Export these before you move

The rates, with the date each one started. A rate table without dates will price last year at this year's rate.
The reports you already sent or approved — as files, month by month. After the move they are the record of what was agreed at the time.
Your rules: standard day length, overtime, weekend or night rules, rounding. Write them down; you will need them to check the new numbers.
One month to test with: note the hours and cost of a recent month. After the move, the same month in the new tool should give the same hours — if it does not, something did not come across.

4. Your options on the Cloud side

Jira on its own keeps every worklog and shows time per issue, but has no rates and no cost report. The spreadsheet method, and the three traps that make its number wrong, are in How to turn Jira worklogs into a cost report.
A timesheet app with a Cloud version. The Marketplace has many. If what you used was planning, a calendar of who logged what, or people submitting timesheets for approval, that is the kind of app to look for.
A cost report app, if the question you answer each month is "what did this project cost".

5. Where Fair Hours fits

Fair Hours is our app, so read this part as the maker's description. It does one of the jobs above — turning worklogs into cost — and not the others:

Because it reads the worklogs Jira already has, the months before your migration can be priced too, as soon as the rates are entered.
Rates by company, team (a Jira group) or person, each with an effective date — so the rate table you exported goes in as it was.
Overtime counted per person per day, weekend multipliers and a night premium, all off until you set them. Worklogs cut at midnight.
A reconciliation against Jira's own hours for the same month — the check in step 4 of section 3, done for you.
Close a month to record who approved it. Costs are visible only to Jira administrators. Free for sites up to 10 users. No external servers.

What it does not do, said up front: planning, timesheet submission and approval by each person, payroll or invoicing — and it reports one project at a time. If you used TimeWise for planning or time approval, Fair Hours does not replace that part. Full detail in the documentation.

Fair Hours on the Atlassian Marketplace · About Fair Hours

Fair Hours is an independent app, not made by or affiliated with Atlassian, jPlugs or DragonSoft. Jira is a trademark of Atlassian. App names belong to their makers. What the Marketplace shows about other apps was read on the date above and may have changed since.