With Atlassian announcing the end of life for Jira Data Center, many organizations are preparing to move their Jira instances to Cloud. For teams using Checklists for Jira Data Center, the question naturally follows: How do we take our checklists with us?
The answer is Checklists for Jira Enterprise. It provides the same trusted functionality that teams rely on, while embracing the flexibility, scalability, and modern architecture of Atlassian Cloud.
In this guide, we’ll explore the benefits of using Checklists for Jira Enterprise, key differences between checklists on Data Center and Cloud, and how to migrate smoothly using either the Jira Cloud Migration Assistant (JCMA) or a direct import.
Why Move to Checklists for Jira Enterprise
Checklists for Jira Enterprise enables teams to track progress work items, ensure compliance and standardization, while reducing administrative overhead. Moving to the Cloud version offers:
- Scalability: Effortlessly support large teams and multiple spaces.
- Consistency: Use Global Checklists to standardize recurring processes across teams.
- Future-readiness: Built to align with Atlassian’s ongoing Cloud-first updates.
Checklists in Cloud vs. Data Center
While both versions deliver the same core functionality, they differ in how they achieve it.
How Checklists Work in Jira Data Center
In the Data Center version, Checklists create a custom field type for each checklist. These fields integrate fully with Jira, allowing you to use checklists on any Jira screen, query checklists with JQL search, export checklists with other Jira fields and assign contexts so the same checklist field can be adapted to different Jira spaces and work items.
How Checklists Work in Jira Cloud
Atlassian Cloud does not allow apps to create new custom field types. Instead, Checklists for Jira cloud stores checklist data in a secure database, then renders the checklists on the Jira work item.
This approach allows you to create unlimited checklists without inflating your Jira custom field count, and means there’s less dependency on the Jira administrators for day to day work.
Checklists for Jira cloud does create six standard custom fields in Jira to track metadata such as checklist completion status and progress.
Global Checklists: The New Standard
In Checklists for Jira Enterprise cloud, Global Checklists replace the Global Items feature used in Data Center.
Global Checklists:
- Are created and managed by Jira Administrators.
- Are applied via a context to designated spaces and work types.
- Are live so that any changes update across all open and new work items automatically.
- Are stored in a database, not within Jira fields.
This model provides centralized control while keeping your Cloud environment lightweight and efficient.
Configuration and UI Differences
Since Checklists in cloud are stored in a database, rather than as a custom field type, there are some different configuration settings, as well as differences in the UI you’ll need to know about:
Enable Spaces
Checklists in cloud can be enabled for individual spaces, or all spaces in your Jira instance.
Global Settings
Under Jira Settings → Marketplace apps → Checklists for Jira Enterprise → Global Settings, administrators can manage how and where checklists appear. Many of the settings which were on the Parameters page in Checklists for Jira Data Center may be found here. Some of these Global Settings can also be overridden at the project level, allowing more flexibility.
Permissions
By default, users who can view or edit the work item can also view or edit its checklists, but you can customize this further by setting custom checklist permissions. Note that permissions do not migrate automatically, so you’ll need to review them after the import.
Space Settings
Within each project (Space Settings → Apps → Checklists for Jira Enterprise), you can:
- Enable or disable checklists for that project.
- Choose whether checklist items use checkboxes, statuses, or both.
- Set up email notifications for mentions on checklist items.
Space Templates
Space-level templates can be created and managed without Jira Admin permissions, and can be set as defaults for specific spaces or work types.
Work Item UI
The checklist UI on work items remains simple and familiar:
- The checklist input field is visible by default.
- Statuses stay visible even when items are complete.
- A new extended menu provides quick access to checklist actions.
Migration Options: JCMA or Direct Import
Checklists for Jira has two options for migrating checklist data from Data Center to Cloud:
- Jira Cloud Migration Assistant (JCMA) – Recommended for most teams.
- Direct Import – For teams that have already migrated their Jira work items and only need to bring over checklists.
Option 1: Migrating with the Jira Cloud Migration Assistant (JCMA)
The JCMA provides a structured way to move your Checklists data as part of your larger Jira Cloud migration.
Preparing for Migration
In your Jira Data Center instance:
- Verify that you’re using Checklists for Jira Data Center v7.0.6 or later.
- Install the Jira Cloud Migration Assistant app.
- Check your connected app details in Atlassian Admin to confirm version and app key is com.okapya.jira.checklist.
In your Jira Cloud instance:
- Install Checklists for Jira Enterprise (v2.0.0a or later).
- Confirm the app key is com.okapya.jira.checklist.
- Ensure the projects you plan to migrate don’t already exist in Cloud.
Running the Migration
- Navigate to System → Migrate to cloud in your source instance.
- Connect to your target Cloud site and begin Assessing your apps.
- Under the list of apps, find Checklists for Jira and mark it as Needed in Cloud.
- Complete pre-migration checks and create a migration.
- Choose what to migrate (projects, boards, users, etc.) and run the migration.
🟢 Important: If you stop and restart a JCMA migration, previously imported data will be overwritten. Avoid canceling an import in progress.
Note that Global and Local items are now separate in Cloud; work items that previously had both will now display two distinct checklists.
Option 2: Direct Import
If your Jira issues are already in Cloud, you can import checklist data directly.
Preparing for Migration
In your Jira Data Center instance:
- Verify the scope of each checklist’s context—avoid using “All Projects” unless necessary.
- Document configurations including permissions, conditions, post functions, and item assignees.
- Use the Checklist Export feature to generate export files.
In your Jira Cloud instance:
- Install Checklists for Jira Enterprise and prepare for downtime (checklist data will be temporarily unavailable during import).
Executing the Migration
- Navigate to Jira Settings → Marketplace apps → Checklists for Jira Enterprise → Import.
- Select the Server/DC tab.
- Upload the exported files.
- Choose whether to clear previously imported data or append to existing data:
- Enable Clear previously imported data if you are reimporting or correcting data.
- Disable it to append additional checklists.
- Click Start import and monitor progress.
Post-Migration Review
After migration (regardless of method) perform these checks:
- ✅ Set the Checklists for Jira Enterprise Global Settings to fit the needs of your teams.
- ✅ Review and adjust Checklist permissions as needed.
- ✅ Validate Global Checklists for correct context.
- ✅ Default local checklist items are not supported in cloud, so you’ll need to recreate them as items on a default template.
- ✅ Replace Data Center custom fields with the Checklists for Jira Cloud custom fields in automation rules, board cards, etc..
- ✅ Reassign checklist items.
- ✅ Verify that any custom statuses have migrated correctly
Your Enterprise subscription includes priority support, including discovery meetings, guided migration calls, and troubleshooting assistance.
Ready to Move to the Cloud?
Checklists for Jira Enterprise ensures that your established processes move with you so your teams can continue working efficiently and consistently in Jira Cloud.
If you’re preparing for migration or need hands-on help, contact the HeroCoders support team. We’ll help you plan, test, and execute your migration smoothly.
