web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Preserve Created On date when migrating data using xmltoolbox data transporter

(0) ShareShare
ReportReport
Posted on by 4
Hello,
 
I want to migrate data from one dynamics 365 environment to another.
 
I've managed to migrate some sample data fine.  However, I would like to preserve the Created On date from the source environment to the target environment.
 
I can see a field called overridecreatedon but it's greyed out and not valid for update.
 
Thanks in advance!
 
M
Categories:
I have the same question (0)
  • Suggested answer
    Websrider Profile Picture
    2 on at
    This is expected behavior in D365. The Created On field is a system-managed field and can not be directly updated after a record is created.
     
    The Override Created On field can only be populated during RECORD CREATION, not during an UPDATE.
     
    Create Scenario: Map Source createdon field to Target overriddencreatedon and ensure you are creating the record not updating.
     
    Update Scenario: If you have record already there in target system, then you can't not update createdon and  overriddencreatedon field. in this case, create a custom field and map source created on to the custom field i.e. originalcreatedon for the reporting purpose. for all the existing records get the created on data from this field and newly created records will keep this field blank.
     
    Hope, this will help you. 
  • MR-21071937-0 Profile Picture
    4 on at
    Thanks for the response - makes sense.
     
    How do I map Source createdon field to Target overriddencreatedon? The Data Transporter tool doesn't display the createdon field and I can't see how to map one field to another anywhere.
     
    Kind regards,
    MR
  • Verified answer
    Assisted by AI
    Riazux Profile Picture
    19 on at

    Created On is a system-managed field in Dynamics 365/Dataverse and cannot be updated after the record is created.

    To preserve the original Created On date during migration, the source createdon value needs to be mapped to the target overriddencreatedon field during record creation. Dataverse will then populate the actual createdon value from overriddencreatedon.

    If you are using XrmToolBox Data Transporter and it does not expose createdon for mapping, then Data Transporter may not support this scenario directly. You would need to use another migration approach/tool that allows mapping system fields during create operations, such as Configuration Migration Tool, KingswaySoft, SSIS, or Dataverse Web API.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 57

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 41 Super User 2026 Season 1

#3
sannavajjala87 Profile Picture

sannavajjala87 25

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans