Custom Objects and Advanced Use Cases in HubSpot–Salesforce: ABM, Renewals, and Product Catalog Sync

Published by Bles Software, a custom software and AI company based in Yehud-Monoson, Israel, building web apps, AI agents and API integrations for clients in Israel, the US, the UK and the EU.

Once your core HubSpot–Salesforce integration is stable, the next wave of value comes from modeling your business more precisely: the accounts you target, the products you sell, the subscriptions you renew, and the relationships that tie them together. This playbook covers practical patterns for using custom objects and advanced configurations to power ABM, renewals, and product catalog sync—without creating chaos or brittle dependencies.

We will focus on survivable designs that give marketing and sales what they need while protecting a single source of truth for commercial data. Expect a handful of simple schemas, clear directionality, and repeatable processes for rollout and governance.

Principles for Custom Object Design

Custom objects succeed when they are small, named after business concepts everyone understands, and mapped to real revenue outcomes. Resist the urge to encode every nuance. Your north star is explainability: anyone reading a record should know what it represents and which team owns it.

Follow three principles:

These principles make complexity tractable and integrations resilient.

ABM: Accounts, Buying Groups, and Programs

Account‑based motions hinge on precise targeting and synchronized action. Your integration should represent accounts with the fields you use to qualify, segment, and route (industry, size, region, ideal customer profile fit), plus the relationships that connect contacts and opportunities.

In Salesforce, Accounts remain the commercial backbone; HubSpot mirrors key fields for segmentation. To model buying groups, you can use Contact Roles on Opportunities in Salesforce and static/dynamic lists in HubSpot to represent who’s involved. If you need richer structure, consider a simple custom object called Buying Group with relationships to Account, Contacts, and active Opportunities. Keep its schema deliberately small: name, status, primary initiative, and target segment.

Programs (e.g., “2025 Manufacturing ABM”) can be represented as Campaigns in Salesforce and as Program lists and workflows in HubSpot. Sync campaign membership to power targeted emails and ad audiences. Do not duplicate the campaign’s financials in HubSpot; keep dollars in Salesforce and in your BI layer.

Renewals: Subscriptions and Entitlements

For recurring revenue, sales needs renewal visibility and marketing needs to orchestrate pre‑renewal communications. Model subscriptions as a custom object in Salesforce with relationships to Account and Opportunity. Key fields include product family, term start/end, next renewal date, amount, and status. HubSpot should mirror the subset needed for segmentation (product family, renewal date, status) and should never write commercial changes back.

With this mirror in place, HubSpot can drive a renewal nurture that adapts to status (active, at risk, lost) and to term left (90/60/30 days). Sales can see which contacts engaged and tailor outreach accordingly. One set of subscription facts, two different operating motions.

Product Catalog and Bundles

Many teams try to push the full product catalog into HubSpot. Resist that unless you are powering a self‑serve commerce motion. Instead, mirror only the product families and flags that matter for segmentation—e.g., whether the account owns Module A or Module B. In Salesforce, keep the full catalog with price books. If marketing needs to personalize messaging based on ownership, store a boolean or short set of enumerations in HubSpot that read from Salesforce.

For bundles, let Salesforce calculate bundle composition and pricing. HubSpot should not attempt to reconstruct order math. When in doubt, mirror less and link more.

Events and Triggers Across Systems

Advanced use cases depend on timely signals: usage drops, a support escalation, a renewal quote created. Represent these as events with timestamps and minimal context, not as wide tables. HubSpot only needs the event type, who it affects, and when it happened to trigger the right play. Store details in the source system and link back if needed.

Build a small event gateway in your integration that translates signals into HubSpot‑friendly properties or custom objects. Keep it opinionated and narrow to avoid event sprawl.

Data Directionality and Guardrails

For every custom object or mirrored property you add, restate the three decisions: who creates it, who updates it, and who reads it. For subscriptions, Salesforce creates and updates; HubSpot reads. For ABM programs, Salesforce Campaigns and HubSpot workflows both create useful constructs, but dollars and pipeline stay in Salesforce.

Guardrails keep teams from inadvertently breaking each other’s work. Write‑protect commercial fields in HubSpot. Validate referential integrity in Salesforce so a subscription cannot point to a deleted Account. Track schema changes in a versioned document so you can answer, “Who added this field and why?”

Reporting and Explainability

If your schema is clear, your reporting is faster. For ABM, you should be able to answer: which accounts are in‑program, who is in the buying group, which campaigns touched them, and what pipeline resulted. For renewals: how much ARR is due in each window, which accounts are at risk, which contacts engaged with the renewal sequence, and what the ultimate outcome was.

Keep revenue math in Salesforce and your BI layer. Use HubSpot to drive messages and capture engagement, not to own ARR numbers.

Rollout Patterns

Roll out one advanced use case at a time with a thin vertical slice: one schema change, one workflow, one report. For ABM, pilot a single segment (e.g., manufacturing). For renewals, pilot a single product family or region. Measure signal quality, operational effort, and results. Expand only after you can run a weekly review meeting using the new data without confusion.

Maintenance and Sunsetting

Custom objects accumulate over time. Schedule quarterly schema hygiene: deprecate fields that no longer drive decisions, archive programs no longer in market, and prune unused properties in HubSpot. Add a “sunset” status to custom objects, so you can retire them gradually while preserving history.

Security and Privacy

Advanced objects can include sensitive information: pricing, entitlements, and support data. Limit exposure in HubSpot to only what marketing needs. Consider field‑level security in Salesforce and property permissions in HubSpot. Review who can export data from both systems and ensure your privacy notices cover the data flows you’ve implemented.

FAQ

Should we replicate the entire product catalog into HubSpot?

Usually no. Mirror only segmentation‑critical facts like product family ownership or key capability flags. Keep full catalog structure and pricing in Salesforce.

How do we represent buying groups without creating a complex object graph?

Start with Contact Roles on Opportunities and lists in HubSpot. If you truly need a separate object, keep it small and tied to specific workflows and reports.

Where should subscription truth live?

Salesforce. Use a Subscription custom object related to Account and Opportunity. HubSpot reads what it needs to orchestrate communications.

Can HubSpot update renewal dates or amounts?

Avoid it. HubSpot should not write commercial facts. If renewal events need to originate in HubSpot (e.g., a self‑serve flow), send a request to Salesforce to create or update the subscription there.

What’s the best way to pass product usage signals to HubSpot?

Emit small, timestamped events that drive lists and workflows. Avoid copying large usage tables; link back to the source for detail.

More RevOps Playbooks from Bles Software