Sync properties
Each CRM sync configuration lists which FunnelStory fields to copy into Salesforce or HubSpot. This page summarizes the categories you can opt into; the live form only shows resources your workspace actually has (models, funnels, metrics, signals, etc.).
Account sync payloads
When sync type is Account, you can typically include any combination of:
| Category | What gets sent |
|---|---|
| Account properties | Mapped Account model columns you select (including custom properties). |
| Account activities | Chosen product or non-product activities summarized for the account. |
| Subscription properties | Fields such as subscription type, valid from, valid until when subscriptions are modeled. |
| Signals | Workspace signals you pick from the list. |
| Account metrics | Configured account metrics (for example health components) with the aggregations you select in the form. |
| Account traits | Enrichment-backed or derived traits enabled for sync (connect Apollo or Clearbit—or your workspace’s enrichment source—so traits exist to map). |
HubSpot account sync can also target Deal, Company, or a custom object—see HubSpot sync.
User sync payloads
When sync type is User, you select parallel categories for users (properties, activities) plus, where offered, account-level subscription slices for the account the user belongs to, so contact-level automation in the CRM still reflects contract context.
Custom mapping and naming
- HubSpot — You define a property group name; FunnelStory writes managed properties inside that group so CRM admins can distinguish FunnelStory-owned fields.
- Salesforce — Field mappings follow your admin’s configuration for the sync template; custom objects or fields may be provisioned as part of onboarding—confirm with your FunnelStory implementation contact if you need a new target field.
Choosing what to sync
- Start with the smallest set of properties teams actively use in the CRM.
- Add metrics and signals once stakeholders agree on definitions (to avoid noisy or confusing CRM fields).
- Keep traits behind feature flags or pilot sandboxes until enrichment quality is validated.
Related
- CRM sync overview — schedules, runs, and navigation.
- HubSpot sync and Salesforce sync — CRM-specific steps.
- Data models overview — where account and user fields originate.