Migration guide (Data Center → Cloud)

Feature availability differences (Data Center vs Cloud)

When migrating from Jira Data Center to Cloud, keep in mind that the feature set differs slightly between platforms. The Cloud version does not support:

• the following settings from the Advanced calendar section:

  • linking of the issue’s duration to the Original estimate;

  • 24-hour / 12-hour time display format on the grid (only 12-hour format is supported);

  • groups whose members are allowed to edit issues directly on the calendar;

• timeline view grouping by different fields;

• quick filters grouping;

• different quick filter operators (only AND);

• export to / import from iCal format;

• service desk / project sections of the app;

• sharing calendars with individual users (only groups);

• any day of the week can be selected as first (only Sunday and Monday can be selected);

• hiding any day from the grid (only weekends can be hidden).

Migration steps

1) Pre‑checks (before any run)

• ✅ Jira Cloud Migration Assistant (JCMA) installed/updated on DC (latest available).

• ✅ All projects/issues that are used in the app are identified.

• ✅ The Calendar for Jira installed on the Cloud site (same vendor as on DC) and a trial/license activated.

2) Assess the Calendar for Jira app in JCMA (DC)

1. Go to Administration → System → Migrate to cloud (open Jira Cloud Migration Assistant).

   

2. Open Assess your apps.

3. Locate your Calendar for Jira app in the list and make sure that it is chosen for migration (Needed in cloud).

3) Prepare the app for migration (Cloud + DC)

1. Open Prepare your apps.

2. Connect to a cloud site

3. Install your Calendar for Jira (if not already installed)

4. Consent to app data migration.

4) Migrate your data

1. Open Create a migration.

   

2. Follow the steps of migration guide.
   Make sure that all data relevant to the app such as projects, issues, users and groups will be migrated (or have already been migrated) during this process.

3. Run pre‑migration checks and review the data.

4. Run migration.

5) Migration limitations and fallback behavior

If the Data Center → Cloud migration is interrupted, incomplete, Jira Cloud does not contain all entities referenced by a calendar or there is a diffrence in the app functionality between DC and Cloud some calendar data may be migrated with limitations:

1. Missing or inaccessible projects
   If a project used by a calendar does not exist in Cloud, or the user does not have access to it in the target instance, the calendar is still migrated. However:

   1. issues from that project will not appear in the calendar;

   2. an alert icon will be shown in the calendar settings button to indicate a configuration problem;

   3. the calendar base may become invalid, depending on how the calendar was configured.

2. Missing saved filters
   If a saved filter used by a calendar does not exist in Cloud, the calendar is still migrated, but:

   1. the calendar grid will be empty;

   2. the user will see an error because the calendar base is invalid.

3. Missing groups
   If groups referenced by calendar sharing settings do not exist in Cloud, the calendar is still migrated, but those groups are not added to sharing. They will not appear in the sharing menu.
   Sharing is also not migrated if the calendar was shared directly with individual users, because Cloud does not support this sharing mode.

4. Missing custom fields
   If custom fields used by a calendar do not exist in Cloud, the calendar is still migrated, but those fields are not shown in calendar cards or in the issue preview card.

5. Missing users
   If the original calendar creator cannot be found in Cloud, the migration first attempts to identify that user by emailAddress among existing Cloud users. If the creator still cannot be identified:

   1. the calendar is still migrated;

   2. the calendar is migrated without a creator;

   3. the calendar cannot be deleted, because only the creator has permission to delete it.

6. Quick filters and card colors
   In Data Center, quick filters and card colors can be created without JQL and during migration:

   1. quick filters with empty JQL are not migrated;

   2. card colors with empty JQL are not migrated.

7. External calendars
   External calendars have specific migration rules:
   - if an external calendar has no name, it is migrated with a default name in the format External Calendar N, where N is a number;
   - external calendar names must be unique within the same calendar in Cloud.
   Additionally, an external calendar cannot be migrated:

   1. if its link is missing;

   2. if it was added as a file.

8. First day of the week
   In Data Center, the first day of the week can be set to any day. In Cloud, only Monday and Sunday are supported.During migration:

   1. calendars configured to start on Sunday will keep Sunday;

   2. all other values will be migrated as Monday.

9. Hidden days
   In Data Center, any days of the week can be hidden. In Cloud, this setting is not migrated and not processed during migration.

10. Empty end dates
    In Cloud, there is a setting that controls whether issues with an empty end date should still be displayed. By default, Cloud allows such issues to be displayed.
    To preserve the familiar Data Center behavior, migrated calendars do not display issues when the configured end date field is empty.

11. Same start and end date fields
    In Data Center, a calendar can use the same field for both start and end date. In Cloud, this is not allowed. When such a calendar is migrated:

    1. it is migrated as a single-date calendar;

    2. the end date field is left empty.

Migration Completion Messages

At the end of your migration, you will see one of the following completion messages (example):
“Calendar for Jira (Timeline Roadmaps and Custom Events) migration completed. 35 calendar(s) were migrated. 22 item(s) were skipped due to validation errors or missing data: 5 external calendar(s), 6 quick filter(s), 1 card color(s), and 10 role(s). 37 event(s) were created.”