Thanks for your response Alyssa - this is so interesting! You described my issue at Plum to a t.
What we ended up doing after this post was creating a custom property to store the date, like you mentioned, but instead of just copying over the HubSpot internal became a MQL date we used a workflow to date stamp the property with the enrollment trigger being “contact became MQL”.
This has been working so far for us, with the caveat that then of course this property is written over whenever a contact reverts, and re-converts later (this is a fairly common scenario for us, as well).
Your solution is super interesting - if you don’t mind, I do have one followup question. How do you handle multiple contacts from the same company being moved into MQL? E.g. you get an initial MQL from a demo request, another individual from that company also comes through and converts to MQL - is a separate deal object created for this contact, or do you somehow associate them to the original “deal” and report on numbers at an account level? I suppose this question really goes back to how you fundamentally structure MQL reporting, but I’d be curious to get your take.
Thanks again for your response!