Skip to main content
All CollectionsMigrateHelp me solve thisMigration Errors
The time zone at the destination is not the same as the source
The time zone at the destination is not the same as the source
Updated over 2 weeks ago

Symptoms

When copying an object. Sharegate displays the following warning:

The time zone at the destination is not the same as the source. The date and time values will keep the same moment in time. The value displayed in the browser might be different.

Error code

  • AN-048-195

  • AN-049-195

Details

When the source object and the destination object do not have the same timezone settings, the date and time may not match that of the destination.

ShareGate Migrate does not correct the value of the timezone to match the actual time at the destination. Doing that would corrupt the value which is problematic, especially if you need the date or time for auditing purposes.

If you only have a date set, the time is automatically set to midnight. Once migrated at the destination, it is possible that the value displayed is plus or minus a day if the destination timezone has a lower or greater offset. As an example:

  • If the source timezone is UTC and the destination is UTC+6. 2/23/2015 20:00 will become 2/24/2015 2:00 at the destination.

  • If the source timezone is UTC and the destination is UTC-6. 2/23/2015 5:00 will become 2/22/2015 23:00 at the destination.

Verify the regional settings of your source and destination sites to make sure they match.

Go to Site settings in your site, then select Regional settings.

Note: Regional settings are applied on individual sites. This means that you could have subsites with different regional settings within the same site collection.

Did this answer your question?