Move the relationship without rewriting the event
Synthetic lead copies contain a discovery call on 6 October and a quote response on 9 October. They merge on 12 October. The call still occurred on 6 October, and the response still belongs to quote Q-5. A note saying “follow up next week” needs its original timestamp to interpret the intended date. Store the merge as its own activity rather than retimestamping every historical entry.
| Activity | Original time / author | Decision link | After merge |
|---|---|---|---|
| A-CALL | 6 October / Mai | O-EXPORT | Time and author unchanged |
| A-REPLY | 9 October / customer reply | Q-5 | Retain original response and quote link |
| A-MERGE | 12 October / data owner | Two lead IDs into C-31 | New merge event only |
Check the combined chronology
- List activities from both records
- Retain original event metadata
- Keep quote and opportunity links
- Add a separate merge entry
Two similar notes are not automatically duplicates; compare their source event and decision link before removing either.
What is the age of the 6 October call on the 12 October merge date?
Show the worked answer
Six calendar days in this date-only fixture. Retimestamping it to 12 October would incorrectly report zero.
The sheet preserves CRM activity semantics. It does not specify a storage migration mechanism or imply that every CRM supports immutable activity fields.