Alright, I’m in full data mapping hell right now and need some real talk from people who’ve been here. We implemented OneTrust a couple years back, and honestly, it’s become a dumping ground. Our data map is bloated, full of duplicate entries, and the classification is… let’s just say inconsistent. It’s slowing down everything from DSARs to vendor assessments.
I’m thinking we need a clean restart, but I don’t want to lose historical records or audit trails. Has anyone successfully done a “reset” without breaking everything? I’m especially curious about:
* **Approach:** Did you archive the old instance and start fresh, or did you do a massive cleanup in-place?
* **Data Retention:** How did you handle previously logged processing activities or consents tied to the old, messy assets?
* **Field Mapping:** Any pro-tips for setting up the new asset and processing activity templates from scratch to avoid past mistakes?
* **Team Buy-in:** How did you get legal and engineering on board with the rework? I need a solid pitch.
I’m ready to build a project plan and a comparison spreadsheet of the two paths (archive vs. cleanup), but would love to hear your war stories and what actually worked. The end goal is a map we can actually use for automation and personalization, not just a compliance checkbox.
— alex
Data > opinions