Two Versions of a LinkedIn Outreach Campaign Went Live: Choose One and Reconcile Every Touch

Two live versions of the same LinkedIn outreach campaign are an incident, not a test. A prospect can receive repeated comments, competing connection requests or different opening messages, including replies from separate inboxes. The immediate job is to stop future conflict, then reconstruct the record.

Do not choose the survivor because it has the newer name or cleaner copy. Choose the version that has a clear audience definition and current offer, plus usable reply ownership and unambiguous CRM history. Then treat every touch from the other version as evidence that must be reconciled, not erased.

This process applies to legitimate, consent-based business outreach. It does not require account or identity sharing, or an attempt to bypass platform controls.

• Freeze new enrollments and queued sends in both versions while the team identifies the authoritative survivor.
• Export the audience, touch history, queued work, reply state, bookings, CRM activity, suppressions, and reporting identifiers for each version.
• Assign one owner to decide the surviving campaign and one owner to certify that the retired version can no longer create a new touch.

Which live campaign version should remain authoritative?

Choose the version that best reflects the current campaign decision. It needs a defined target audience, a current offer, a named reply owner, and a reporting destination the team will keep using. A campaign with better wording but unclear ownership is not a safe survivor.

Record the decision in the ledger before changing records. Write the campaign ID, version, launch time, decision owner, reason, and shutdown action for the retired version. That prevents a later reviewer from treating the choice as an undocumented preference.

Keep the authority decision narrow. It decides which version can create future touches. It does not declare all prior activity from the retired version invalid.

Which prospects need a touch reconciliation?

Create a combined audience file from both versions and match prospects using the strongest available identifier. Use the CRM record ID when both versions point to the same record. If that is missing, use a verified profile URL or another stable identifier already held in the system. Do not merge people because their names look similar.

Classify each prospect into a clear disposition: survivor only, retired only, overlap with no executed touch, overlap with one executed touch, overlap with conflicting executed touches, active reply, booked meeting, suppressed, or unresolved. The disposition determines the next action.

For an overlap with no completed touch, move the prospect to the survivor only after confirming that the retired version has no queued work. For an overlap with an executed touch, preserve the original touch history and decide whether the survivor should continue from the next appropriate step or stop for human review.

Use a higher bar for conflicting touches. If a prospect received different messages or has an active response, assign one person to own the conversation. Do not allow a campaign workflow to decide the next message while the conflict remains unresolved.

• Check comments, connection requests, messages, tasks, inbox replies, bookings, CRM activities, and suppression records for each overlapping prospect.
• Mark every future action as keep, cancel, defer, or human review.
• Add the reviewer and timestamp, with an evidence link to every unresolved or corrected record.

How should replies and bookings be merged?

Replies and bookings belong to the prospect's canonical conversation record, not to whichever campaign happened to create the latest activity. Select one reply owner and link all relevant history to that owner. Stop all automated or queued follow-up until the owner confirms the next step.

Keep the original campaign attribution as historical context. A reply can have started after touches from both versions. Do not force a false single-campaign story when the record shows overlapping activity. Record the sequence of touches and explain the attribution rule used in the report.

HubSpot documents that a contact can be enrolled in only one sequence at a time. In that product, moving a contact to another sequence requires unenrollment from the current sequence first. That is a product-specific control, not a general LinkedIn rule. HubSpot's enrollment guidance was last updated June 23, 2026.

HubSpot also states that sequence contacts can be automatically unenrolled when they reply or book a meeting, depending on the configured triggers. Review those triggers before the restart so a reply or booking does not leave a prospect exposed to a conflicting future step. HubSpot's sequence settings guidance was last updated August 17, 2026.

How should CRM writes and suppressions be corrected?

Treat CRM reconciliation as a controlled review, not a bulk overwrite. Compare the current record with the activity history from both versions. Preserve information that remains correct, such as a confirmed booking or genuine reply, plus an existing suppression. Correct only the fields and activities that the duplicate launch made inaccurate.

Add an incident note to affected records with the campaign IDs, touch timestamps, corrective action, reviewer, and canonical owner. That note gives future operators enough context to avoid re-enrollment or to understand why an apparently skipped prospect was intentionally held.

Do not remove a suppression because the authoritative survivor needs more audience. A suppression reflects a safety or preference decision until the system's documented process changes it. The duplicate-campaign incident is a reason to review suppressions carefully, not a reason to weaken them.

If LinkedIn activity was logged through a CRM integration, verify whether the record timeline actually contains the conversation. HubSpot states that InMail conversations sent from its LinkedIn Sales Navigator integration do not automatically save to the record timeline and may need manual logging. HubSpot's integration guidance was last updated August 31, 2026.

How should reporting attribution survive the cleanup?

Split reporting at the incident cutoff. Report historical activity for both versions through the cutoff, then report future activity under the authoritative survivor. Keep the retired version visible in the incident report so the team can see the overlap and resulting corrections, including work that did not proceed.

Do not add sent touches from both versions and call the total campaign reach. Deduplicate at the prospect level first. A prospect touched by both versions counts as one prospect with overlapping activity, not as two independent prospects.

Keep attribution rules for replies and bookings alongside CRM attribution rules in the ledger. If a prospect interacted after activity from both versions, mark the result as shared incident history or assign it using a rule agreed before the report closes. The rule matters more than making one version look better.

For systems with sequence reports, preserve the platform's historical activity rather than assuming unenrollment deletes it. HubSpot says manual or automatic unenrollment stops upcoming scheduled steps without undoing emails already sent. Sequence enrollment and performance data remain unaffected. HubSpot's unenrollment guidance was last updated September 30, 2026.

What proves that the duplicate campaign cannot recur?

A shutdown is complete only when the retired version cannot produce a new prospect touch. Confirm that it has no active audience enrollment, no queued actions, no automation path, no task queue, and no linked workflow that can restart the same audience.

Run a recurrence test with a controlled record or a non-sending inspection path. Confirm that the survivor has the intended audience and that the retired version cannot create a touch. Capture the result in the ledger with the person who performed the check.

Then add a launch control. Every future campaign version needs a campaign ID, owner, target definition, launch timestamp, reply owner, CRM destination, suppression source, and approval record before it goes live. A clone without these fields is not ready to launch.

Warm, comment-led outreach still needs clean operational history. Familiarity is built over repeated real interactions. Duplicate activity can break that context before a connection request or conversation has a fair chance to land.

• Require a pre-launch overlap check against every active campaign audience.
• Require one named authority for each prospecting motion.
• Require a shutdown proof before a replacement version can take over.