What measures support data integrity during merges or version changes?

• A. Delete old data during merges to avoid conflicts
• B. Disable versioning
• C. Use locked fields, versioned templates, reconciled data with migration steps, and audit trails
• D. Rename templates to reflect changes without migration

Answer: (C)

Maintaining data integrity during merges or version changes hinges on implementing coordinated controls and traceability. Locked fields prevent edits on key data during a merge, so values stay consistent and conflicts don’t creep in. Versioned templates provide a clear record of how forms and rules have evolved, ensuring changes to structure or behavior don’t silently disrupt data relationships. Reconciled data with migration steps ensures old records are accurately transformed to fit new versions, preserving meaning and connections. Audit trails capture who changed what and when, offering a reliable way to review, diagnose issues, and rollback if needed. Together, these measures minimize data loss, mismatches, and ambiguity during changes. Deleting old data, disabling versioning, or renaming templates without migration would undermine integrity by removing history, losing change control, or failing to map data properly.