I have automations which trigger when deals are created or moved to a new stage. I am wanting to now sync my deals from pipedrive but I dont want them to trigger any automations? Do you know if this will happen?
Hi @Hyroxware,
That depends on what exactly you set up - can you share a screenshot of your enrollment criteria?
If you want to exclude deals created by an integration, you would do so via the record source property.
Best regards!
@Hyroxware if the integration is creating deals in that stage, yes, they would enroll.
Find a deal created from Pipedrive, look up its ‘Record source’ or ‘Original source drill-down 2’, the exclude this value in your workflow enrollment criteria.
Do I need to just turn all workflows off then sync and then turn eveything back on? I have 45 automations.
@Hyroxware if this is a one-time effort, that might be easier than adjusting all workflows, yes.
Keep in mind however that Pipedrive created deals might still enroll later on if they meet the criteria later.
Keep also in mind that workflows might have deals waiting in delays, which shouldn’t be turned off just like that.
Yeah this is a one time thing. We are migrating from pipedrive to hubspot and I preset hubspot up with all the automations we need. So I am just moving eveything over for now and then will pause the sync once everything is over.
@Hyroxware if currently no deals are enrolled in your workflows, turning them off, running the sync, turning them back on, might be the easiest option. Make sure to not enroll existing records when you turn the workflows on.
Hi @Hyroxware
If you migrate deals from Pipedrive into HubSpot, yes those new deals can trigger workflows if they match your enrollment criteria. The safest route is either turning workflows off during the import, or better, excluding “Integration” as the record source in your workflow settings. You can check this in the deal property “Record source” or “Original source drill-down 2” and add it as a filterr
(Set your workflow enrollment triggers )
- If you’ve got 45 automations, switching them all off can be heavy. Another trick is to clone your critical workflows, add the source exclusion, and use those moving forward. That way your existing automations don’t catch migrated data but will still fire correctly for future native HubSpot deals
(HubSpot's default deal properties ) - Since this is a one-time migration, pausing workflows or excluding record source are both valid. Just be mindful of any workflows with delays those will resume once you turn things back on
And just as a side note, some teams skip the hassle entirely by using a platform like Stacksync. It handles two-way syncs and can apply fine-grained filters so migrated data lands cleanly without tripping automations.
Hope this clears it up.