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 :
Power Platform Community / Forums / Power Apps / How to migrate data fr...
Power Apps
Suggested Answer

How to migrate data from dataverse table to another environment with the original createdOn date?

(1) ShareShare
ReportReport
Posted on by 85
I did already a migration with the tool "Comon Data Service Configuration Migration" (pac tool cmt). I deployed the solution with 5 dataverse tables from environmentA to environmentB. I created first the schema and saved it in a specific folder on my machine. After that I exported the data to the same folder. At the end I imported this data to environmentB. When I look to the records in the dataverse tables I see in the createdOn column the date of the migration. I expect the original createdOn date like in my source dataverse table. How to fix this?
 
I have the same question (0)
  • Suggested answer
    Valantis Profile Picture
    6,735 on at
     
    The CMT tool doesn't preserve createdOn by default because createdon is a system-managed field that Dataverse always sets to the current timestamp on record creation. The tool doesn't override it during import unless you explicitly configure the schema to include it.
     
    To preserve the original createdOn date, you need to include the overridecreatedon attribute in your schema file and ensure the importing user has the right permissions:
     
    1. Open your schema.xml file in a text editor
    2. Find the entity definitions for your 5 tables
    3. Add the createdon field to each entity's field list if it's not already there
    4. In the CMT tool, when setting up the schema, look for the option to include createdon as a field to migrate
     
    Critical requirement: the user account used to import the data must have the prvOverrideCreatedOn privilege in their security role. Without this privilege, Dataverse ignores the createdon value even if you pass it. This privilege is included in the System Administrator role by default.
     
    If you're using pac data import via CLI, the same requirement applies: include createdon in the schema and ensure the auth user has the overridecreatedon privilege.
     
    After adding this, re-export from environmentA and re-import to environmentB. The original dates should be preserved.
     

     

    Best regards,

    Valantis

     

    ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

    ❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

    🏷️ For follow-ups  @Valantis.

    📝 https://valantisond365.com/

    💼 LinkedIn

    ▶️ YouTube

  • Suggested answer
    11manish Profile Picture
    3,333 on at
    If your goal is to migrate business data while preserving audit timestamps, the Configuration Migration Tool is not the right tool.
     
    It is intended for configuration/reference data migration and does not preserve system audit fields.
     
    Use KingswaySoft, a custom migration process, or another ETL tool that supports overriddencreatedon during record creation.

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 Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard