When using Salesforce Data Loader to insert, update, or upsert records that include DateTime fields, you may encounter the following error:
Error converting value to correct data type: Failed to parse date: 1999-01-01T23:01:01+01:00
This error occurs when the DateTime value in your CSV file includes a timezone offset formatted with a colon separator (e.g., +01:00). While this format is valid for the Salesforce SOAP and Bulk APIs, Salesforce Data Loader has its own internal parser with unique formatting requirements that differ from the general API specification.
Although Salesforce API documentation lists 1999-01-01T23:01:01+01:00 as an acceptable DateTime format, Data Loader cannot parse the colon in the timezone offset portion. You must use one of the Data Loader-specific supported formats described in the Resolution section below.
For a full reference of valid DateTime formats accepted by the Salesforce APIs (not Data Loader), see the Additional Resources section.
Data Loader has its own set of supported DateTime formats that differ from the broader Salesforce API specification. For the specific example used in this article, the value 1999-01-01T23:01:01+01:00 must be reformatted using one of the following two approaches:
Option 1 — Remove the colon from the timezone offset:1999-01-01T23:01:01+0100
Option 2 — Use the GMT prefix format:1999-01-01T23:01:01GMT+01:00
Both formats are accepted by Data Loader and resolve the "Failed to parse date" error. For a complete reference of all DateTime formats supported by Data Loader, refer to the Data Types Supported by Data Loader article in the Additional Resources section below.
Data Types Supported by Data Loader
Format the Date and Date Time Data in a CSV File
Valid Date Format in Records — Bulk API
000383025

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.