Features

Contacts, companies, deals, tickets, properties, associations, pipelines and activity history; custom objects depend on entitlement.

Example

Link an OA company, its contact, a deal and a service ticket rather than maintaining four disconnected lists.

Evidence

26,718 contacts; 35,758 companies; 1,125 deals; 1,332 tickets. Three custom objects have 15 / 38 / 2 active records.

Who

Sales, marketing, service and operations; editors need appropriate seat access and permissions.

License

Core access does not equal advanced Sales or Service access. Custom-object operations require a qualifying Enterprise subscription.

Removal

The last Enterprise downgrade leaves custom-object records viewable but blocks creation/editing, new associations and custom-object workflows. Do not equate this with deletion.

Unknown

Which custom-object processes are operationally indispensable?

Evidence: audit · downgrade · seats

Features

Campaigns, segments/lists, forms, marketing emails, workflows, ads/social and reporting; exact depth varies by tier.

Example

A webinar segment can enroll in a timed marketing nurture; the campaign groups its email assets for reporting.

Evidence

Marketing Professional licensed. 18 campaigns, 437 saved lists, 172 forms and 842 non-archived marketing emails.

Who

Marketing operators and analysts with the relevant tool permissions.

License

Current $623 base plus $700 for 25,000 additional marketing contacts; base includes 2,000 and three Core seats. Campaign tools require Pro/Enterprise.

Removal

Removing only the contact add-on changes billable capacity, not CRM record storage. Retaining Marketing Pro preserves ordinary licensed marketing automation, not all Data/Enterprise actions.

Unknown

Which audiences must receive which communications, on which system?

Evidence: audit · billing · campaigns · actions

Features

Sales workspace, leads, pipelines, sequences, templates, meetings, calling, forecasting and reporting; Enterprise adds higher limits and advanced governance/automation.

Example

A representative uses an individual connected inbox for a sequence with follow-up tasks, unlike a marketing campaign email.

Evidence

Enterprise licensed: 14 purchased Sales seats, 12 active assignments; 53 real Sales Sequence definitions and four deal pipelines.

Who

People who actually need advanced sales tools; not everyone with an executive or sales-related job title.

License

Public Pro $100/seat/month; proposal assumes five seats at $500. Pro supports 15 pipelines and sequences. Workflow-driven sequence enrollment requires Enterprise.

Removal

Downgrade changes custom-object eligibility if this is the last Enterprise Hub, sequence enrollment automation, reporting/governance limits and calling capacity.

Unknown

Which current and incoming users need which capabilities during the transition?

Evidence: audit · catalog · sequences · downgrade

Features

Tickets, Help Desk, routing, knowledge base, surveys, SLAs, customer-service reporting and advanced assistance where licensed.

Example

An OA support team triages tickets while designated service specialists manage advanced Help Desk views and SLAs.

Evidence

Professional licensed: five purchased and five active Service assignments; nine ticket pipelines and 1,332 active tickets.

Who

Support operators; advanced Help Desk features need an assigned Service seat. Basic ticket access also requires appropriate permissions.

License

Current five seats $350; proposal estimates two Pro seats $200. Current Pro ticket-pipeline limit is 15.

Removal

Reducing seats is not a tier downgrade. Core cannot replace every advanced service workflow, but not everyone touching a ticket necessarily needs a Service seat.

Unknown

Who owns SLAs, routing and coverage after the proposed team merger?

Evidence: audit · helpdesk · seats · catalog

Features

Data sync, custom mappings, data quality, Data Studio and advanced automation including custom code, webhook actions and formatting; features depend on tier.

Example

A call-booked workflow hands data to an external integration. Its successful downstream receipt must be proven before replacement.

Evidence

Professional licensed at $480. One enabled webhook workflow, two disabled custom-code workflows; installed-app and sync configuration inventory incomplete.

Who

Infrastructure and operations owners; Stephen should coordinate technical dependency validation.

License

Pro workflow allowance 400; highest Hub allowance wins rather than adding limits. Public Data Pro starts at $800 with one Core seat; current discounted price differs.

Removal

Lost Data-only actions fail and advance; custom sync mappings are lost and syncs turn off. Reporting capacity and the included Core seat also need review.

Unknown

What mappings, datasets, scheduled/event triggers and reports depend on Data?

Evidence: audit · actions · downgrade · catalog

Features

Website and landing pages, blog, content tools, HubDB and related CMS capabilities; availability varies by tier.

Example

A landing page can collect webinar registrations and connect the resulting contact to marketing follow-up. This is a teaching example, not a newly built account flow.

Evidence

Zero website pages, zero landing pages and one blog post in the retrieved collections. Content paid tier is not established by billing evidence.

Who

Content and web teams when these tools are the chosen publishing system.

License

Do not infer a paid Content subscription from an accessible API or a file library. No Content price is included in these scenarios.

Removal

No Content removal is proposed. Zero pages in an accessible collection does not prove no other CMS dependency.

Unknown

Design-manager assets, knowledge base, podcasts, case studies and broader content usage were not fully inventoried.

Evidence: audit · catalog

Features

Quotes/CPQ, invoices, payment links, payments and subscriptions where offered and licensed; payment processing and fees are separate.

Example

An invoice linked to a customer relationship is a business CRM object, not the invoice HubSpot sends for its software subscription.

Evidence

Aggregate CRM counts include 5,022 invoices, 5,106 payments and 479 subscriptions; zero quotes in the retrieved search. No customer financial details are published.

Who

Revenue operations and finance under the appropriate access policy.

License

A standalone Commerce paid tier, processing contract and exact CPQ entitlement were not established. No invented price is added to renewal math.

Removal

No Commerce change is authorized. Integrations may create records; record existence is not proof of a purchased Commerce package.

Unknown

Payment-link and marketing-event product inventories remain incomplete.

Evidence: audit · catalog

Features

AI-assisted work, agent capabilities and enrichment can have different access, credits and configuration requirements.

Example

Enrich-record actions appear in the automation audit; their presence does not prove an active paid Data dependency or measured ROI.

Evidence

Two enrich-record action nodes were observed. Credit balance, consumption, AI adoption and effective feature access were not measured.

Who

Tool owners who can define a useful outcome and approve data access.

License

Treat credits, feature permissions and subscriptions as separate gates. Do not assume included credits cover expected production volume.

Removal

Removing a Hub does not have a single universal AI consequence; map each configured feature to its actual entitlement.

Unknown

Which AI tasks are in use, who approves them, and what credit cost is acceptable?

Evidence: audit · catalog · actions