/
Jira DC to Cloud migration

Jira DC to Cloud migration

When migrating to Jira Cloud with Atlassian's Jira Cloud Migration Assistant (JCMA), Electronic Signatures records are transferred, preserving core signature data.

While signature records migrate completely (signatory, timestamp, and meaning), the issue History tab information showing workflow transitions, signature requirements, and validation events does not migrate during the process.

Platform differences

While we maintain feature parity wherever possible, architectural differences between Data Center and Cloud platforms result in some functional variations. Core signature capabilities and usability remain consistent, but workflow integration features might require reconfiguration.

Key differences include:

  • Authentication method: Cloud uses PIN-based signatures instead of password validation.

  • Workflow components: Validators and post functions require reconfiguration after migration.

  • Custom field limitations: Some DC-specific fields are not available in Cloud.

On this page:

On this page:

You can see a comparison between the DC and Cloud versions of the app here.

Known limitations:

The Jira Cloud Migration Assistant has current limitations that might prevent some Electronic Signatures data from migrating completely. For example, some DC-specific custom fields, such as User Validator fields, Logged User Validator fields, and DC-specific signature metadata, cannot be migrated. These fields are replaced with cloud-equivalent functionality that provides similar capabilities. For additional information, see What gets migrated with the Jira Cloud Migration Assistant.

What data is migrated

The migration process transfers your Electronic Signatures records from Jira DC to Cloud. All signature records from the E-Signatures section will appear in the Electronic Signatures panel in your cloud issues exactly as they did in your DC environment, including:

  • Signatory names

  • Timestamps

  • Signature meanings

  • Issue status when signed

Migration process

Prerequisite

Before beginning the migration process, ensure your environment meets these requirements:

Jira Data Center version

Version 9.0 or higher

Electronic Signatures version

Version 3.0.6-jira8 or higher

Jira Cloud Migration Assistant

Installed and configured on your Jira DC instance

Administrative access

Jira administrator permissions on both source and destination instances

Network access

If your Jira DC instance is behind a firewall, ensure access to the atlassian.com domain or other Atlassian domains.

Migration knowledge

Familiarity with Atlassian's JCMA documentation and process.

Before the migration

Before initiating the migration process, configure both your Data Center and Cloud environments to ensure Electronic Signatures data transfers correctly.

To…

Do this…

To…

Do this…

Prepare your Cloud environment

  • Install (or reinstall) Electronic Signatures for Jira Cloud on your destination instance.

  • Complete initial app configuration. This is required only once, before your first migration.

Prepare your DC environment

  1. Enable migration feature flags in your Jira DC instance:

    • Navigate to <Jira_URL>/secure/SiteDarkFeatures!default.jspa

    • Add com.atlassian.jira.migration.app-migration.feature to the Site Wide Dark Features section

  2. Configure logging for migration monitoring:

    • Go to Jira Administration > System > Logging and profiling

    • In the Default Loggers section, click Configure logging level for another package

    • Add these packages with Trace level:

      • ru.andreymarkelov.atlas.plugins.cfr.listener.CloudMigrationProcessListener

      • ru.andreymarkelov.atlas.plugins.cfr.service.CloudMigrationService

Migration steps

  1. To start the migration:

    1. In Jira DC, navigate to Administration > System > Import and Export > Migrate to cloud.

    2. Select Assess and Install apps and mark Electronic Signatures as Needed in cloud.

    3. Complete the Assessment wizard according to Atlassian's guidance.

  2. Go to the Migrate section and click Create a migration.

  3. Click Connect to cloud to link your DC and Cloud instances.

  4. Specify migration name and select your cloud site.

  5. Select migration scope based on your current state.

For new cloud instances

Select the projects and data to migrate. Electronic Signatures' history will transfer with the associated projects.

For existing cloud instances with migrated projects

Select I don't intend to migrate projects and Users and groups only. In this case, the Electronic Signatures history for existing cloud issues will be migrated.

  1. Configure user and group migration according to your organizational needs. For additional details, see How Jira users and groups are migrated.

  2. Review any warnings or blockers identified by JCMA.

  3. Address critical issues before proceeding, or choose Continue and fix later for non-blocking warnings.

  4. Click Run to start the migration process.

  5. Monitor the progress on the Migration dashboard. Migration duration depends on data volume and system performance.

Result:

  • Projects become available on Cloud immediately after the project data migration completes.

  • Electronic Signatures history can take additional time to appear in issues, depending on the volume of migrated data.

How to verify the migration was successful

To confirm that your Electronic Signatures data migrated successfully by checking both the transferred signature records and the migration process logs.

To…

Do this:

To…

Do this:

Verify Electronic Signatures data integrity

  • Signature records: Check that signature records appear in migrated issues.

  • User mappings: Verify that signatories are correctly mapped to cloud users.

  • Timestamps: Confirm that signature dates and times are preserved.

Verify Electronic Signatures migration status

  1. Go to Jira Administration > System > Troubleshooting and support tools.

  2. On the Create support zip tab, click Customize zip.

  3. Select Jira application logs from the list.

  4. Download and review logs for the Electronic Signatures migration status.

Atlassian's migration reports don't include app-specific data, so manual log analysis is required to verify the Electronic Signatures migration status.

Post-migration steps

Due to platform architectural differences, workflow components require manual reconfiguration.

Validators

Electronic Signatures validators must be recreated in cloud workflows

Post functions

Cloud versions require different configuration parameters.

Workflow schemes

Must be reviewed and updated for cloud compatibility.

For detailed configuration steps, see the Workflow integration page.

Need support? Create a request with our support team.

Copyright © 2005 - 2025 Appfire | All rights reserved.