Issue Summary

When migrating Jira projects from Server to Cloud "Due date" value gets changed to 1 day less than that of the source and all other date field of Jira issue get changed according to the timezone

Steps to Reproduce

1. Create a Jira Server instance with a timezone, for example, GMT+01:00
2. Configure "Due date" on this server instance and create issues using this field
3. Create a Jira Cloud instance with a different timezone, for example, GMT+00:00
4. Migrate the Jira project from the server to the destination cloud site using Migrate all data at once option in JCMA
5. We will see the Due date for the Jira issue is created 1 day less than that of the server.

Expected Results

Migrated issues on the cloud have the same "Due date" as that of the source server instance

Actual Results

Migrated issues on the cloud have "Due date" 1 day less than that of the source server

Workaround

• Stop Jira Server
• Change the Jira Server timezone, by Setting the timezone for the JAVA environment to UTC 

  -Duser.timezone=UTC 

• Start Jira
• Migrate the project