Short answer: HubSpot says that, from August 31, 2026, recorded meetings captured by HubSpot Notetaker, Zoom, Microsoft Teams, or Google Meet will create a meeting record rather than both a meeting and a call record. Recordings, transcripts, and summaries will be on the meeting record. Phone calls remain call records, and historical data is not being changed.
If your workflows, reports, properties, or integrations use a call record as a proxy for a recorded meeting, audit that dependency before the rollout. The safe migration question is not “How do I delete duplicate calls?” It is “Which business event was this automation or report actually trying to measure?”
What changes on August 31?
HubSpot’s official notice describes a change to how certain recorded-meeting activity is represented. Before the change, a recorded meeting can produce two related objects: a meeting record and a call record. After the change, the recorded meeting produces the meeting record only. The recording, transcript, and summary follow the meeting record.
There is an important boundary: an actual phone call is still a call record. The change does not mean that all calls become meetings, nor does it mean every meeting integration has the same behavior. Keep the scope on the documented capture paths and verify what your portal displays.
| Business event | Before the rollout | After the rollout | Audit implication |
|---|---|---|---|
| Recorded meeting via a documented capture path | Meeting plus related call record may exist | Meeting record only; recording, transcript, and summary attach to meeting | Find logic that filters or counts calls for this event |
| Actual phone call | Call record | Call record remains the relevant object | Do not migrate phone-call logic to meetings by default |
| Historical recorded-meeting data | Existing records | Historical data remains unchanged | Do not mass-delete existing call records as a “cleanup” |
Who needs to act?
Start with the people who own the data path, not only the person who owns the calendar. RevOps and CRM administrators usually know which properties and workflows are in use. Marketing operations may own lifecycle or lead-routing automation. Sales operations may own activity reports. Data and integration teams may be reading call objects through exports or APIs.
The change matters most when a team uses a call record to answer a question about a recorded meeting, such as:
- How many discovery meetings were completed?
- Which contacts had a recorded meeting in the last 30 days?
- Should a lifecycle stage or lead score change after the meeting?
- Where should a transcript or recording link be retrieved?
- Which rep or account owner should receive a follow-up task?
If a call object is used only for genuine phone calls, the documented change may not require a migration. Verify that assumption rather than moving every call-based automation.
Step 1: Build a dependency inventory
Export or record every asset that filters, counts, joins, or triggers on call records. Include the asset owner, business purpose, intended event, and the fields it uses. A simple table is enough:
| Asset | Current dependency | Intended event | Owner | Test case |
|---|---|---|---|---|
| Workflow | Call-created trigger or call property | Recorded meeting or phone call? | Named owner | One known recorded meeting and one phone call |
| Report | Call count/filter | Meeting attendance or phone activity? | Named owner | Known records before rollout |
| Integration | Call-object export or webhook | Need meeting assets or call activity? | Named owner | Payload and association check |
| Property | Call property used in segmentation | Which object should hold the value? | Named owner | Property population and association |
Do not rely only on asset names. A workflow named “meeting follow-up” may still trigger on a call record. Search the actual filters, enrollment conditions, report data source, integration mapping, and API object.
Step 2: Separate the business event from the object
For each dependency, write the intended event in plain language before choosing the replacement. “A call record was created” is an implementation detail. “A prospect attended a recorded discovery meeting” is a business event. Those are not interchangeable.
- Recorded meeting: move the dependency toward the meeting record and its meeting properties/associations, following the fields available in your portal.
- Phone call: retain the call record and its phone-call logic.
- Either activity: decide whether the automation should intentionally support both objects; document the separate conditions rather than assuming one object represents both.
HubSpot’s notice specifically recommends reviewing call-based workflows and recreating the intended behavior with meeting triggers and properties where the business event is a recorded meeting. Use the account’s current workflow editor and property picker; do not hard-code an undocumented field name from another portal.
Step 3: Audit reports and dashboards
Reports are easy to miss because they may continue to load while the number quietly changes. For every call-based report, record the current date range, filters, object, count, and a small known sample. Then answer whether the report is meant to show phone calls, recorded meetings, or both.
After the rollout, update a report that is meant to show recorded meetings to use the meeting object and appropriate meeting filters. Keep a separate phone-call report when that is the true business question. Re-run the known sample and compare definitions, not just totals. A different total may be correct if the old report counted the duplicate call object.
For a data warehouse, store an event-type field or source-object field in the transformation. That makes it possible to explain a step change instead of hiding it in a blended activity table.
Step 4: Check recordings, transcripts, and integrations
HubSpot says the recording, transcript, and summary will be on the meeting record after the change. Open the meeting index and a known test record after rollout. Confirm that the expected assets are visible to the users who need them and that links or exports still resolve.
For integrations, inspect whether the connector reads calls, meetings, or both. A connector that only listens for call creation may stop receiving the event it used as a proxy for a recorded meeting. If the integration needs phone calls too, keep the two paths separate and add an explicit deduplication rule downstream. Validate one recorded meeting and one real phone call so a fix for one does not suppress the other.
Step 5: Run a before/after QA plan
- Before August 31: save the current workflow definitions, report filters, object counts, and integration mappings. Capture a known recorded meeting and a known phone call.
- At rollout: read HubSpot’s live notice and check the account’s Product Updates area for any portal-specific timing or availability message.
- After rollout: create or locate one new recorded meeting through a documented path. Confirm one meeting record, the recording/transcript/summary location, relevant associations, and expected workflow activity.
- Phone-call control: verify that a genuine phone call still creates/updates the call record and follows its intended automation.
- Report control: run the saved report against the known sample, document the new object/filter, and explain any count change.
- Integration control: inspect the received payload or synchronized record, then check that no duplicate activity is introduced downstream.
- Close the loop: record owner sign-off, the date tested, portal tier/permissions where relevant, and any unresolved gap.
Keep the old definitions in the change record. Historical data is unchanged, so an audit trail helps a future analyst understand why a new report is not directly comparable with an old call-based report.
What not to do
- Do not delete historical call records to make a dashboard look cleaner.
- Do not migrate all call workflows to meetings without checking whether they represent phone calls.
- Do not assume every HubSpot plan, integration, or capture path exposes the same fields or rollout timing.
- Do not compare pre- and post-rollout activity counts without saving the object and filter definitions.
- Do not treat a successful test in one portal as proof that a separate production portal has the same configuration.
Teams building a broader stack can use this as a focused change-control exercise alongside the martech stack in 2026 guide. The objective is not to add another tool; it is to keep the business event, object, automation, and report definition aligned.
Frequently asked questions
Will HubSpot delete the old duplicate call records?
HubSpot says historical data is not changed. Existing records remain; this article does not recommend deleting them. Reconcile future reporting definitions instead.
Are phone calls becoming meeting records?
No. The official notice says actual phone calls remain call records. The documented change concerns certain recorded meetings that previously produced both a meeting and a call record.
Where will a new recording or transcript appear?
HubSpot says the recording, transcript, and summary will be associated with the meeting record after the change. Check the meeting index and a known post-rollout record in the relevant portal.
Which workflows should I change?
Audit any workflow that uses a call-created trigger or call property to represent a recorded meeting. If the intended event is a meeting, recreate the logic with meeting triggers and properties available in your account. Leave genuine phone-call workflows on call objects.
Will every report break?
Not necessarily. A report intended for phone calls may remain correct. A report that used duplicate call records to count recorded meetings may need a new object or filter. Validate a known sample and document the definition.
Should I wait until after August 31 to act?
No. Build the dependency inventory before the scheduled rollout, save current definitions, and plan a post-rollout test. Re-check HubSpot’s live notice on the day because account communication can change the operational details.
Bottom line
HubSpot’s August 31, 2026 change is best handled as a data-definition migration. Recorded meetings move to a meeting-only record pattern for the documented capture paths; phone calls remain calls; historical data remains in place. Audit the intended event, update only the affected workflows and reports, and prove the new recording, transcript, integration, and phone-call paths with a small before/after test.
That object-level discipline is more useful than a broad platform verdict. The existing HubSpot vs Salesforce comparison can help with CRM selection, while the AI marketing automation guide covers multi-channel automation. This page covers the operational seam where a product change can alter what your numbers mean.
For adjacent platform dependencies, see the current LinkedIn Marketing API changes and ChatGPT Ads product feeds guides. In each case, preserve the source definition, the owner, and the read-back test before treating an integration as healthy.
Official sources
- HubSpot: recorded meetings will no longer create duplicate call records
- HubSpot Product Updates: July 2026
- HubSpot: opt an account into a public beta
- HubSpot: use the data model builder
Editorial note: Prepared from HubSpot’s official Knowledge Base and product-update documentation checked August 30, 2026. This is a general migration checklist, not a claim of access to a reader’s HubSpot portal.
