Migration with CCMA shows incorrect timezone after migration

Issue Summary

When migrating Space using CCMA, the create/update Date and Time show time differential depending on time from Server. For example, when migrating a newly created test page, instead of showing ~4 minutes in Confluence Cloud, the time shows 4 hours. This appears to be due to the fact that the server setenv.sh has been configured with the value: 

-Duser.timezone=America/New_York

Steps to Reproduce

1. Configure setenv.sh with the value:

-Duser.timezone=America/New_York

according to KB: Set the timezone for the Java environment

1. Create a new test page
2. Migrate Space with test page using CCMA

Expected Results

The migrated Cloud Space should contain the page and reflect create/update time accurately

Actual Results

If the page was created at 1 pm NY time, it becomes created at 1pm GMT in the Cloud

Workaround

Removing the manual configuration (Duser.timezone) in setenv.sh appears to eliminate the problem