CRM field ownership
Move one CRM field's authority at a time
Transferring ownership changes which edits win. Reconcile existing values and coordinate writers before enabling the new direction.
In this article
Agree the new authority
State which system will own the field, when the change takes effect and what users should do afterwards. Update the relevant interface or process so people do not keep editing a value that will be overwritten.
Identify every writer of the field, including imports and automation inside the CRM.
Keep the migration limited to a coherent field or group of related fields where possible. Moving every property at once makes conflicts harder to explain.
Compare existing values
Produce a controlled difference report and classify expected transformations, stale copies and genuine disagreements. Use the business owner to resolve ambiguous values.
Do not choose the newest timestamp automatically unless the policy explicitly supports that interpretation. A bulk import timestamp may be newer than the underlying information.
Record the chosen starting value and provenance for unresolved or manually reviewed cases.
Transfer writers under a controlled sequence
Stop the previous authoritative path for the field, enable the new one and verify a representative change. Prevent queued old events from reasserting the previous value after the switch.
Use source versions or an explicit transition boundary where the integration design supports it. A delayed event needs a known policy, not a guess based on arrival time.
Keep rollback behaviour clear. Returning authority to the previous system may require carrying back changes made under the new owner.
Verify the next scheduled cycle
Run or observe batch imports, CRM automation and reconciliation after the live switch. These can be the last hidden writers.
Check clearing, identity merges and conflict reporting under the new policy. Update documentation and support tools to reflect the new direction.
The migration is complete when users and every writer follow the same ownership model. A changed mapping file alone does not prevent the old business process from continuing to edit the field elsewhere.
Primary sources
Microsoft Dataverse: conditional operationsReferences checked 11 September 2026.