Skip to content
Get a quote

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.

By

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

NeedNative supportLimit
Created/modified date and user on recordsAudit fields, on insertCan’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 datesActivityDate and the event start/end fieldsAudit fields still apply for the created date
Email datesMessageDate on EmailMessage, insert via API onlyStatus has to be set in a separate update
Field history (who changed what, when)NoneSalesforce 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.

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.

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