## TL;DR
Unmerge or split the note by moving the call summary to the contact who was actually on the call, using the call recording association and the attendee list as the source of truth, then turn off automatic association to merged duplicates so the next merge does not drag notes across. Start with the merged HubSpot contact record, the call note that landed on it, and the merge history showing both source contacts, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

```text
how to fix HubSpot call notes error summary attached to wrong contact after merge
```

## Use this when
- You see this exact message or symptom: how to fix HubSpot call notes error summary attached to wrong contact after merge
- One run, record, call, or object is affected and you can name it
- A retry without changing anything reproduces the same result

## Not for this skill when
- The system fails with a different message and none of the signals here appear
- Nothing has failed yet and you are doing first time setup or general planning
- Every service from this vendor is down for all users, which is a vendor outage to wait out first

## Steps
1. Reproduce the failure once using the merged HubSpot contact record, the call note that landed on it, and the merge history showing both source contacts, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the attendee list on the original call, the associations on the summary note, and which contact the merge kept as primary. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: unmerge or split the note by moving the call summary to the contact who was actually on the call, using the call recording association and the attendee list as the source of truth, then turn off automatic association to merged duplicates so the next merge does not drag notes across. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the summary sits on the contact named in the attendee list and the other contact no longer shows the call
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

## Variant phrasings
### how to fix HubSpot call notes error summary attached to wrong contact after merge
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.
### Tool-first phrasing of this failure
The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
### Why does this keep happening after a retry
The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: HubSpot calls and contact merge at current versions

## Why it happens
A contact merge rewrites associations to the surviving record, so a summary created against the secondary contact is re-pointed at the primary even when the call was with a different person at the same company.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_YTqCmTLqV2BrQcJF_MDAEw