Migrating Contact Source Data Without Losing Historical Accuracy
SOLVE
Hi community!
We currently use a custom property to track the source of our contacts, but it was set manually in the past, leading to some inconsistencies due to poor selection. To address this, I’m considering creating a new property and building a workflow to migrate the data to more accurate options.
However, I’m concerned about losing the “evolution over time.” Specifically, once the workflow is activated, the dates in reports would reflect when the workflow was applied rather than the original create date.
Does anyone have advice on how to handle this while preserving historical accuracy in reports?
Regular properties don't capture the evolution over time, at least not in a way that would be accessible in a report. (Only special properties like lifecycle stage properties do that automatically.) You would have to use a custom date property and make sure to maintain this also.
In the context of a source however, I would challenge this a bit. Typically, the date information that goes along with a source would be the Create date and that is maintained automatically.
If you want to carry over the property history from the old to the new, that's unfortunately not possible.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Regular properties don't capture the evolution over time, at least not in a way that would be accessible in a report. (Only special properties like lifecycle stage properties do that automatically.) You would have to use a custom date property and make sure to maintain this also.
In the context of a source however, I would challenge this a bit. Typically, the date information that goes along with a source would be the Create date and that is maintained automatically.
If you want to carry over the property history from the old to the new, that's unfortunately not possible.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer