Reminder for Jira migration guide (Data Center → Cloud)

This is a short, practical guide summarizing the essential steps for migrating the Reminder app from Jira Data Center to Jira Cloud. Before starting the migration, carefully review the official Atlassian documentation linked at the end of this guide to ensure all prerequisites and procedures are fully understood.

1. Assess and prepare apps with the Cloud Migration Assistant: https://support.atlassian.com/migration/docs/assess-and-migrate-apps-with-the-cloud-migration-assistant/

2. Assess apps with the Jira Cloud Migration Assistant (JCMA): https://support.atlassian.com/migration/docs/assess-apps-with-the-jira-cloud-migration-assistant/

3. Step‑by‑step DC → Cloud (Atlassian Community): https://community.atlassian.com/forums/Jira-articles/Step-by-Step-Guide-Migrating-Jira-Data-Center-to-Jira-Cloud/ba-p/2925735

4. Migrate Marketplace app data separately: https://support.atlassian.com/migration/docs/migrate-marketplace-app-data-separately/

As recommended by Atlassian run at least one test migration before production.

1) Pre‑checks (before any run)

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

• ✅ All projects/issues that use reminders are identified.

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

2) Assess the Reminder 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 Reminder 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 Reminder 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 result

If the Data Center → Cloud migration process is interrupted, or if Jira encounters unexpected issues, some entities required by the Reminder for Jira app may be missing in Cloud. In such cases, the following scenarios can occur:

1. Missing Issue

(The issue linked to the reminder does not exist in Cloud.)

• The reminder will still be imported, but without a linked issue.

• The following note will be appended to the message:

  “This reminder was originally created for {issueKey} — {summary} in Jira Data Center (migrated item, issue not found).”

2. Missing Recipient

(The intended recipient does not exist in Cloud.)

• The reminder will be imported, but the Creator will be set as the Recipient.

• The following note will be appended to the message:

  “This reminder was originally created in Jira Data Center for {recipient_name} (migrated item, recipient not found).”

3. Missing Creator (Sender)

(The creator or sender of the reminder does not exist in Cloud.)

• The reminder will be imported, but the Recipient will be set to N/A.

• The following note will be appended to the message:

  “This reminder was originally created by {creator_name} in Jira Data Center (migrated item, creator not found).”

4. No Creator and No Recipients

• Reminders without both a sender and recipients will not be imported.

Migration Completion Messages

At the end of your migration, you will see one of the following completion messages:

• With Warnings (example):
  “Reminder for Jira (Issue Follow-Up & Notifications) migration completed with warnings. 458 reminders were successfully imported from Jira Data Center. Some reminders required adjustments or were skipped due to missing entities: Missing issues: 1 — imported as unlinked (To do). Missing recipients: 1 — reassigned to the sender. Missing creators: 1 — delivery unaffected, can be accessed in Reminders queue in Jira admin's settings or in the relevant issue. Skipped (no sender and no recipients): 1 — not imported.”

• Without Warnings (example):
  “Reminder for Jira (Issue Follow-Up & Notifications) migration completed without warnings.
  500 reminders were successfully imported from Jira Data Center.”

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:

• Data Center only:

  • Conditional issue-related reminders — allows sending reminders only when specific conditions are met (for example, issue status or assignee).
    ⚠️ Because conditional reminders are not yet supported in Jira Cloud, all migrated or newly created reminders will be sent exactly at their scheduled time, regardless of issue status or field values. This ensures that reminders continue to function, but they might trigger even if their original DC condition would have prevented them. Note that we are working on bringing conditional reminder support to the Cloud version in future releases.

  • Integration with the Configuration Manager app — when using Configuration Manager for Jira, the Reminder for Jira app provides a built-in integration to help migrate and deploy reminder data between Jira instances.

• Cloud only:

  • My Reminders gadget — a convenient dashboard gadget showing all reminders created by or assigned to the user, providing quick access to upcoming notifications.