Dynamics Community Forum Thread Details

Can't preserve createdby migrating between two Dataverse environments — SSIS Toolkit v25.2

Migrating Account records from one Dataverse env (Dev) to another (UAT) using KingswaySoft SSIS Toolkit v25.2 (CRM Source → CRM Destination, Upsert on Primary Key, GUIDs preserved).

Separate environments, so users exist in both but with different systemuserid GUIDs.

createdon preserves fine — mapped source createdon into overriddencreatedon, works on fresh Create. Connection's app user has System Administrator (so the import override privilege is present).

For createdby, I set a Text Lookup on the field: Target entity systemuser, input createdbyname → target fullname, Smart Name Match on. Deleted existing UAT accounts first, then re-ran as fresh Creates.Result: Package succeeds, but Created By still shows the application user, not the original creator. Created On preserves correctly on the same run, so the create path and privilege work — only createdby isn't honored.

Questions:

Can createdby be set to a different user through the Destination component, or does the platform always stamp the calling user?

If yes, what am I missing — endpoint type (SOAP vs Web API), a destination option, a specific privilege?

If not possible via the component, is a pre-operation plugin on Create the only route?

Env: SSIS Toolkit v25.2.0.27301, Dataverse online (both), OAuth Client Credentials.

Categories:

Dynamics 365 general

In Dataverse, createdby is a system-controlled audit field and cannot be set during record creation through SSIS, Web API, SOAP, or plugins.

Even with KingswaySoft and System Administrator privileges, Dataverse will always stamp the calling user (service principal/app user).

createdby → Not editable on create (platform enforced)
createdon → Can be preserved using overriddencreatedon
Endpoint type (SOAP/Web API) → No impact
Pre-operation plugin → Not a reliable or valid solution

Why your current setup works partially

createdon works because Dataverse explicitly allows override with privilege
createdby does not because it is fixed at system level during insert

Instead of forcing createdby, use:

A custom field (e.g., Source Created By) to store original user
Optionally map source user identity (email/name) for reporting

You cannot set createdby directly in Dataverse during migration. The correct enterprise approach is to store original creator information in custom fields instead of system audit fields.

Quick Links

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