Lifecycle stage (sql-to-mql)

SOLVE
Marie_Baltz
Member

Is it ok to move the Lifecycle stage backwards?

0 Upvotes
2 Accepted solutions

Accepted Solutions
MFrankJohnson
Solution
Thought Leader

_hubspot-button-accept-as-solution-gif-v00.gif

Help other HubSpot searchers find this post by accepting the 'solution' (HubSpot word).

 

Q: Is it ok to move the Lifecycle stage backwards??

 

Short A: Not a HubSpot best practice.

 

Longer A:

HubSpot will warn against doing so in workflows. This will also adversely impact reporting.

- see Difficulty reporting due to deletion of Became x Lifecycle Stage Date property?

 

Help answer your question? If so, remember to accept this 'solution'.

Best,
Frank

 


Please add @MFrankJohnson to your message if you'd like me to reply.

 

hubspot-solutions-signature-mfrankjohnson-v03.png

 

www.MFrankJohnson.com

 

Note: HubSpot is a constantly evolving platform. Please check the date of each post and view all solutions in that context.

-- Visit

 

Hope that helps.

 

Be well,
Frank


Support • Web • Apps • Training

HubSpot's Hiring World-Wide!

View solution in original post

0 Upvotes
bradmin
Solution
Key Advisor

"Is it okay" is a tough question to answer. If you mean "is it possible to do this", you can with workflows in the Marketing product. Because HubSpot won't natively let you move the stage backwards (other than a manual edit), your workflow will need to first clear the value of the lifecycle stage property, then set it to its desired value. 

 

If you mean "is doing this a best practice", that's also tough to answer. You can certainly accomplish it, but you should have well-defined reasons for doing so, that are clear to the rest of your users. Else, they'll just see something which feels (to them) like some sort of phantom change. Even then, that assumes that there aren't any downstream impacts - for example, are there other workflows or automation an MQL would want to go through once, and only once, instead of on demotion? 

If it doesn't make sense to your organization or users, it's probably not a good idea. Otherwise, as long as you've carefully reviewed all use cases and communicated it to your teams, this is absolutely something doable. 


Brad Mampe, Salesforce Analyst, Fidelity
I'm probably wrong. I may not be right about that.

View solution in original post

2 Replies 2
MFrankJohnson
Solution
Thought Leader

_hubspot-button-accept-as-solution-gif-v00.gif

Help other HubSpot searchers find this post by accepting the 'solution' (HubSpot word).

 

Q: Is it ok to move the Lifecycle stage backwards??

 

Short A: Not a HubSpot best practice.

 

Longer A:

HubSpot will warn against doing so in workflows. This will also adversely impact reporting.

- see Difficulty reporting due to deletion of Became x Lifecycle Stage Date property?

 

Help answer your question? If so, remember to accept this 'solution'.

Best,
Frank

 


Please add @MFrankJohnson to your message if you'd like me to reply.

 

hubspot-solutions-signature-mfrankjohnson-v03.png

 

www.MFrankJohnson.com

 

Note: HubSpot is a constantly evolving platform. Please check the date of each post and view all solutions in that context.

-- Visit

 

Hope that helps.

 

Be well,
Frank


Support • Web • Apps • Training

HubSpot's Hiring World-Wide!

View solution in original post

0 Upvotes
bradmin
Solution
Key Advisor

"Is it okay" is a tough question to answer. If you mean "is it possible to do this", you can with workflows in the Marketing product. Because HubSpot won't natively let you move the stage backwards (other than a manual edit), your workflow will need to first clear the value of the lifecycle stage property, then set it to its desired value. 

 

If you mean "is doing this a best practice", that's also tough to answer. You can certainly accomplish it, but you should have well-defined reasons for doing so, that are clear to the rest of your users. Else, they'll just see something which feels (to them) like some sort of phantom change. Even then, that assumes that there aren't any downstream impacts - for example, are there other workflows or automation an MQL would want to go through once, and only once, instead of on demotion? 

If it doesn't make sense to your organization or users, it's probably not a good idea. Otherwise, as long as you've carefully reviewed all use cases and communicated it to your teams, this is absolutely something doable. 


Brad Mampe, Salesforce Analyst, Fidelity
I'm probably wrong. I may not be right about that.

View solution in original post