Addepar × HubSpot
How an RIA, family office or private bank running Addepar can bring households, clients, assets under management and asset-class exposure into HubSpot, aggregated to the household and limited to what compliance approves, so growth, onboarding and client reviews run from one CRM.
Does Addepar integrate with HubSpot?
Addepar is a wealth data platform used by RIAs, family offices and private banks. It models every client, account, trust and holding company as an entity, collects them into groups such as households, and calculates values and exposures across them.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. The API is documented publicly. A firm administrator grants API permission and creates the key; OAuth clients are set up through the firm's Addepar contact.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Addepar can give HubSpot household-level AUM and asset-class exposure, through a documented REST API the firm controls.
Campaign Creators assessment
The Addepar API runs on the firm's own Addepar domain under /api/v1 and follows the JSON:API format. Ownership resources (entities, groups, positions, external IDs) describe who owns what. The portfolio query endpoint and the Jobs API return values and exposures for an entity, a group or the whole firm. Access is by API key and secret over HTTP Basic auth, or by OAuth 2.0 with scopes such as PORTFOLIO, ENTITIES and GROUPS. That makes a direct Addepar-to-HubSpot integration buildable. Two things shape the design: Addepar limits each firm to 50 requests per 15 minutes and 1,000 per day, so data moves in a few large scheduled exports rather than many small calls; and the firm's compliance team approves which client data HubSpot may hold.
Ratings are CC judgments from Addepar's public developer documentation. The firm's household setup, custom attributes and query columns are confirmed in discovery.
An ownership model with external IDs
Clients, accounts, trusts and holding companies are entities, and households are groups of them. An external ID type for HubSpot lets each entity carry its HubSpot record ID, so the two systems cross-reference cleanly.
A call budget shared across the firm
Addepar allows 50 requests per 15 minutes and 1,000 per 24 hours per firm, shared with every other integration the firm runs. The sync uses Jobs API exports and a fixed read plan, sized in discovery.
Permissions and compliance first
An API key carries the data permissions of the user who created it. A dedicated integration user with approved data access, and a signed field list from compliance, come before any build.
Which Addepar APIs does the integration use?
Seven parts of the Addepar API are relevant to HubSpot. Four carry the integration, one enriches it, one is a scope decision, and one stays inside Addepar.
Entities: clients and accounts
Ownership · /v1/entitiesEvery client (PERSON_NODE), financial account (FINANCIAL_ACCOUNT), trust and holding company is an entity, with standard and firm-defined attributes.
- Client entities become HubSpot contacts
- Accounts as a Financial Account custom object
- Firm custom attributes read alongside standard ones
Groups and households
Ownership · /v1/groupsGroups collect entities. A household group becomes a HubSpot company, with its member clients as associated contacts.
- Members and child groups readable through the API
- Household group type confirmed in discovery
- Group name and custom attributes carried over
Portfolio query and Jobs API
/v1/portfolio/query · /v1/jobsValues and exposures for an entity, a group or the whole firm. Jobs run large queries asynchronously, so one scheduled export can cover every household.
- Household AUM and asset-class mix
- Results available for 24 hours after the job is created
- One query specification agreed with operations
External IDs
/v1/external_id_typesAn external ID type for HubSpot lets each Addepar entity store its HubSpot record ID, and portfolio queries can look entities up by that ID.
- One external ID type for HubSpot
- Written by the integration on first match
- Visible as a column in Addepar's analysis tool
Contacts, users and teams
/v1/contacts · /v1/users · /v1/teamsAddepar contacts are the people who can sign in to the Client Portal, with emails, phone numbers and links to the entities and groups they can see. Users and teams describe the firm's own staff.
- Client emails and phone numbers for HubSpot matching
- Portal access status for onboarding
- Advisor assignment from a team or firm attribute, confirmed in discovery
New clients from HubSpot
HubSpot → AddeparWhen a prospect becomes a client in HubSpot, the integration could create the client entity or the portal contact in Addepar. Many firms keep client setup in Addepar with operations. Decided per engagement.
- Off by default
- Triggered by a closed-won deal
- Operations review before creation
Holdings, transactions and reports
Positions · Transactions · ReportsPositions, transactions, performance and generated reports stay in Addepar. HubSpot receives household rollups only.
- No position-level holdings by default
- No transaction history in HubSpot
- Report delivery stays in the Client Portal
How does the Addepar HubSpot integration work?
A CC-built integration layer reads Addepar on a schedule, rolls values up to the household, applies the compliance rules and writes to HubSpot in batches. HubSpot owns prospects, relationships and client communication; Addepar owns ownership structures, values and performance.
Each system owns its records
Addepar is the book of record for ownership, values and performance. HubSpot is the system of record for prospects, relationships and client communication.
Aggregate before data leaves Addepar
HubSpot keeps household totals, tiers and asset-class percentages. Positions and transactions stay in Addepar.
Permissions travel with the data
The integration user sees only what compliance approves. HubSpot field-level permissions limit exact AUM to the advisors and teams who need it.
What does Addepar HubSpot integration setup involve?
Each phase ends on a gate the firm signs off before the next begins. Read-only data goes live first; write-back to Addepar is a later decision.
Goals and inventory
Confirm how the firm models households, clients and accounts in Addepar, which attributes hold advisor and custodian, and which growth and service decisions HubSpot should support.
Access
Create a dedicated integration user with API Access permission and approved data access, then issue an API key or set up an OAuth client through the firm's Addepar contact. Complete the firm's vendor security review.
Call budget and query design
Agree the portfolio query (columns, groupings, dates) with operations and plan reads within 50 requests per 15 minutes and 1,000 per day, leaving room for the firm's other integrations.
Compliance plan
Agree the field list, who may see exact AUM, and how client communications sent from HubSpot are archived under the firm's SEC and FINRA recordkeeping obligations.
HubSpot data model and build
Create the properties, the Financial Account custom object, association labels, pipelines and field-level permissions in a HubSpot sandbox. Build the auth client, readers, rollups, masking and an error replay queue, and write HubSpot IDs to Addepar as external IDs.
Backfill
Load current households, clients, accounts and values once, then switch to scheduled jobs.
Workflows, parallel run & launch
Build onboarding, review-cadence and segmentation workflows with sends paused, run two weeks in parallel, then switch on.
What does the Addepar HubSpot integration sync?
Resource and attribute names follow Addepar's developer documentation. Firm-defined attributes (such as advisor or custodian) and the exact portfolio query columns are confirmed in discovery.
| Addepar field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Households and groups | ||||
| Group ID | adp_group_id | Company | Addepar → HS | Primary match key for households. Unique. |
| Group name | name | Company | Addepar → HS | Addepar is the source for the household name. |
| Group members | Contact to company association | Company | Addepar → HS | Member clients associated with a household label. |
| Firm group attributes | adp_* properties | Company | Addepar → HS | Mapped by name. Confirm in discovery. |
| Advisor (team or firm attribute) | hubspot_owner_id | Company / Contact | Addepar → HS | Mapped through an advisor-to-user table. |
| Clients and portal contacts | ||||
| Client entity ID | adp_entity_id | Contact | Addepar → HS | Primary match key for clients. Unique. |
| original_name | firstname, lastname | Contact | Addepar → HS | Split on agreed rules. Portal contact names used when present. |
| emails[].email | Contact | Addepar → HS | Match key #2. Fill blanks only. | |
| phone_numbers[].number | phone | Contact | Addepar → HS | Fill blanks only. |
| portal_access | adp_portal_access | Contact | Addepar → HS | Client Portal status. Drives an onboarding task. |
| entity_affiliations, group_affiliations | Associations | Contact | Addepar → HS | Links portal contacts to clients and households. |
| HubSpot record ID | external_id_hubspot (entity attribute) | Client entity | HS → Addepar | External ID type created once for HubSpot. |
| Accounts | ||||
| Account entity ID | adp_account_id | Financial Account | Addepar → HS | Match key. One record per Addepar account. |
| original_name | adp_account_name | Financial Account | Addepar → HS | Account numbers masked to the last four characters. |
| Custodian | adp_custodian | Financial Account | Addepar → HS | Attribute name confirmed in discovery. |
| created_at | adp_account_added | Financial Account | Addepar → HS | Date the account was added to Addepar. Drives onboarding. |
| Account value | adp_account_value | Financial Account | Addepar → HS | Off by default. Restricted like household value. |
| Values and exposure | ||||
| Household value (portfolio query) | adp_household_aum | Company | Addepar → HS | Exact figure, restricted by field-level permissions. |
| AUM tier | adp_aum_tier | Company | Addepar → HS | Calculated from household value. Visible to marketing. |
| Value date | adp_value_date | Company | Addepar → HS | End date of the query the value reflects. |
| Asset-class exposure | adp_equity_pct, adp_fixed_income_pct, adp_alternatives_pct, adp_cash_pct | Company | Addepar → HS | Percent of household value. Classes follow the firm's Addepar setup. |
| Client value | adp_client_aum | Contact | Addepar → HS | For clients outside a household. Restricted. |
| Lifecycle | ||||
| Prospect won | New client entity | Entity | HS → Addepar | Off by default. Scope decision. |
| Prospect won | Portal contact and invite | Contact (Addepar) | HS → Addepar | Off by default. Operations sends the invite. |
How are authentication and API limits handled?
Addepar access is issued by the firm's own administrators or through its Addepar contact. Values Addepar does not publish are marked for confirmation.
| Topic | Addepar | HubSpot |
|---|---|---|
| Access model | A firm administrator grants API Access permission and creates an API key and secret under Firm Settings. OAuth clients are set up through the firm's Addepar contact. | Self-serve in the client portal. Custom objects and field-level permissions need an Enterprise hub. |
| Interfaces | Addepar API, REST over HTTPS in JSON:API format. Base URL on the firm's Addepar domain, path /api/v1, with an Addepar-Firm header on every call. | REST APIs: CRM objects, associations, imports. |
| Authentication | HTTP Basic with API key and secret, or OAuth 2.0 authorization code flow with scopes such as PORTFOLIO, ENTITIES, GROUPS and USERS. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Token handling | OAuth access tokens last 60 minutes and renew with the refresh token. An API key carries the same data permissions as the user who created it. | Private app tokens do not expire; OAuth tokens refresh. |
| Exports | Jobs API runs portfolio queries asynchronously, with a four-hour timeout. Results are deleted 24 hours after the job is created. | Batch endpoints handle volume; writes are immediate. |
| Rate limits | Per firm: 50 requests per 15 minutes, 1,000 per 24 hours, and 60 seconds per request. Over the limit returns 429 with a retry-after header. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Client, account and value data, including tax and personal details on portal contacts. Only approved fields are read; account numbers are masked. | Sensitive data properties on Enterprise; field-level permissions by team. |
What should you plan for, and what does the integration unlock?
Severity reflects impact on the SOW, not technical difficulty alone.
Challenges to plan for
Addepar's limits apply to the whole firm, across every integration. The read plan uses Jobs API exports and a fixed schedule, and is signed off before the build.
Values, accounts and personal details are sensitive. The compliance team approves the field list and who sees exact AUM before the build. Holdings detail is off by default.
Emails and messages sent to clients from HubSpot fall under the firm's SEC and FINRA recordkeeping and supervision obligations. Plan the archiving connection as a project item; the compliance team decides the method.
Firms model households as groups, often with their own group type and attributes. Discovery confirms the structure before mapping starts.
AUM and exposure depend on columns, groupings and dates. CC fixes one query specification with operations so HubSpot matches Addepar reports.
Creating clients or portal contacts from HubSpot saves time but touches the book of record. Keep it off until operations has seen the read-only integration working.
Opportunities in HubSpot
Prospects move through a HubSpot pipeline, and the deal closes when Addepar shows the client and its first account.
New accounts and Client Portal access drive onboarding stages and tasks, so operations and advisors see every client not yet fully set up.
Marketing targets households by tier and asset-class mix without seeing exact values, and advisors see the full figure on their own records.
Each household gets a review frequency by tier. HubSpot tracks the last review and creates a task when the next one is due.
Each advisor sees their households ranked by AUM, last review and open service items.
New households, new assets and conversion rates by source and advisor appear in HubSpot dashboards beside marketing results.
From prospect to reviewed client, in one record.
HubSpot runs the relationship from first touch. Addepar confirms each milestone with data from the book of record.
- Prospect enters HubSpot and moves through the advisory pipeline.
- Deal closes; the client appears in Addepar and its HubSpot ID is stored as an external ID.
- Accounts and Client Portal access move the household through onboarding.
- Household AUM, tier and asset mix set the review cadence and the segments it belongs to.
Which HubSpot properties does the integration create?
All custom properties use the adp_ prefix in an Addepar property group. Rollups, tiers and percentages are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| adp_entity_id | Addepar Client ID | Contact | Single-line text | Client entity ID; unique |
| adp_group_id | Addepar Household ID | Company | Single-line text | Household group ID; unique |
| adp_household_aum | Household AUM | Company | Number (currency) | Portfolio query value; restricted |
| adp_aum_tier | AUM Tier | Company | Dropdown | Tier bands agreed with the firm |
| adp_value_date | Value Date | Company | Date picker | End date of the value query |
| adp_equity_pct | Equity % | Company | Number | Share of household value |
| adp_fixed_income_pct | Fixed Income % | Company | Number | Share of household value |
| adp_alternatives_pct | Alternatives % | Company | Number | Share of household value |
| adp_cash_pct | Cash % | Company | Number | Share of household value |
| adp_portal_access | Client Portal Access | Contact | Dropdown | Contact portal_access status |
| adp_account_id | Addepar Account ID | Financial Account | Single-line text | Account entity ID; unique |
| adp_review_frequency | Review Frequency | Company | Dropdown | Set by AUM tier in HubSpot |
Interactive scope builder
Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Scope summary
Sources & verification
Based on Addepar's public developer documentation. Each item marked for confirmation is verified with the firm and Addepar during the access phase.
Addepar HubSpot integration FAQ
Does Addepar integrate with HubSpot?
Yes, through the Addepar API, a documented REST API on the firm’s own Addepar domain. Campaign Creators builds a custom integration layer that reads entities, households and portfolio values on a schedule and writes household-level data to HubSpot, limited to the fields the firm’s compliance team approves.
What data syncs between Addepar and HubSpot?
Household groups sync to HubSpot companies and client entities to contacts, with emails, phone numbers and Client Portal status; accounts sync to a Financial Account custom object; and household AUM, AUM tier and asset-class exposure are written to the company. HubSpot record IDs are stored in Addepar as external IDs, while positions and transactions stay in Addepar.
Which system owns which data?
Addepar is the book of record for ownership structures, values and performance. HubSpot is the system of record for prospects, relationships and client communication. Creating clients in Addepar from HubSpot is off by default and decided per engagement.
What does setting up the Addepar HubSpot integration involve?
Seven phases, each closed by a firm sign-off: goals and inventory, access (a dedicated integration user with an API key or OAuth client), call budget and query design, a compliance plan, the HubSpot data model and build, backfill, and workflows with a two-week parallel run before launch.
How long does the integration take and what does it cost?
Timeline and cost depend on the households, accounts, fields and workflows in scope (for example the firm’s household setup, custom attributes, compliance requirements and Addepar’s per-firm call budget). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.
Ready to Get More From HubSpot?
Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.
.png?width=1920&height=553&name=cc-logo-color%20(2024).png)