DC to Cloud migration guide

Here's all you need to know about moving your Jira Data Center (DC) instance to Jira Cloud with Agile Poker.

For a complete comparison of Agile Poker for Jira DC and Agile Poker for Jira Cloud, refer to this page.

Data Center to Cloud migration

Agile Poker will appear in Jira Cloud Migration Assistant to allow a smooth transition from Data Center to Cloud.

Most Agile Poker data will be migrated one-to-one, including general configuration, Interactive and Asynchronous sessions, and their configurations. However, there are a few caveats to keep in mind:

Automatic migration availability depends on Atlassian enabling app migration in Jira Cloud Migration Assistant.

Not migrated

Relative estimation sessions will not be migrated. Please finish any ongoing Relative sessions before the migration, as their state won't be transferred.

Special handling of some fields

Asynchronous estimation sessions: Only the last round of estimation comments will be migrated. Previous round comments won’t be transferred.
Moderator settings in Asynchronous sessions: If multiple Moderators were defined in DC, all session participants will become Moderators in Cloud (“Everyone” option selected). The same applies if no Moderator was set.
Issues without the Estimation field: In DC, Agile Poker allowed estimation of issues without an Estimation field. These issues will be migrated but will remain hidden in Cloud until the field is configured.
Scoped Session migration: The Scoped session in Agile Poker DC will be migrated as an Interactive session in Cloud, with the defined scope preserved.

Special cases handling (Update)

Agile Poker sessions are linked to a specific Jira board. Previously, there were limitations during migration documented by Atlassian. However, Atlassian has resolved the migration issue mentioned in this section via the resolution of the MIG-169 ticket. Boards linked to more than one project can now be migrated successfully.

Estimation sessions that do not have at least one participant available will not be migrated. This may occur if all users participating in a specific session were skipped during the Jira DC to Cloud migration. For example, because their accounts were deactivated or the users were not selected for migration.

It's recommended to verify the latest updates on Jira Cloud Migration Assistant to ensure the smooth transition of all sessions. To learn more, check out Atlassian documentation here.

Migration troubleshooting

We highly recommend enabling logging for Agile Poker. To do that, you need to add com.spartez.pokerng with info level at Jira Data Center’s logging and profiling page (more information).

The following log entry will appear once after Agile Poker or JCMA gets restarted. It indicates that Agile Poker is ready for the migration process:

2021-02-19 ... INFO ... [...CloudMigrationHandler] The migration listener is ready to take migrations events

The following log entries will appear during each migration process:

2021-02-24 ... INFO [...CloudMigrationHandler] Migration New Migration started
2021-02-24 ... INFO [...MigrationDtoProvider] Preparing MigrationDto ...
2021-02-24 ... INFO [...MigrationDtoProvider] MigrationDto with 10 boards and 45 sessions is prepared.
2021-02-24 ... INFO [...CloudMigrationHandler] Writing app data on the cloud ...
2021-02-24 ... INFO [...CloudMigrationHandler] App data is written.

Such warning logs will contain information about boards and sessions that were skipped during the migration; as well as details about session participants, issues, and custom fields referenced in the migrated sessions that were missing in Jira Cloud:

2021-02-24 ... WARN [...MigrationDtoProvider] 3 sessions from 2 boards got skipped. Board ids: [1001, 1002] - Session ids: [2001, 2002, 2003]
2021-02-24 ... WARN [...MigrationDtoProvider] 4 users are missing from cloud. User ids: [31, 32, 33, 34]
2021-02-24 ... WARN [...MigrationDtoProvider] 5 issues are missing from cloud. Issue ids: [41, 42, 43, 44, 45]
2021-02-24 ... WARN [...MigrationDtoProvider] 2 custom fields are missing from cloud. Custom field ids: [51, 52]

We have put a limit on the maximum size of the Agile Poker data migration bundle. If that limit is exceeded, you’ll see a corresponding message in the migration log. Please contact our support team for assistance in such cases. Although we anticipate no customers will exceed this limit, we have implemented measures to protect our systems from unexpectedly large data sets.

If you need any guidance or assistance during your migration process, please don't hesitate to contact us. We'll be glad to help! We'd also love to hear about your organization's specific needs so that we can adjust our product development plans accordingly.