Issue Summary

During migration, the datepicker field in the database has the correct date, but the exported changegroup JSON shows the date as one day earlier. This means changegroup is exporting the wrong (previous) date.

The date isn’t saved with timezone info, so during export, it shows as one day earlier. This causes incorrect dates in migrations and customers may see wrong historical data

Steps to Reproduce

1. Create an issue with a datepicker custom field set to a specific date (e.g., 26-05-2025).
2. Perform a migration.
3. Inspect the exported JSON for the changegroup entity.
4. Observe that the date for the datepicker field is one day earlier than expected.

Expected Results

The exported history value for the datepicker custom field value UI (e.g., 26-05-2025).

Actual Results

The exported history value is one day earlier than the actual custom field value (e.g., 25-05-2025).

Workaround

Currently there is no known workaround for this behavior. For further assistance, you can Contact Support.