Moving to Jira Cloud when your leave app has no Cloud version

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

Short answer. If your leave requests were Jira issues, the issues move with Jira. What does not move by itself is what the app knew: each person's allowance, the balance, the leave rules. So the one thing to get right is the balance on the day you switch — write it down per person before the move, and put it into whatever you use on the Cloud side.

1. Which app 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 Vacation Manager for Jira (by Transition Technologies PSC) for Data Center only. In the migration information its maker publishes, the Cloud version is marked private — not on the Marketplace — and the migration path as unknown.

The same maker sells a different app in Cloud, Absence Tracker, which its listing describes as logging absences in a dedicated Jira project and showing them on any issue. If you use Vacation Manager today, ask the maker first: a private Cloud version can be available on request, and they know best what carries across.

2. What moves, and what does not

Vacation Manager's own listing says each vacation type is a Jira issue type, so each request is a Jira issue. From Atlassian's list of what the Jira Cloud Migration Assistant migrates:

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

In practice: expect the old requests to arrive as issues you can still search, and plan as if the allowance, the balance and anything the app calculated will not.

3. Write these down before you move

Each person's balance on the switch day — days left, and how many of them are carried over from last year. This is the number people will check first.
Approved leave that has not happened yet. Someone booked for next month must still be booked after the move.
Each person's yearly allowance and start date, if they joined this year.
Your rules: carry-over (all, none, a maximum), any "use by" date, which public holidays apply, and which kinds of leave come out of the balance.

Switching at the start of your leave year is the easy case: nobody has taken anything yet, so the only number to carry is last year's leftover.

4. Your options on the Cloud side

Keep leave as Jira issues, with no app. It works for a few people; the costs — no balance, no working days, no carry-over — are in How to track vacation and PTO in Jira Cloud.
The maker's own Cloud options — ask about the private version, or look at Absence Tracker.
Another leave app with a Cloud version. The checklist in the guide above says what to look for.

5. Where Time Off fits

Time Off is our app, so read this part as the maker's description, including how the switch works:

At the start of a leave year: on the People tab, set each person's days per year and put last year's leftover in Days carried over from before. That is the whole migration.
In the middle of a year: the same, plus each person enters the leave they already took this year as a request with its real dates, and an administrator approves it. Past dates are accepted, and the balance then matches the one you wrote down. Future leave that was already approved goes in the same way.
The balance is recalculated from the requests every time, counts working days only, handles half days, and pro-rates the first year from a start date.
Public holidays for 17 countries, a different country per person, and carry-over with an optional "must be used by" month.
Free for sites up to 10 users, then US$0.40 per user per month. No external servers: data stays in Atlassian's storage for your site.

What it does not do, said up front: import the old app's data (entries are made in the app, as above), email notifications (Atlassian does not give apps email addresses), per-team approvers (Jira administrators approve), and regional holidays. Full detail in the documentation.

Time Off on the Atlassian Marketplace · About Time Off

Time Off is an independent app, not made by or affiliated with Atlassian or Transition Technologies PSC. 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.