Fields on Import Set Staging Tables Should be String Even for Data Types Such as Date/Time, Reference, true|false and CurrencyIssue When importing data, the field containing the Date/time, Schedule Date/Time, Reference, true|false or Currency value should be Type String in the Import Staging (source) table. And should be the relevant Type, e.g Date/Time, Reference, true|false or Currency, in the Target table. Note that sometimes when importing from Data Sources like Excel spreadsheets or JSON (over the REST API) the import set staging table will automatically have fields created of Type Date/Time or Currency). This can cause issues and these fields on the Import Set Staging table should be changed to String using the Dictionary.Related LinksA few more tips for importing Date/time, Reference, true|false or Currency values: Reference field values should be imported as sys_id's if there's any chance there could be multiple records with the same Display Value in the target table. For example with Report[sys_report] records you can have multiple reports with the same Title (Title is Display Value for Report), so imports of fields that reference sys_report should use sys_idFor date fields the user doing the import also needs to have both their default timezone (Time zone[time_zone] on the User[sys_user] record for that user) and their current session timezone (click the 'cogwheel' icon and choose a timezone) set to match the timezone of the date/time values in the import file.For date fields you need to ensure that the Date Format field on the Field Mapping is correct. Click the lightbulb icon next to the field for examples, or see the official documentationFor fields of type Schedule Date/Time (e.g from the cmn_schedule_span table) the imported data should be a string in the format yyyy-MM-dd HH:mm:ss, e.g 2023-08-01 15:00:00.. That means the Import Staging table field type should be String. If importing from Excel the cell should be type Text, NOT Date.These are similar to DateTime values except there is no timezone component, and the database format is different. So once that example value is imported it will show as 15:00 1 Aug 2023 in the UI no matter what timezone you've set in your session, and doing Show XML you'll see it in this format (for the Start Date time field in this example): <start_date_time>20230801T150000</start_date_time> .