Duplicate operator records after CRM migration
Ticketclosed
Penmaen Software · Duplicate operator records after CRM migration
CRM migration created duplicate operator records after field was renamed. Root cause was old and new field names both being indexed. Resolved by removing old records.
What happened
What this says
As at Fri 9 Oct 2026CRM migration created duplicate operator records after field was renamed. Root cause was old and new field names both being indexed. Resolved by removing old records.
Problem: Ffion reported duplicate operator records affecting metric accuracy during a critical board review period. She traced the issue to a Salesforce operator field rename during CRM migration. Handling: Bethan identified that both old and new field names were indexed, creating duplicates. She removed the old records and reindexed with only the new field. Watch: Data quality issues undermining critical business reporting pose a renewal threat.
Details
Updated 9 Oct 26Trail
created · Ffion Rees 10 Jul 2026 13:46Hi, we're seeing duplicate records for some of our operators in the brain. It looks like a few of them have been duplicated with different IDs, which is throwing off our metrics and making the dashboards show inflated counts. This is affecting our ability to trust the data and we need it sorted fairly urgently - we're reviewing operator performance with our board this week. Thanks, Ffion- Public reply · Bethan Lister 10 Jul 2026 15:28Hi Ffion, thanks for reporting this. I need a bit more detail to track down the issue. Can you tell me which operators are duplicated and what the record IDs are? That'll help me see what's happened. Also, when did you first notice the duplicates - was it after a sync or a data change? Thanks, Bethan
- Public reply · Ffion Rees 13 Jul 2026 16:12The duplicates are spread across about a dozen operators - I've sent over a spreadsheet with the IDs. It looks like it started happening when we migrated our CRM data structure last week. We renamed the operator field in Salesforce and I think that may have triggered it. This is really impacting us right now as we need reliable numbers for the board. Ffion
- Public reply · Bethan Lister 14 Jul 2026 15:09Got it. The issue is that the old and new operator field names were both being indexed, creating the duplicates. I've removed the old records from the index and reindexed with just the new field. Your fresh data will come through cleanly with the next refresh overnight. I'd suggest doing a quick audit of your Salesforce operator records to make sure the field migration is clean on that end too. Let me know if you see any more issues. Thanks, Bethan
- Status change · 18 Jul 2026 23:59