Why the date resets
Salesforce stamps CreatedDate with the moment of insert, so every legacy record looks as if it was created on migration day. That breaks any reports on sales cycle length, cohorts or lead age. The fix is a pair of permissions Salesforce made for migrations.
Steps
- In Setup > User Interface, tick Enable “Set Audit Fields upon Record Creation” and “Update Records with Inactive Owners” User Permissions.
- Create a permission set that grants Set Audit Fields upon Record Creation, and Update Records with Inactive Owners if former employees still own records. Assign it to the user who runs the load. Standard profiles can’t receive these permissions.
- Create every user first, including inactive ones.
CreatedByIdandOwnerIdmust be user IDs in the target org. - Format the dates in your CSV as Data Loader expects (ISO 8601 with a time zone, for example
2019-03-04T09:30:00Z). - Insert (not update) and map
CreatedDate,CreatedById,LastModifiedDateandLastModifiedById. - Spot-check a sample, then disable the permission.
What the native tool does / where it stops
| Need | Native support | Limit |
|---|---|---|
| Created/modified date and user on records | Audit fields, on insert | Can’t be applied afterwards; Professional Edition needs API access first |
| Records owned by people who have left | ”Update Records with Inactive Owners” | The users have to exist in the org |
| Task and event dates | ActivityDate and the event start/end fields | Audit fields still apply for the created date |
| Email dates | MessageDate on EmailMessage, insert via API only | Status has to be set in a separate update |
| Field history (who changed what, when) | None | Salesforce can’t import field history; store it in a custom object or an archive |
The last row catches teams out. Salesforce can take a record’s created date, but not the history of every change to its stage or owner. If you report on stage duration, migrate the stage history as its own custom object, or calculate the durations before the move and store them on the record.
Where FlitStack AI fits
FlitStack AI preserves timestamps by default: it creates users first, writes audit fields on insert and keeps the original dates on activities. See the Salesforce Data Loader guide or talk to us.