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

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

Can ‘Create By’ be Immigrated or Changed?

(0) ShareShare
ReportReport
Posted on by 1
I'm working on a Dataverse-based project. This project required me to migrate data from outside the Microsoft platform (e.g., salesforce) into Dataverse.

There are several fields that are difficult to handle in the data that need to be migrated: 'Modify By', 'Modify Date', 'Create By', 'Create Date'. These are the system data of Power Platform, and I have not found a way to modify these fields. Therefore the corresponding data cannot be placed in these fields. Is there any way to enter data into these fields?

What I do is download the old data in JSON format, then read the JSON via automate flow and add it into my prepared Dataverse table. However, data like 'Modify By', 'Modify Date', etc. will only be new custom columns instead of using the original system columns.
I have the same question (0)
  • Suggested answer
    Abdul Wahab Profile Picture
    12,112 Moderator on at
    Can ‘Create By’ be Immigrated or Changed?
    Data Import using Data Migration Tool (XRMToolBox / Configuration Migration Tool)
    Microsoft’s Configuration Migration Tool (part of SDK) allows preserving Created On and Created By under certain conditions.
    Similarly, some third-party migration tools (KingswaySoft, Scribe, etc.) can write into those fields because they use privileged APIs.
     
    Using “Override Created On”
    For the Created On field only, Dataverse provides an OverrideCreatedOn parameter in the SDK/API.
    This lets you set the Created On date when inserting records (but not Created By or Modified fields).
     
    Custom Columns (your current approach)
    If you don’t use migration tools with elevated privileges, then your approach (storing original values in custom columns like Legacy Created On, Legacy Modified By) is the standard solution.
    This preserves history for reporting/auditing while allowing Dataverse to continue managing its own system fields.
     
    Abdul Wahab
    Direct: +923323281237
    Email: abdulwahabubit@outlook.com
    LinkedIn: https://www.linkedin.com/in/abdul-wahab-a5b8b011a/
    Twitter: https://twitter.com/Abdulwahabubit
    GitHub: https://github.com/AbdulWahabWarind
    YouTube: https://www.youtube.com/channel/UCBjgLqLK_2kU-3bwo4McrTw

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

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

#1
DAnny3211 Profile Picture

DAnny3211 401

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 137 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 71 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans