Hosting: Jira Cloud
The migration copies the following data from Data Center to Cloud.
What is migrated
-
Calendars of every type, including calendar subscriptions, with their settings, permissions, event types and conditional colors.
-
User events with participants and linked issues, including recurring events and their changed or deleted occurrences.
-
The calendar list of each user, with "Subscribe to reminders" and "Subscribe to event changes".
-
Quick filters and conditional colors of users, with favourites and sharing with groups.
-
Default calendars, default quick filters and default color conditions.
-
Calendars on Jira Service Management portals.
-
The personal "Reminders" and "Notifications" settings of each user.
What is not migrated
Dashboard gadgets, export links and the IP allowlist are not migrated, so you add the gadget and create the export links again. "Calendar log" and both "Audit log" tabs start empty. Google Calendar sync does not exist on Data Center, so each user turns it on in Cloud.
Data of a user who does not exist in Cloud is left out: their calendar list, private quick filters and rows in calendar permissions.
Calendars that change or need a fix
When the saved filter of a Filter calendar is not migrated, the calendar arrives as a JQL calendar with the query of the filter.
A calendar whose start or end date is a custom field that does not exist in Cloud is created with an error: its tooltip in the calendar list says "Start field doesn't exist" or "End field doesn't exist". Open "Edit" and choose the date field again.
JQL in a calendar can be up to 512 characters long in Cloud. A calendar with a longer query is not created and its events are not migrated, so shorten the query in Data Center first.