# Re-enrollment after merging

**URL:** <https://community.hubspot.com/t/re-enrollment-after-merging/73585>\
**Category:** Email Marketing Tool\
**Tags:** marketing-email\
**Created:** [January 24, 2023, 10:57am UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585 "2023-01-24T10:57:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![StefanTV](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@StefanTV](https://community.hubspot.com/u/StefanTV)\
**Post date:** [January 24, 2023, 10:57am UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/1 "2023-01-24T10:57:00Z")

</div>

Hi!  
After we merged contacts, some contacts got re-enrolled in a marketing workflow and received mails out of nowhere.

It was the case that a contact filled out a form with his primary mail address, however, he was not enrolled in the marketing workflow with his business address. After merging the private with the business profile, the workflow startet from scratch and he received the first email of the workflow on his business address (new primary mail address). Is there a way to prevent that from happening, or take the stage of the workflow in consideration, when enrolling the new primary email address, so the workflow won’t start all over?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 24, 2023, 11:00am UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/2 "2023-01-24T11:00:13Z")

</div>

Hi @StefanTV,

In the _Settings_ tab of a workflow, you can specify how the workflow should handle merges:

 ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/5/0596b47b142d9239f118bfb929c83ad5f085d1aa.png)

Best regards!

---

<div class="post-metadata">

**Author:** ![StefanTV](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@StefanTV](https://community.hubspot.com/u/StefanTV)\
**Post date:** [January 24, 2023, 12:21pm UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/3 "2023-01-24T12:21:58Z")

</div>

Hi @karstenkoehler,

Thanks for your reply!  
We also found those settings the last time it happened, however, it keeps occurring…

 ![StefanTV_0-1674562864363.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/b/6/b6803cec1bd663dd66cd77d5d369f26f60f7f6ee.png)

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 24, 2023, 12:25pm UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/4 "2023-01-24T12:25:51Z")

</div>

Hi @StefanTV,

If contact 1 was already enrolled in the workflow and after merging contact 1 and 2, the merged contact enrolled despite the ‘No’ setting, this sounds like a bug.

What exactly are the enrollment and re-enrollment settings of the workflow? Can you please share a screenshot?

Best regards!

---

<div class="post-metadata">

**Author:** ![StefanTV](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@StefanTV](https://community.hubspot.com/u/StefanTV)\
**Post date:** [January 24, 2023, 12:32pm UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/5 "2023-01-24T12:32:30Z")

</div>

It was the case that contact 2 was enrolled, contact 1 was not. So after merging, contact 1 got re-enrolled.  
Here you can find the screenshot of the enrollment criteria:

 ![StefanTV_0-1674563527305.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/e/feb41103b78a6e32986c33f8def5670b015156b2.png)

---

<div class="post-metadata">

**Author:** ![StefanTV](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@StefanTV](https://community.hubspot.com/u/StefanTV)\
**Post date:** [January 27, 2023, 7:58am UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/6 "2023-01-27T07:58:57Z")

</div>

Hi!  
Do you maybe have an update on this one?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 27, 2023, 8:04am UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/7 "2023-01-27T08:04:05Z")

</div>

Hi @StefanTV,

Unfortunately I don’t. I’d recommend taking this up with HubSpot support, they investigate this directly in your portal.

Best regards!

---

<div class="post-metadata">

**Author:** ![MHunter1](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MHunter1](https://community.hubspot.com/u/MHunter1)\
**Post date:** [April 17, 2024, 1:19pm UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/8 "2024-04-17T13:19:13Z")

</div>

Hi Karsten,

It doesn’t appear that this feature works with tickets… Do you know of a way to keep merged tickets from unenrolling in a workflow?

Thanks!

 ![Screenshot 2024-04-17 091756.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/3/b/3b7ae978485dcc4515de66a21e0f3c818c2a4633.png)

---

<div class="post-metadata">

**Author:** ![CBN](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbn/32/95196_2.png) [@CBN](https://community.hubspot.com/u/CBN)\
**Post date:** [May 31, 2023, 11:17am UTC](https://community.hubspot.com/t/re-enrollment-after-merging/73585/9 "2023-05-31T11:17:55Z")

</div>

We have just had issues with merged contacts being unenrolled from all workflows instead of being where they are/reenrolled.

Why don’t you get an warning about workflows in progress on either contact when you merge?
