Delegated Project Creator for Jira: Data Center to Cloud migration health checks when using JCMA
Use the following migration health and readiness checklist to assist in migrating Delegated Project Creator for Jira from Data Center (DC) to Cloud using JCMA.
✅ Pre-Migration Checks
Checkpoint | Actions | |
|---|---|---|
| 1 | App Compatibility and Versioning | Ensure Delegated Project Creator (DPC) Data Center is v6.0.3 or higher (migration support introduced with JCMA compatibility fix). Verify JCMA version ≥ 1.12.26. Confirm the DPC Cloud app is installed on the target Cloud instance with an active license before migration. |
| 2 | Configuration and Permissions Inventory | Navigate to > Manage Apps > Delegated Project Creator > Project Templates Settings. Confirm that all template owners and creator groups exist in both the source and target (Cloud) environments. Use the Project Creation Report to identify which templates are currently in use. |
| 3 | Template Configuration Review | Review each Project Template. Associated Schemes (Permissions, Issue Type, Notifications, Roles). Verify Project Request Questions (and mandatory fields). Validate custom “Base Projects” |
| 4 | Dry Run Validation (Recommended) | Execute a JCMA test migration. Monitor JCMA logs for: No PluginDataMigrationException entries. Successful completion at 100%. If the DPC section shows “Skipped”, upgrade the app to the latest version. |
✅ Post-Migration Checks
Checkpoint | Actions | |
|---|---|---|
| 1 | Template and Permission Verification | In the Cloud environment, navigate to Delegated Project Creator > Project Templates Settings. Verify that all templates and associated schemes appear correctly. Confirm that Project Creation Permissions and Request Permissions groups are present and mapped to existing Atlassian Cloud groups. Validate that Project Approvers are retained. |
| 2 | Functional Validation | Test the following actions: Create a Project from a Template. Submit a Project Request. Approve/Reject Requests. Check the Project Creation Report. |
| 3 | Data Integrity | Validate Project Template associations with: Schemes (Workflows, Notifications, Permissions) Issue Schemes with predefined issues. Components and Versions imported correctly. |
| 4 | Known Limitations / Behavior Changes | Refer to the Feature comparison between Data Server and Cloud versions |
✅ Troubleshooting and Recovery
Scenario | Root Cause | Resolution / Reference | |
|---|---|---|---|
| 1 | JCMA shows error: “Some apps are not registered to receive migration notifications.” | The Delegated Project Creator app failed to register its migration hook with JCMA due to missing handler mapping. | Upgrade to DPC v6.0.4 or later, which includes a fix for the migration hook registration.- Ensure JCMA ≥ 1.12.26 and the DPC Cloud app is installed on the target Cloud instance before migration.- Retry migration from JCMA. |
| 2 | DPC data marked as “Skipped” in the JCMA migration report. | JCMA did not detect the app because it was using an older version, or the app was not installed on the target Cloud. | Pre-install DPC Cloud on the target Cloud site and validate the active license. Upgrade the Data Center app to version 6.0.3 or later. Retry the migration; the app should show as “Completed.” |
| 3 | Post-migration: “Create Project from Template” button does nothing. | JCMA migration succeeded, but Cloud permissions mapping is incomplete (missing app-level permissions). | Grant Administer Jira global permission to the “atlassian-addons-admin” group in the Cloud instance.- If unavailable, contact Atlassian to restore it.- Revalidate DPC permission sets. |
For detailed information about migrating the DPC app from the Server or Data Center to the Cloud, please refer to our migration documentation here: