# Better control over data submitted in forms (prevent existing good data from being spoiled) **URL:** \ **Category:** Ideas and Feature Requests\ **Created:** [April 13, 2026, 11:39am UTC](https://forum.mautic.org/t/better-control-over-data-submitted-in-forms-prevent-existing-good-data-from-being-spoiled/38088 "2026-04-13T11:39:56Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![ekke](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ekke/32/296_2.png) [@ekke](https://forum.mautic.org/u/ekke)\ **Post date:** [April 13, 2026, 11:39am UTC](https://forum.mautic.org/t/better-control-over-data-submitted-in-forms-prevent-existing-good-data-from-being-spoiled/38088/1 "2026-04-13T11:39:57Z")
As discussed in today’s DACH online meetup: There are situations where known good data (e.g. from CRM, or at least DOI-verified submissions, maybe manually improved) should be protected from being overwritten by any form submission. Exact requirements and strategies vary, may include e.g. - _“no write to contact data before DOI”_ - _“extend that to progressive profiling / or not?”_ - _“improvement of data quality through external services”_ - _“company matching based on (DOI-confirmed) email domain”_ - _“catch duplicates even with different capitalization, typos, … yet support large enterprises with many similar subsidiaries, n:m contacts\<-\> companies relations, …”_ - _“capture submitted data only in form submit data, allow transferring that to the contact later”_ - _“option for manual review & approval”_ My idea is: - create more complete picture of possible scenarios, i.e. requirements and strategies (also: what do other systems do?) - come up with a basic feature set for implementation within Mautic (and implement that) - provide guidelines for more flexibility (and achieving more sophisticated things) though external middleware, e.g. n8n