Issue Summary

It seems that JCMA currently exports the created date from the server database and migrates it as is without validating whether the date is correct. For example, created dates from the beginning of the millennium, like 0095 or 0023, are migrated to the cloud as is without validation of their correctness. The same dates from the Due date field get migrated correctly. 

This is reproducible on Data Center: 

Steps to Reproduce

1. Create a JIRA issue, and then update the year to 1995 for both the creation and due dates using an update query(jiraissue table).
2. When the project is migrated, the year in the creation date appears correctly on the UI; however, the JSON file displays an incorrect year, such as "created": "0095-06-25T11:43:38.793+0000."
3. Use the endpoint https://sitename.atlassian.net/rest/api/2/issue/issueKey to retrieve the JSON.

Expected Results

"00YY" should be replaced with "YYYY" format, similar to the Due Date field, or the created date should be replaced with the migrated day date(like CSV import).

Or, Identify these kinds of date during the data preparation and throw the error so that the user can correct it in the server database.

Actual Results

The date is migrated in 00YY format, such dates can't be processed by the app vendor's app.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available