---
title: "ES - Migration from Server/DC to Cloud"
canonical: "https://support.appfire.com/space/ESF/17498411/ES%20-%20Migration%20from%20Server%2FDC%20to%20Cloud"
format: markdown
---
> Macro (aura-html)

  


> ℹ️ This page describes how to migrate Electronic Signatures data from Server/DC to Cloud.
> ℹ️ 
> ℹ️ Migration between Server or Data Center instances is available starting with version 3.1.2-jira8 and above using [Configuration Manager for Jira](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview) app. Use [Project Snapshot](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82779727) to migrate Electronic Signatures history, Logged User Validator and User validator custom fields, validator and post function, and [System Snapshot ](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82777327)to migrate Electronic Signatures Configuration page.

## <span style="color: #003366">Introduction</span>

<span style="color: #003366">Electronic Signatures app is a powerful tool to prevent unauthorized actions on Jira issues and save your data. We realize that no changes should ruin your compliance with the FDA regulation CFR 21 part 11. That's why we're doing our best to make your path from Server / Data Center to Cloud easy and smooth. You should not worry about losing your data due to moving to a new environment. In cooperation with the free Atlassian plugin, we ensure a fast and robust mechanism to move your electronic signatures to the cloud instance. No extra effort or cost.</span>

<span style="color: #003366">Electronic Signatures Server vs Cloud</span>  


### <span style="color: #003366">Differences in Electronic Signatures Server and Cloud</span>

<span style="color: #003366">We're working hard to ensure the most similar functionality in Cloud as you're used to seeing in Server. But there are some differences due to the absolutely different architecture between Server and Cloud.  The good news is core functions and usability are the same.</span>  
  


> ℹ️ <span style="color: #003366">Due to different architecture between Server and Cloud Jira versions, the app functionality is not totally the same. See more in the comparison table</span><span style="color: #091e42"> </span><span style="color: #091e42">[here](https://appfire.atlassian.net/wiki/spaces/ESF/pages/17498144/ES+-+FAQ#CanIexpectthattheCloudversionhasthesamefunctionalityastheServerversion?)</span><span style="color: #091e42">.</span>

###   
<span style="color: #003366">What data is migrated?</span>

<span style="color: #003366">We provide the ability to migrate the full history of executed electronic signatures. Records from the Electronic Signatures tab will be available on your cloud site as you're used to seeing them in Jira server.</span>

  


## <span style="color: #003366">Prerequisites for migration</span>

1. <span style="color: #003366">Your Jira instance runs on version 8.14 or above.</span>
2. <span style="color: #003366">Your version of the Electronic Signatures plugin is 3.0.6-jira8 or above.</span>
3. <span style="color: #003366">You've looked through Atlassian's</span><span style="color: #333333"> </span><span style="color: #333333">[documentation](https://confluence.atlassian.com/cloud/use-the-jira-cloud-migration-assistant-to-migrate-from-server-to-cloud-993925215.html)</span><span style="color: #333333"> </span><span style="color: #003366">about a</span><span style="color: #333333"> </span><span style="color: #333333">[Jira Cloud Migration Assistant.](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?hosting=server&tab=overview)</span><span style="color: #333333"> </span>
4. <span style="color: #003366">You are a Jira admin.</span>

  


## <span style="color: #003366">Before migrating</span>

1. <span style="color: #003366">Install </span><span style="color: #003366">[Electronic Signatures](https://marketplace.atlassian.com/apps/1211601/electronic-signatures?hosting=cloud&tab=overview)</span><span style="color: #003366"> plugin or </span><span style="color: #003366">**re-install **</span><span style="color: #003366">it if you already have it on your Jira Cloud site. You have to re-install the app only once, before your first Electronic Signatures app migration. </span>
2. <span style="color: #003366">On Server, enable feature flags for app migration in the server instance of Jira. Use the following link </span><span style="color: #003366">**<Jira_URL>/secure/SiteDarkFeatures!default.jspa**</span><span style="color: #003366"> and add </span>`com.atlassian.jira.migration.app-migration.feature `<span style="color: #003366">to Site Wide Dark Features if it is absent.</span>  
  
> Macro (inline-media-image)
3. <span style="color: #003366">**Default Loggers**</span><span style="color: #003366"> section click </span><span style="color: #003366">**Configure logging level for another package**</span><span style="color: #003366"> and add necessary packages with Track level:</span>
  - `ru.andreymarkelov.atlas.plugins.cfr.listener.CloudMigrationProcessListener`
  - `ru.andreymarkelov.atlas.plugins.cfr.service.CloudMigrationService`

  


  


## <span style="color: #003366">Migration process</span>

<span style="color: #003366">When all prerequisites are met, you are able to migrate your data from Server/DC to Cloud. </span>

<span style="color: #003366">Steps to follow to migrate from Jira Server or Data Center to Jira Cloud:</span>

1. <span style="color: #003366">To migrate data, go to </span><span style="color: #003366">**Jira Administration**</span><span style="color: #003366"> settings in Jira Server → </span><span style="color: #003366">**System **</span><span style="color: #003366">→</span><span style="color: #003366">** Import and Export **</span><span style="color: #003366">section→</span>**<span style="color: #003366"> Migrate to cloud.</span>**  
  
> Macro (inline-media-image)
2. <span style="color: #003366">Select </span><span style="color: #003366">**Assess and Install apps**</span><span style="color: #003366"> and mark the Electronic Signatures app as </span><span style="color: #003366">**Needed in cloud**</span><span style="color: #003366">.</span>  
  
> Macro (inline-media-image)
3. <span style="color: #003366">Perform steps according to Assessment wizard.</span>  
  
> Macro (inline-media-image)

  
<span style="color: #003366"> </span>
4. <span style="color: #003366">Go to</span><span style="color: #003366">** Manage your migration**</span><span style="color: #003366"> and click </span><span style="color: #003366">**Create new migration**</span><span style="color: #003366"> button.</span>
  
5. <span style="color: #003366">On the next page, you may find a short Atlassian explanation about the migration steps. Click </span><span style="color: #003366">**Connect to cloud**</span><span style="color: #003366"> to continue.</span>
  
6. <span style="color: #003366">Specify the </span><span style="color: #003366">**name**</span><span style="color: #003366"> of migration and your </span><span style="color: #003366">**cloud site**</span><span style="color: #003366">, so that to connect your Server and Cloud instances.</span>  
  
> Macro (inline-media-image)
  
7. <span style="color: #003366">Depending on whether the appropriate projects already exist in the cloud, choose which data to migrate. You can transfer Electronic Signatures plugin data </span><span style="color: #003366">**during**</span><span style="color: #003366"> or </span><span style="color: #003366">**after**</span><span style="color: #003366"> </span><span style="color: #003366">**the project migration**</span><span style="color: #003366">. </span>  
  
> Macro (inline-media-image)
  
8. <span style="color: #003366">You can choose to migrate all or some of your projects. You won’t be able to migrate projects with project keys that already exist in your Jira Cloud destination site.</span>
  
9. <span style="color: #003366">Choose how you want to migrate users and groups.</span> [Learn more about user and group migration.](https://confluence.atlassian.com/cloud/migrating-users-and-groups-1018767732.html)
  
10. <span style="color: #003366">Make sure you marked the Electronic Signatures app as Needed in cloud to migrate the application data.</span>
  
11. <span style="color: #003366">In the next step, Jira Cloud Migration Assistant will perform checking and notify you if there are any warnings or blockers for migration data from Server to Cloud.</span>
  
12. <span style="color: #003366">Carefully read and evaluate all the warnings, if any, before starting the migration. If you decide to </span><span style="color: #003366">**Continue and fix later**</span><span style="color: #003366">, you can come back to view the errors once you have saved your migration.</span>
  
13. <span style="color: #003366">After you click </span><span style="color: #003366">**Run**</span><span style="color: #003366">, the process will start and you will be able to see progress and migration status on the Migration dashboard. It takes some time, depending on your data size.</span>
  
14. <span style="color: #003366">You can view the project on your cloud site as soon as all the project data is migrated. </span>
  
15. <span style="color: #003366">Currently, Atlassian's logs migration reports do not include information about plugins' data. We recommend downloading and checking Jira logs manually. To check Jira logs, go to </span><span style="color: #003366">**Jira Administration**</span><span style="color: #003366"> → </span><span style="color: #003366">**System**</span><span style="color: #003366"> →  </span>**<span style="color: #003366">Troubleshooting and support tools.</span>**  
  
> Macro (inline-media-image)
16. <span style="color: #003366">On Create support zip tab</span><span style="color: #003366">**, **</span><span style="color: #003366">click</span><span style="color: #003366">** Customize zip **</span><span style="color: #003366">and select from the list </span><span style="color: #003366">**Jira application logs**</span><span style="color: #003366">.</span>  
  
> Macro (inline-media-image)
17. <span style="color: #003366">In the downloaded file, you can find information about the migration result.</span>  
  
> Macro (inline-media-image)

  


  


## <span style="color: #003366">After migrating</span>  
  


> ⚠️ <span style="color: #003366">Note, due to Jira Cloud Migration Assistant plugin</span><span style="color: #172b4d"> </span><span style="color: #172b4d">[limitations](https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html)</span><span style="color: #172b4d"> </span><span style="color: #003366">some data can't be migrated for now. We do monitor Atlassian's updates and will improve the migration of Electronic Signatures app as soon as the limitations are gone.</span>

###   
<span style="color: #003366">What you have to consider to keep enjoying Electronic Signatures plugin and stay safe in a new environment:</span>

- <span style="color: #003366">Electronic Signatures validator and post function can't be migrated and their purposes are slightly different in cloud. Read our</span> [documentation](https://appfire.atlassian.net/wiki/spaces/ESF/pages/17498501) <span style="color: #003366">carefully and reconfigure them.</span>
- <span style="color: #003366">Migrated history of signatures does not contain names of Electronic Signatures custom field (User Validator, Logged User Validator fields) as they are not available in cloud.</span>

  


<span style="color: #003366">If you have any questions or need assistance, contact the Anova Apps Products team at</span><span style="color: #172b4d"> </span><span style="color: #172b4d">[anovaproducts@appfire.com](mailto:support@appfire.com)</span><span style="color: #333333"> </span><span style="color: #003366">or visit our</span><span style="color: #333333"> </span><span style="color: #172b4d">[Service Desk](https://anovaapps.atlassian.net/servicedesk/customer/portal/2)</span><span style="color: #333333"> </span><span style="color: #003366">.</span>