Summary

  • Outside HubSpot's specified primary-ID preservation beta, merging contacts removes both records from active workflows. Inside the beta, the primary continues and the secondary leaves.
  • Bulk selection by latest update includes hidden internal properties. The freshest record can win without carrying the most valuable unfinished commitment.
  • Re-enrollment starts a workflow again from the beginning. Merges cannot be undone, so a successful cleanup needs an account of what happens to the remaining work.

The duplicate count goes down. Somewhere else, a customer is still waiting for the next message. Both can be true after a perfectly successful contact merge.

Consider a hypothetical pair of genuine duplicates for the same prospect. One record is waiting in a workflow for a post-demonstration follow-up; the other is waiting for a trial check-in. Combining them settles the question of how many records the prospect should occupy. It leaves a rather more commercial question: what happens to the two pieces of work the company has not finished?

HubSpot's published rules make that question unusually sharp. A merge can gather the evidence of a relationship while interrupting the machinery that was meant to continue it. The file looks better. The customer has yet to receive the benefit.

A complete past can hide an empty next step

HubSpot's record-merging documentation describes the combination of activities, associations and property history. A salesperson opening the resulting contact can find conversations that previously lived in separate places. That is a useful improvement, and a persuasive visual signal that the relationship has survived intact.

Running work follows a separate rule. For the Professional or Enterprise accounts to which the workflow functionality applies, the decisive distinction is enrollment in the public Primary ID Preservation for Merged Records beta. Outside it, both records leave their active workflows at the time of the merge. Inside it, the primary keeps its delays, branches and pending actions. The secondary leaves the workflows in which it was active.

Choosing the primary therefore preserves something operationally valuable under the beta: a place in a running process. An old activity from the secondary can appear in the combined history without bringing along the next action that was waiting behind it.

In the imagined sales case, somebody still has to settle the fate of the demonstration follow-up and the trial check-in. The team might keep both, combine their purpose in a human conversation, or deliberately cancel one. The reduction in record count does none of that thinking.

This is how two sensible checks can miss the same problem. The administrator confirms that the duplicate has gone. The salesperson confirms that earlier conversations remain. Each has inspected a real benefit. Neither has yet established that the next promised action will happen.

The newest timestamp gets a promotion

A person reviewing one pair can ask which record carries the work that should continue. A batch needs a rule. HubSpot's duplicate-management tool offers choices based on engagement, creation time and the most recent update. The update criterion evaluates all properties, including hidden internal ones.

That gives the software an orderly way to choose. It gives the business no automatic ranking of unfinished customer commitments. A recently changed record can be less important to the next customer interaction than an older one.

Under the beta, this ordering can help decide which workflow keeps running. A timestamp has been promoted from sorting assistant to supervisor of unfinished work. It has little interest in who must explain a missed follow-up later.

The consequence follows from the authority assigned to the rule. There is no need to invent a vendor motive. “Changed most recently” answers a question about sequence; “must continue” answers a question about the business. Treating the first as a convenient substitute for the second hides a decision inside routine administration.

The answer need not be a committee for every idle contact. First confirm that the proposed duplicates really represent the same person, then separate records carrying active work from those carrying none. An empty record and a record waiting to act for a customer deserve different attention even when the cleanup tool places them in the same queue.

Re-entry is a fresh lap

HubSpot has a separate setting for enrolling merged contacts. By default, changes caused by the merge do not automatically put a contact into new workflows, even when it meets their conditions. The setting can permit that entry. It does not restore the previous execution position.

The re-enrollment rules start the record at the beginning again. Earlier actions return to its path, with actual execution subject to the relevant conditions. Trying to recover one missing step can therefore put already completed work back on the itinerary.

Manual enrollment also starts at the beginning. To run only later steps, HubSpot suggests creating or cloning a separate workflow that begins at the desired action. Recovery requires a distinction between work already performed and work still owed. Knowing the name of the old workflow is insufficient.

Someone has to make that distinction. Someone reviews the history, prepares the remaining steps and decides whether the customer needs another message. A few saved clicks in data administration can turn into a small investigation elsewhere. Productivity looks wonderful if the stopwatch stops before that investigation begins.

The evidence belongs after the merge

The workflow details page exposes actions, events and times. Comparing the merge with unenrollment, subsequent entry and actual execution is more useful than admiring the final contact history. Establishing a particular commercial loss requires that account's pre-merge positions and subsequent action records.

There is also a firm limit to reversal. HubSpot does not support unmerging the records. Removing an additional email and creating another contact with it makes a new record. Recovering an old ID helps explain provenance; it does not restore two previous execution states.

A cleanup is consequently finished when the remaining commitments have a destination. Continue them, assign them to a person, or cancel them deliberately. “The record looks tidy” is a description of the cabinet, not an account of the work inside it.

Customers need not know how many rows they once occupied. They do need the business to remember what was supposed to happen next. That is the result a contact merge should ultimately be judged against.