How is it that this is not a thing? I genuinely can’t believe that one of the most rudimentary lables meant to provide a lead with an easy to follow lifecycle isn’t mappable. WHY??? Please someone tell me why!
If stage and stasus mapped, there is so much more automation that could be built in from triggers on both systems. not only that, but the ammout of reporting that would be available would also increase. Please fix this.
Hi Paul,
You should be able to map the Outreach Prospect Stage with the HubSpot Lead Status through a custom field mapping.
I’ve attached a screenshot to provide additional clarity.
If you’re having difficulties with this, feel free to open a ticket with our support team so we can assist.
With regards to the status field in Outreach, I’m afraid this isn’t visible via the Outreach API and therefore, we can’t expose it within our integration.
Hope this helps.
Thanks JonasR.
This was very helpful! After putting much thought into it, and discussing with my marketing team, it seems that this isn’t the best way to map.
The reason is Marketing has already built workflows around contact stages. I noticed there is a Lead object in Hubspot that we were not using. I’d like to sync Lead Stages in Hubspot to Prospect Stages in Outreach. However, I can’t figure out how to had an object sync to the integration.
Is this possible?
Best,
Paul
Hi Paul,
Good question! At this point, it’s indeed not possible to map dedicated Lead Stages from the Leads object within a Data Sync integration at this point.
The current Leads object in HubSpot is dependent on the Lifecycle stages. This means you can only use the HubSpot Lifecycle Stage in your Data Sync mapping and not the Lead Stages I’m afraid.
Best,
Jonas