View the contact merge history (audit log)
Every contact merge is logged with who, when and a snapshot of the absorbed contact. Learn how to review that record.
What the merge history is
Every time you merge two contacts in Omnifox, the system writes an entry to an audit log. That entry records which contact was kept, which one was absorbed, who performed the merge, when, and a snapshot (copy) of all the data from the contact that disappeared. So even though a merge can't be undone, you never lose traceability of what happened.
The history lives in your workspace's contact_merge_logs audit table and includes: the kept contact, the merged contact, the user who ran the action, the timestamp, and the backup of the absorbed data.
When this helps
- A customer claims data "went missing" after a merge and you need to reconstruct what the absorbed contact held.
- You want to audit who is merging contacts and how often.
- You need traceability evidence for compliance or internal control.
How it's generated (a reminder of the merge flow)
- Go to CRM > Duplicate contacts. Omnifox detects records that look like the same person (same email, same phone, or similar name).
- In each group pick which contact to keep with Keep.
- Click Merge into kept and confirm.
- Deals, conversations, activities, tags and custom fields move to the kept contact; the other contact is removed and the audit entry is written automatically.
A merge can't be undone, but the audit-log snapshot preserves the absorbed contact's data.
How to review the history
The audit log is a backend traceability table: today it has no dedicated screen in the app. To review it, ask your admin or Omnifox support to pull the entries from contact_merge_logs for your workspace. Each row tells you the kept contact, the absorbed one, who merged, the date, and the full snapshot.
Verify it
- After a test merge, request the latest log entry: it should show the kept contact id, the absorbed contact id, your user, and the timestamp.
- The metadata (snapshot) field should contain the data of the contact that disappeared.
If you can't find the entry
- Nothing shows up: confirm the merge actually completed (it didn't half-fail on an error) and that you're querying the right workspace; the log is isolated per workspace.
- I don't know who merged: if the user field is empty, the merge was run by an automated or API process rather than a person.
Tips
- Before a large merge, export or note the key data; the audit log is your safety net, not an undo button.
- Periodically review who merges contacts to catch team mistakes early.
Related articles
Related articles
-
How to import contacts from a CSV file
Upload your contact list in minutes by mapping your CSV columns to CRM fields.
-
Managing contacts and the CRM
In Omnifox every conversation creates a contact. Learn to use custom fields, tags, the deal pipeline and the contact 360 timeline.
-
CRM complete guide
The CRM in depth, in 46 chapters: pipeline, deals, the deal record, to-dos, dashboard and goal, settings, the contact record, contacts, import, lead forms, chat, AI and workflows.
-
Contact custom fields
Build fields tailored to your business to store exactly the information you need about each contact.
-
The sales pipeline and deals
Visualize and manage your sales process with a stage board and opportunity cards.