---
title: "Keep original created dates when importing to Salesforce"
description: "Enable Set Audit Fields upon Record Creation, grant it by permission set, and write CreatedDate on insert with Data Loader. Limits and activity dates."
url: "https://flitstack.ai/answers/keep-created-dates-importing-into-salesforce"
---

# How do I keep original created dates when importing legacy CRM data into Salesforce?

Short answer

Turn on "Set Audit Fields upon Record Creation" in Setup > User Interface, and grant the permission through a permission set. Then map the legacy dates to CreatedDate and CreatedById in Data Loader. It works only when a record is created, not on update. For activities, also set ActivityDate on tasks and MessageDate on EmailMessage.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Ask us about your migration ](https://flitstack.ai/contact) [Read the full guide →](https://flitstack.ai/guides/salesforce-data-loader)

## 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

1. In **Setup > User Interface**, tick *Enable “Set Audit Fields upon Record Creation” and “Update Records with Inactive Owners” User Permissions*.
2. 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.
3. Create every user first, including inactive ones. `CreatedById` and `OwnerId` must be user IDs in the target org.
4. Format the dates in your CSV as Data Loader expects (ISO 8601 with a time zone, for example `2019-03-04T09:30:00Z`).
5. **Insert** (not update) and map `CreatedDate`, `CreatedById`, `LastModifiedDate` and `LastModifiedById`.
6. 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](https://flitstack.ai/guides/salesforce-data-loader) or [talk to us](https://flitstack.ai/contact).

![Aditya Kumar](https://flitstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://flitstack.ai/about/aditya-kumar)

Founder, FlitStack AI

Aditya Kumar is the founder of FlitStack AI and Jetstack AI, both built at Ambrstack. FlitStack AI migrates CRM and business data between platforms; Jetstack AI is the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about CRM data, migrations, HubSpot architecture and automation from the work of building them.

[More from Aditya](https://flitstack.ai/about/aditya-kumar) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

On this page

Questions, answered

## A few useful answers.

Can I fix created dates on records I've already imported?

Not by updating them. Salesforce allows audit fields only on record creation. You have to delete the records and insert them again with the dates. Keep the other records that point to them in mind, because their lookups will break.

Can I set LastModifiedDate too?

Yes. The permission covers Created By, Created Date, Last Modified By and Last Modified Date, still only on insert. SystemModstamp can't be set.

Should we leave the permission switched on?

No. Salesforce advises enabling it only for as long as you need it and then disabling it. Grant it to the integration user for the migration window only.

## Related

### [Salesforce Data Loader vs Data Import Wizard vs dataloader.io: which should you use?](https://flitstack.ai/guides/salesforce-data-loader)

[Read →](https://flitstack.ai/guides/salesforce-data-loader)

### [Migrate to Salesforce](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

[Read →](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

### [HubSpot to Salesforce migration](https://flitstack.ai/migrations/crm/hubspot/to/salesforce-sales-cloud)

[Read →](https://flitstack.ai/migrations/crm/hubspot/to/salesforce-sales-cloud)

## Sources

1. [Salesforce Help: Enable 'Set Audit Fields upon Record Creation' and 'Update Records with Inactive Owners'](https://help.salesforce.com/s/articleView?id=000386699\&language=en_US\&type=1)
2. [Salesforce Help: Audit fields can only be set on record creation](https://help.salesforce.com/s/articleView?id=000385636\&language=en_US\&type=1)
3. [Salesforce Help: Insert EmailMessage records with Data Loader](https://help.salesforce.com/s/articleView?id=000380515\&language=en_US\&type=1)
4. [Marketo Nation: moving legacy records into Salesforce with Set Audit Fields](https://nation.marketo.com/t5/product-discussions/how-to-update-people-in-marketo-with-salesforce-id-values/m-p/49479)

A closer look

## Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

[Get a quote](https://flitstack.ai/contact)
