What This Update Actually Is
Right now, every meeting recorded through HubSpot Notetaker, Zoom, Google Meet, or Microsoft Teams creates two separate engagement records: a Call record and a Meeting record. That's one real event logged twice, in two different places.
After July 31, 2026, recorded meetings will create only a Meeting record. Call records will still exist, but only for actual phone calls. Transcripts, recordings, and meeting-specific properties like duration and transcript ID will live exclusively on the Meeting object.
HubSpot is also backfilling key properties directly onto Meeting records. The properties "has transcript," "transcript ID," and "duration" are being added to the Meeting object now so you can start rebuilding ahead of the deadline.
Why HubSpot Shipped This
The duplicate record problem isn't new. Humans who manage HubSpot portals have been tripping over inflated Call counts and inconsistent activity reports for a while. When a single recorded Zoom call creates both a Call record and a Meeting record, your engagement reporting gets bloated and your automations become unreliable.
The deeper issue is that "Call" and "Meeting" mean different things in practice. A phone call is not the same as a scheduled video meeting with a transcript. Treating them the same object type creates downstream confusion in workflows, dashboards, and integrations.
By separating them cleanly, HubSpot gives ops teams a more accurate activity model and gives sales and service humans a cleaner view of what actually happened in each conversation.
How to Use It Step by Step
There are two phases: what to do before July 31, and what to finalize after.
Before July 31:
- Audit your workflows: Find every workflow triggered by Call creation and check whether it's actually tracking a recorded meeting. Flag any that use Call-based properties like "has transcript," "transcript ID," or "duration."
- Audit your reports: Open every dashboard that filters by Call or Engagement objects and identify which ones are measuring meeting activity. Note them so you know exactly what to rebuild.
- Opt into the Meeting Workflows Beta: Join the beta now so you can start building Meeting-based workflows. New property data starts populating July 1, but you can configure the workflows before then.
- Explore the Meeting index page: Get familiar with where all transcripts and recordings will live after the switch. This is now the single source of truth for recorded conversations.
- Watch for historical backfill: New Meeting property data starts July 1. Full historical backfill completes by July 31. Don't wait until July 31 to test your rebuilt workflows.
After July 31:
- Turn on your rebuilt workflows: Switch any Call-triggered workflows to Meeting-based triggers. Don't leave old workflows active or they'll fire on nothing.
- Update your reports: Replace Call-filtered activity reports with Meeting-based versions. Expect your Call volume numbers to drop. That's not a data loss; it's accuracy.
- Update team habits: Coach your humans to find meeting transcripts and recordings on the Meeting index page, not the Call index page.
What It Touches in Your HubSpot Strategy
This change ripples into more corners of a portal than most admins expect. Here's where to look.
Workflows
Any workflow using "Call is created" as a trigger needs to be evaluated. If it's tracking recorded meetings, rebuild it with a Meeting trigger. If it's tracking actual phone calls, leave it alone. The line between the two is now explicit.
Properties
The three key properties being migrated are "has transcript," "transcript ID," and "duration." HubSpot is adding them directly to the Meeting object. Any custom property logic or conditional rules you built on Call-based versions of these fields needs to move. If you've built conditional property logic into your records, this is worth a careful review.
Dashboards and Reports
Your "Call" volume metric will drop after July 31. Prepare your leadership team for this now so it doesn't look like activity fell off a cliff. Frame it clearly: the number is more accurate, not smaller. If you're running activity reports tied to pipeline stages or rep performance, those need to pull from Meeting data going forward.
Key Takeaway
Your Call volume will drop on July 31. That's not lost activity. It's duplicate records being removed. Prep your stakeholders before the number changes on the dashboard.
Integrations
If you've built integrations or Zaps that pull from HubSpot Call records to sync meeting data into a third-party tool, those connections will break. Audit your integration stack the same way you audit your workflows.
If you haven't done a full portal audit recently, this change is a strong prompt to do one now. Our HubSpot portal audit checklist covers workflows, integrations, properties, and data quality across every hub.
Key Takeaway
This update touches workflows, properties, dashboards, and integrations all at once. Treat it as a mini audit project, not a quick settings change.
Who Should Care Most
Not every HubSpot portal will feel this equally. Here's who needs to move fastest.
- RevOps leads and HubSpot admins: You're the ones who need to audit workflows and reports before July 31. This is your deadline to own.
- Sales managers running activity-based coaching: If your rep performance dashboards use Call volume to measure meeting activity, your numbers will look wrong after July 31 unless you rebuild the reports now.
- Service team leads using Notetaker for customer calls: Transcripts and recordings will move to the Meeting record. Your team needs to know where to look.
- Companies with complex automation stacks: The more workflows you have tied to engagement objects, the more surface area this change touches. Start the audit early.
- Smaller teams with lighter setups: You'll likely only need to check one or two workflows and one or two reports. This is a quick afternoon project for you.
George's Take
This is one of those updates that looks small on paper but reveals exactly how much technical debt has been accumulating in portals that have been live for two or three years. We've seen this pattern dozens of times: a team builds workflows on Call objects because that's where the transcript data lived, and now those workflows are doing something slightly wrong every single day without anyone noticing. HubSpot is cleaning up a real architectural problem here, and the teams who treat this as a chance to clean house will come out with a more reliable portal. The teams who ignore it until August will come out with broken automations and a very awkward conversation with their leadership about why activity numbers dropped.
“This update doesn't break your portal. It exposes what was already fragile. Use the next eight weeks to fix it right.”
If you've been tightening up your CRM object structure lately, pair this work with the changes from HubSpot's pipeline rules update for contacts and companies. Cleaner objects and cleaner engagement records together give your reporting a much stronger foundation.
And if you're rebuilding Meeting-based property logic at the same time, the recent date and datetime conditional property logic update gives you more precision in how those properties trigger downstream actions.
If you're not sure where to start or you'd rather not spend three weeks untangling your engagement object setup, that's exactly what a Sidekick portal audit is built for. We'll map what needs to change, build a prioritized action plan, and make sure your workflows and reports are ready well before the July 31 deadline. Book a strategy call and let's get your portal squared away.
Frequently Asked Questions
What happens to my existing Call records after July 31, 2026?
Existing Call records for past recorded meetings won't be deleted. The change only affects how future recorded meetings are logged. Going forward, Notetaker, Zoom, Google Meet, and Microsoft Teams meetings will create only a Meeting record. Historical Call records remain in your portal but won't receive new data from recorded meetings.
Will my HubSpot activity reports show a drop in call volume after July 31?
Yes, and that's expected. Because duplicate records are being eliminated, your Call volume metric will decrease after July 31. This doesn't mean less activity happened. It means the data is now more accurate. Update your dashboards to pull meeting activity from Meeting records to keep your reporting correct.
How do I find meeting transcripts in HubSpot after the July 31 change?
All meeting transcripts and recordings will live on the Meeting index page and on individual Meeting records. The Call index page will no longer show transcripts from recorded video meetings. Update your team's habits before July 31 so no one is searching in the wrong place after the switch.
What HubSpot properties are being moved to the Meeting object?
HubSpot is adding three key properties directly to the Meeting object: "has transcript," "transcript ID," and "duration." These properties are being backfilled now so you can rebuild workflows and reports before the deadline. New data starts populating July 1, and historical data is fully backfilled by July 31.
How do I update my HubSpot workflows for the Meeting record change?
First, opt into the Meeting Workflows Beta. Then identify every workflow triggered by Call creation that's actually tracking a recorded meeting, and rebuild those workflows using Meeting-based triggers. You can set up the new workflows now, even before July 1 when property data begins populating. Turn them on after July 31 when the change goes live.
Does this change affect phone calls logged in HubSpot?
No. This change only affects meetings recorded through Notetaker, Zoom, Google Meet, and Microsoft Teams. Actual phone calls made through HubSpot Calling will continue to create Call records exactly as they do today. The goal is to separate phone call activity from video meeting activity into their correct object types.
