What This Update Actually Is
Right now, every recorded meeting in HubSpot creates two separate records: a Call record and a Meeting record. That's been true whether the recording comes from HubSpot Notetaker or from a video conferencing integration like Zoom, Microsoft Teams, or Google Meet.
Starting August 31, 2026, recorded meetings will create only a Meeting record. The Call record won't be generated at all for these interactions.
Phone calls still create Call records. That behavior doesn't change. This update is strictly about meetings that get recorded through video conferencing tools or Notetaker.
To prepare for this, HubSpot is already migrating key properties to the Meeting object: transcript, transcript ID, recording URL, duration, and summary. These properties have historically lived on the Call record. After August 31, they'll live on the Meeting record instead.
Why HubSpot Shipped This
The dual-record pattern was confusing. Humans who book a video meeting and record it don't think of that as a "call." They think of it as a meeting. But HubSpot's data model treated it as both, which created noise in the CRM.
The downstream frustration was real. Reports would count the same interaction twice if they weren't built carefully. Workflows would fire on Call creation even when the trigger was a recorded Zoom session, not a phone call. Admins would audit a contact record and see a pile of Call activities that were actually just meetings.
This change also aligns with how HubSpot's Notetaker product is maturing. As Notetaker gets smarter about capturing meeting context, it makes sense for all that data to live in one clean place: the Meeting record.
How to Use It Step by Step
Before August 31, run through these steps to make sure your portal doesn't break when the switch flips.
- Audit your workflows for Call creation triggers. Go to Automation, filter by "Call" as the enrollment trigger, and check whether any of those workflows were actually meant to fire on recorded meetings. Update the trigger to Meeting creation where needed.
- Review Call properties in use. Pull a list of active workflows and reports that reference Call properties like transcript, transcript ID, recording URL, duration, or summary. These properties are moving to the Meeting object, so any automation or report pulling from the Call object will need to be redirected.
- Rebuild affected reports. If you have any reports using the Call or Engagement object to track recorded meetings, rebuild them using the Meeting object. HubSpot's custom report builder will let you pull in the new Meeting properties once they're migrated.
- Update navigation habits for your team. After August 31, recordings and transcripts live in the Meeting index, not the Call index. Brief your sales and service humans so they know where to look.
- Check third-party integrations. If any tools connect to HubSpot via the Engagements API or pull Call records to sync meeting data, loop in your developer or integration partner now. The Call record for meetings won't exist after the cutover date.
- Bookmark the Meeting index. Go to your HubSpot portal, navigate to Meetings, and confirm your team knows this is now the single source of truth for recorded meeting activity.
What It Touches in Your HubSpot Strategy
This change is small in concept but wide in impact. Here's where you'll feel it across the portal.
Workflows: Any workflow triggered by Call object creation that was actually firing on recorded meetings needs a new trigger. Call-based triggers will no longer fire for recorded video meetings. If your team built follow-up sequences, task assignments, or deal updates off the back of recorded meetings, those automations will stop working unless you update them.
Properties: Transcript, transcript ID, recording URL, duration, and summary are the big five. They're migrating to the Meeting record. Any list, workflow filter, or report built on these properties at the Call level needs to be updated to reference the Meeting object.
Key Takeaway
Don't wait for August 31 to start your audit. HubSpot is already adding transcript, transcript ID, and duration to the Meeting record right now. Start building and testing updated reports and workflows today so you have time to validate before the cutover.
Reporting: If your sales activity reports track recorded meetings via the Call object or the Engagement object, those reports will under-count activity after August 31. Rebuild them to use the Meeting object. This also affects dashboards that compare call volume to meeting volume, since the artificial inflation from duplicate records will disappear.
Notetaker users will feel this most directly. If your team uses HubSpot Notetaker to auto-capture recorded meetings, the AI-generated summaries and transcripts will now live exclusively on the Meeting record. If you want to understand how Notetaker's smart features connect to deal progression and CRM updates, the Notetaker with Smart Deal Progression update is worth reading alongside this one.
Key Takeaway
Your reports are the highest-risk item here. A workflow that doesn't fire is obvious. A report that silently undercounts recorded meeting activity because it's still pointing at the Call object is much harder to catch. Prioritize reporting cleanup first.
This update is also a good prompt to revisit how your RevOps setup handles engagement tracking more broadly. If your team has been building automation off the back of HubSpot's activity records, the Breeze Assistant task help update shows how AI-powered task workflows are becoming a cleaner alternative to activity-triggered automations.
Who Should Care Most
Not every portal will feel this equally. Here's who needs to act fast.
- HubSpot admins and RevOps leads who built workflows triggered by Call creation. If you built automation assuming every recorded meeting would create a Call record, those workflows break on August 31.
- Sales managers who track rep activity through Call-based reports. Your recorded Zoom and Teams calls have been inflating your Call count. After August 31, those recordings live in Meeting reports. The data doesn't disappear, but the report needs to be rebuilt to find it.
- Customer success and service teams using Notetaker for client calls. If you're running recorded video meetings for onboarding or support and have automation tied to those recordings, the trigger objects change.
- Operations humans managing third-party integrations. Any tool that reads HubSpot Call records to sync meeting data, like a BI platform or a custom CRM integration, needs to be updated to read from the Meeting object instead.
- Small and mid-size teams who self-manage their HubSpot portal without a dedicated admin. If no one has eyes on your workflow list and report library, this change could silently break things before you notice.
George's Take
I've seen this pattern dozens of times across portal audits: a workflow built with good intentions, triggered by Call creation, doing something useful for recorded meetings. And then months later, nobody remembers why there's a Call-based trigger in there, or whether it's still working correctly. HubSpot cleaning up the dual-record issue is a real quality-of-life improvement for your data model. But it's also a forcing function. If you've been meaning to clean up your activity-based automations and reports, August 31 is your deadline. Don't let it sneak up on you.
“A clean data model is the foundation of every good HubSpot strategy. HubSpot is doing the hard work of fixing the object structure. Your job is to make sure your workflows and reports are ready to meet it.”
If you're not sure how deep this change runs in your portal, or you want a second set of eyes on your workflow and reporting setup before August 31, let's talk. The Sidekick team reviews these kinds of structural changes every week across client portals, and we can help you audit, fix, and future-proof your setup before the deadline hits.
Book a strategy call with Sidekick Strategies and we'll walk through your specific portal setup, identify anything at risk, and help you make the transition without breaking what's already working.
Frequently Asked Questions
Will my existing Call records for recorded meetings be deleted after August 31?
No. HubSpot is only changing how new recorded meetings are stored going forward. Existing Call records created before August 31 won't be deleted. You'll still have access to historical data, but new recorded meetings after the cutover date will only create a Meeting record.
Do phone calls still create Call records after this change?
Yes. This change only affects meetings recorded via Notetaker, Zoom, Microsoft Teams, or Google Meet. Actual phone calls logged in HubSpot will continue to create Call records exactly as they do today. Nothing changes for your phone-based sales or support activity.
Which HubSpot properties are moving from the Call object to the Meeting object?
HubSpot is migrating transcript, transcript ID, recording URL, duration, and summary from the Call record to the Meeting record. HubSpot has already started adding has transcript, transcript ID, and duration directly to Meeting records ahead of the August 31 deadline.
How do I find workflows triggered by Call creation that might be affected?
Go to Automation in your HubSpot portal and filter workflows by enrollment trigger. Look for any workflow triggered by Call creation or a Call property change. Cross-reference these against workflows you know were built to respond to recorded meetings, then update the trigger to use the Meeting object.
Where will recordings and transcripts live after August 31?
Recordings and transcripts for meetings recorded via Notetaker or video conferencing integrations will live in the Meeting index in HubSpot. Your team should stop looking for these in the Call index and get familiar with navigating to Meetings to find recorded session data.
Does this change affect HubSpot Notetaker specifically?
Yes. Notetaker-recorded meetings are included in this change. After August 31, Notetaker recordings, AI-generated summaries, and transcripts will be stored on the Meeting record only. If you have workflows or reports built around Notetaker activity using Call records, those need to be updated before the deadline.
