Email This Issue
📈 Marketplace❓ Support❤️ Feedback🏠 META-INF Apps
Email This Issue - for Jira Cloud
Email This Issue - for Jira Cloud
  • ⬇️Overview
  • Email This Issue - for Jira Cloud
  • Features
  • How Email This Issue Works
  • Secure the email channel with Email This Issue
  • Comparing Email This Issue and Jira Cloud
  • 📤Outgoing Emails
    • Outgoing emails overview
    • Manual emails
      • Configuring manual emails
      • Sending manual emails
    • Email notification schemes and email notifications
    • Workflow post functions
    • Advanced email configuration
    • Customizing email templates
    • Canned Responses (default messages)
    • Scope evaluation
  • 📥Incoming Emails (Mail Handlers)
    • Incoming emails overview
  • Mail handlers - adding / editing
    • General handler settings
    • Filtering
    • Finding issues
    • Setting up rules and actions in the actions editor
      • Adding/editing actions
      • Adding recipients to Request Participants
      • Creating an issue
      • Updating an issue
      • Setting field values
      • Adding comments
      • Sending auto-reply emails
      • Executing workflow transitions
      • Creating a customer
      • Using split regexp
      • Conditions
      • Approve request
      • Decline request
    • Maintaining email chains
    • Mail Handler New UI
  • Global Sender Address Filters
  • Attachment Filters
    • Regular Attachment Handling Deprecation
  • 🤓Administration
    • Outgoing Mail Connections
    • Alerting via Webhooks
      • Webhooks
        • Configuring Slack to receive alerts via webhooks
        • Configuring OpsGenie to Receive alerts via webhooks
        • Configuring Microsoft Teams to receive alerts via webhooks
      • Webhook execution logs
    • Mail Queue
    • Email Audit Log
    • Permissions
    • Recipient Restrictions
    • Incoming Mail Connections
    • Email Security
    • Incoming Mail Queue
    • Incoming Mail Log
    • OAuth2 Credentials
      • Enabling OAuth2 Authorization in your Google Account
      • Enabling OAuth2 Authorization in your Microsoft 365 Account
      • Troubleshooting guides for Microsoft OAuth2 Connections
        • How to fix "BAD User is authenticated but not connected" error​
        • How to fix "401 Unauthorized" error
        • How to fix "key expires_in " error
        • How to fix "Need admin approval" error
  • ☁️Server to Cloud Migration
    • 🛫Server to Cloud - Automatic Migration tool
      • Preparing for the migration
      • Doing the migration
      • Finalizing the migration in Cloud
      • Migration with unsupported Jira versions causes errors
    • Server to Cloud - Manual migration guide for Email This Issue
  • ❓FAQ
    • No recipients error in outgoing emails
    • How-to add custom macro to email Template?
    • Why cannot I select custom event types in notification?
    • How to configure the Email This Issue addon user in Jira Cloud?
    • I get an error: Could not create request on behalf of the sender
    • Why is the Incoming Mail Queue size limited?
    • Outgoing mail not sent - Read timeout error
    • Access restriction icon is not appearing when adding internal attachments via Email this Issue
  • 🌪️General
    • Release Notes
    • API
      • API for Velocity Context Objects - 1.7
      • API for Velocity Context Objects
    • Addon Pages
      • Integrity Check
      • Feedback and Support
    • Security Advisories
      • Email This Issue Security Advisory September 28, 2020
    • Appendix
      • Supported Time Zones
    • Integration of Glass Documentation
Powered by GitBook
On this page
  • On-premise prepare steps
  • Cloud-side preparation

Was this helpful?

  1. Server to Cloud Migration
  2. Server to Cloud - Automatic Migration tool

Preparing for the migration

PreviousServer to Cloud - Automatic Migration toolNextDoing the migration

Last updated 1 year ago

Was this helpful?

There are two parts of preparing for the migration:

It is essential that you follow the process carefully and not miss any of the steps. If at any time you run into problems, reach out to our and send us as much information as possible, including screenshots and an explanation of what happened.

On-premise prepare steps

1. Download and install the latest version of Email This Issue.

2. Remove any configuration that you don’t want to migrate to the cloud.

3. Disable every Incoming Mail Connection.

After you start the migration, all new incoming emails (both created with Jira and/or with Email This Issue that you would process with Email This Issue on the On-prem version) and their processed data will not be migrated to the Cloud as the process is already running.

If you have Incoming Mail Connection created with Jira it should be disabled as well.

4. Clean up your Incoming Mail Queue

Check if there are any important emails in the Filtered out or Failed incoming mail queues. If you need those emails, make sure to requeue them before the migration.

After this, wait for the New and Being processed queues to become empty. These steps assure that these emails will be migrated as well.

5. Prepare incoming mail accounts

All emails that you do not want to be processed later in Cloud should be moved out or removed from the mail account folder that is used by Email This Issue for incoming emails. By default, this folder is called “INBOX”. To check if your Incoming Mail Connections are using custom folder settings you should look for the Folder option:

After the migration when incoming mail connections are enabled in the Cloud, all emails will be downloaded from the mail accounts regardless of being read or unread. If the mail account folders used by the connections are not cleared, it may lead to duplicate issues and comments.

6. Set email audit log migration period

Optionally, you can set the time frame from when the audit log items should be migrated. The default time frame is to migrate from the last 1 month.

  1. Navigate to the Email Log in the Email This Issue administration settings

  2. Click on Save settings

Cloud-side preparation

The migration tool will delete all existing data from Email This Issue Cloud by the end of the migration.

All these preparations are required to avoid data loss or duplication on the Cloud side of Email This Issue.

1. Make sure Email This Issue is installed and has a valid license on your target Cloud instance.

2. Disable every Incoming Email Connection

New emails will not be downloaded while this migration is in progress. Otherwise, these emails could be lost.

3. Clean up your Incoming Mail Queue

Check if there are any important emails in the Skipped or Error incoming mail queues. If you need those emails, make sure to requeue them before the migration.

After this, wait for the Active and Processing queues to become empty. These steps assure that these emails will be migrated as well.

4. Prepare incoming mail accounts

All emails that you do not want to be processed in Cloud should be moved out or removed from the mail account folder that is used by Email This Issue for incoming emails. By default, this folder is called “INBOX”. To check if your Incoming Mail Connections are using custom folder settings you should look for the Folder option:

5. Enable data migration to your Cloud instance in Email This Issue

This process can take a few minutes to complete, and there is no confirmation of its success.

To enable data migration, navigate to Email This Issue Administration - Migration Options:

Click on Migration then select the time frame that fits your needs from the Migrate from the last select list.

☁️
🛫
support team
On-prem prepare steps
Cloud-side preparation
Disabling Incoming Mail Connections created with Email This Issue on the On-Prem version
Incoming mail queue before cleanup
Incoming mail connection - Folder option
Disabling incoming mail connections in the Cloud version
Incoming mail queue before cleanup
Incoming mail connection - Folder option
Enabling data migration setting in Cloud