# Server to Cloud - Automatic Migration tool ## General information The automatic migration path for Email This Issue is available since version 9.3.0 in On-prem versions (the Cloud version is released at the same time of this version). It can be used to plan and execute migrations in test and production environments alike. {% hint style="info" %} #### Current limitations of the migration: * No filtering for project data is available. If you set it in the Jira Cloud Migration Assistant to only migrate certain projects, it will not be applicable to the Email This Issue configuration. * Email This Issue migration tool supports only full migration. All old data on Email this Issue Cloud side will be lost once the migration is done. * The migration of Mail Handlers is limited in its functionality. For more details see the [Finalize Migration in Cloud](https://docs.meta-inf.hu/email-this-issue/server-to-cloud-migration/server-to-cloud-automatic-migration-tool/finalizing-the-migration-in-cloud) section. * The Default event type will not be migrated, therefore this event type will be removed from the Notification events' Event Types list. If the Notification event was listening only on the Default event, the notification event will not be migrated at all. * Workflow post-function settings are not migrated at all. {% endhint %} {% hint style="danger" %} Important notice: The current recommended version for using the Automatic migration tool is 9.24.2.\ Unfortunately, at the moment, it’s not possible to reliably migrate from version 10.0.0 of the application.\ If you have already upgraded to a later version, we recommend downgrading the application to version 9.24.2 before starting the migration.\ Please note that if you have already created mail connections or OAuth credentials with Grant flow (Application access) you will need to delete the connections and credentials before the downgrade.\ Upgrading to version 10.0.4-GA or above doesn’t help in this case, because all Jira 11 compatible versions are currently blocked from the migration due to a problem on the Jira side.\ If you wish you can signal to Atlassian that this also affects you here: {% endhint %} The process of moving Email This Issue data from On-prem to Cloud instances can be divided to three main sections: {% hint style="danger" %} Important notice: The current recommended version for using the Automatic migration tool is 9.24.2.\ Unfortunately, at the moment, it’s not possible to reliably migrate from version 10.0.0 of the application.\ If you have already upgraded to a later version, we recommend downgrading the application to version 9.24.2 before starting the migration.\ Please note that if you have already created mail connections or OAuth credentials with Grant flow (Application access) you will need to delete the connections and credentials before the downgrade.\ Upgrading to version 10.0.4-GA or above doesn’t help in this case, because all Jira 11 compatible versions are currently blocked from the migration due to a problem on the Jira side.\ If you wish you can signal to Atlassian that this also affects you here: {% endhint %} The process of moving Email This Issue data from On-prem to Cloud instances can be divided to three main sections: * [Preparing Email This Issue for migration](https://docs.meta-inf.hu/email-this-issue/server-to-cloud-migration/server-to-cloud-automatic-migration-tool/preparing-for-the-migration) * [Using the Cloud Migration Assistant, affectively doing the migration](https://docs.meta-inf.hu/email-this-issue/server-to-cloud-migration/server-to-cloud-automatic-migration-tool/doing-the-migration) * [Post-migration configurations](https://docs.meta-inf.hu/email-this-issue/server-to-cloud-migration/server-to-cloud-automatic-migration-tool/finalizing-the-migration-in-cloud) ## On-prem to Cloud Migration support The below tables attempt to list the migration modes of Email This Issue features. :white\_check\_mark: **FULL** means that all data is automatically migrated during the process and needs only a check-up from the user when it's done. :wrench: **CORRECTION REQUIRED** means that the user should manually check and carry out additional configurations after the migration is done. :no\_entry: **NOT SUPPORTED** means that the features are not migrated at all. This is either due to them not being applicable to the Cloud platform or it is due to technological limitations. ### Configuration data
On-prem configurationCloud configurationMigration mode
OAuth2 CredentialsOAuth2 Credentials ✅ FULL
Outgoing Mail ConnectionOutgoing Mail Connection🔧 CORRECTION REQUIRED
Incoming Mail ConnectionIncoming Mail Connection🔧 CORRECTION REQUIRED
Next-Gen Mail HandlerMail Handler🔧 CORRECTION REQUIRED
TemplateEmail Template🔧 CORRECTION REQUIRED
WebhookWebhook ✅ FULL
NotificationsEmail Notification Schemes ✅ FULL
ContextManual Email Configuration🔧 CORRECTION REQUIRED
ContextAdvanced Email Configuration🔧 CORRECTION REQUIRED
Manual Email DefaultsManual Email Configuration🔧 CORRECTION REQUIRED
Canned ResponsesResponses🔧 CORRECTION REQUIRED
Distribution Lists ❌ NO SUCH CONFIGURATION ⛔ NOT SUPPORTED
Attachment Filters Attachment Filters⛔ NOT SUPPORTED
General ConfigurationAdvanced Email Configuration🔧 CORRECTION REQUIRED
General ConfigurationManual Email Configuration🔧 CORRECTION REQUIRED
General ConfigurationPermission Schemes ✅ FULL
Workflow post-functionWorkflow post-function⛔ NOT SUPPORTED
### Operational data | Server configuration | Cloud configuration | Migration mode | | ------------------------------------------- | :-----------------: | :---------------------------: | | Email log | Email Audit Log | :white\_check\_mark: **FULL** | | Outgoing Mail Queue (Mail Generation Queue) | Outgoing Mail Queue | :no\_entry: **NOT SUPPORTED** | | Incoming Mail Queue | Incoming Mail Queue | :no\_entry: **NOT SUPPORTED** | | Incoming Mail Log | Incoming Log | :no\_entry: **NOT SUPPORTED** |