CAI Two-Way Contact Lifecycle & Deal Sync
Overview
Citrus America's HubSpot instance is configured with a two-way synchronization between contact lifecycle stages and deal objects. This means the "Opportunity" lifecycle stage and deal creation are kept in sync automatically, regardless of which direction the user enters the data.
This was confirmed during a live session when Miriam noted that a contact ("Jasmine") had been automatically advanced to the "Opportunity" stage after she created a deal directly — without manually setting the lifecycle stage.
How It Works
The sync operates in both directions:
| Trigger | Result |
|---|---|
| Contact lifecycle stage set to Opportunity | A deal is automatically created and associated with the contact |
| A deal is created directly from the deal object and associated with a contact | The contact's lifecycle stage is automatically advanced to Opportunity |
This means sales reps can enter the pipeline from either end — qualifying a contact through the lifecycle flow, or jumping straight to deal creation — and HubSpot will keep both objects consistent.
Confirmed Behavior
"I definitely know that I did not set her lifecycle stage to opportunity yesterday. So that was just, it was just more so confirming because also then that's the kind of a little note that I want to make for the team as well."
— Miriam Framson
Mark Hope confirmed the intended design:
"If you change the lifecycle stage to Opportunity, it should create a deal automatically. And if you create a deal directly from the deal object, it should then update the lifecycle stage to Opportunity."
Practical Implications
- Flexible entry point: Reps who prefer to start with a deal (e.g., on a live call with a prospect) don't need to first navigate the lifecycle qualification flow. The contact record will catch up automatically.
- Data consistency: Eliminates the risk of a contact remaining in an earlier lifecycle stage (e.g., SQL) while an active deal already exists.
- Team communication: Miriam flagged this as a key point to communicate to the CAI sales team — the two-way nature of the sync is non-obvious and worth documenting in onboarding materials.
Open Item
Mark noted this behavior should be verified to ensure the workflow is correctly configured end-to-end:
"Let us check and make sure that that's what happened."
See [1] for overall project status and [2] for the related MQL → SQL trigger fix happening in the same configuration pass.
Related
- [1]
- [3]
- [2]