Looking for guidance / workaround on HubSpot Lead object + sequence activity
We’ve recently implemented the Lead object for outbound, with the following setup:
Leads are automatically created when a contact is enrolled in a sequence
Lead stages are supposed to progress based on activity (emails, calls, etc.)
Issue:
Because the lead is created after the contact is enrolled, all sequence activity is associated with the contact, not the lead. As a result, HubSpot doesn’t automatically move the lead through its stages.
Current understanding:
HubSpot doesn’t retroactively associate past activities to the Lead
Lead stage automation depends on activities being directly associated with the Lead
Options we’re considering:
Build workflows to “mirror” contact activity → update Lead stages (not perfect, adds maintenance)
Change process so leads are created before sequence enrollment (cleaner, but adds friction for reps)
Question:
Has anyone found a scalable workaround for this?
Is there any way to force or automate activity association to the Lead?
Or best practices for sequencing + Lead object working together cleanly?
Appreciate any insights from teams who’ve solved this.
the native functionality/automation for lead creation is based on lifecycle stage. When a contact becomes xxxx lifecycle stage (which ever is set on the settings automation.)
Once the lead is set HubSpot also has automation (as mentioned) that when an email is sent it will move along the pipeline.
my suggestion would be to follow this process. I’m not sure how you are identifying when someone should be enrolled into a sequence but use that as enrollment into an automation that will mark them as a lead. Once they become a lead, the rep will receive notification and then they can enroll them into the sequence. This will allow for the HubSpot lead automation to then move to attempting stage (or whichever is your stage).
This is a known gap in how HubSpot built the Lead object and there is no native way to retroactively associate sequence activity to a Lead. HubSpot ties sequence activity to the Contact at the point of enrollment, and that association does not transfer automatically.
Of your two options, creating the Lead before sequence enrollment is the right call. The friction for reps is real but manageable, and it is the only approach that keeps your data model clean long term. The workflow mirroring route works initially but becomes a maintenance burden as your sequence activity types grow, and you will always be one edge case away from a Lead stage that does not reflect reality.
The way to reduce rep friction on the pre-creation approach is to automate Lead creation as part of your pre-sequence process rather than making it a manual step. If reps are enrolling contacts through a view or list, you can trigger Lead creation via workflow when a contact meets your outbound criteria, so by the time a rep goes to enroll, the Lead already exists.
On the activity association question: there is no supported way to force retroactive association natively. Some teams have explored doing this via the HubSpot API by manually associating activity IDs to the Lead object after the fact, but it is complex to maintain and dependent on your engineering resource.
What does your current pre-sequence workflow look like for reps? That would help narrow down where the Lead creation step fits most cleanly.
It’s a mix. Reps typically work on accounts alongside their BDRs, but may also work independently.
They identify contacts either directly in HubSpot (if available) or by importing them from third-party tools. Once identified, contacts are enrolled in sequences through HubSpot.
While the BD team also uses another tool that doesn’t link to the lead object (only the contact), we’ll set that aside for now and assume all enrollments are happening in HubSpot.
