How an advisory firm whose advisors work in Wealthbox and whose marketing runs in HubSpot can keep contacts, households, opportunities and client activity in step, or move to HubSpot in phases, with HubSpot as the place where marketing, client data and growth reporting come together.
Wealthbox is a CRM built for financial advisors. Advisors use it to manage clients, households, tasks, notes, opportunities and repeatable workflows. Many firms keep advisors in Wealthbox while firm marketing runs in HubSpot; others plan to move everyone to HubSpot over time. Both need the two systems to agree on who each client is and where each opportunity stands.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. The API is documented publicly. Personal access tokens are self-serve for in-house integrations; OAuth apps are registered through Wealthbox support.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Wealthbox exposes its CRM data through a documented REST API, so HubSpot can hold the firm-wide client and growth picture while advisors keep working in Wealthbox.
Campaign Creators assessment
The Wealthbox API (base URL api.crmworkspace.com, paths under /v1) reads and writes contacts, households, opportunities, tasks, events, notes, projects and workflows, reads the activity stream, and lists users, tags and custom fields. It supports OAuth 2.0 for partner apps and personal access tokens for in-house integrations. That makes a direct Wealthbox-to-HubSpot integration buildable. Three things shape the design: the API is throttled to about one request per second; the public reference documents no webhooks, so changes are read from the activity stream on a schedule; and the firm's compliance team decides which client data and notes HubSpot may hold.
Ratings are CC judgments from Wealthbox's public API reference. Opportunity field names and the firm's custom fields are confirmed in discovery.
Contacts carry a type (person, household, organization, trust), a contact type (client, past client, prospect), household membership, the assigned advisor, tags, custom fields and an external unique ID for cross-referencing.
Advisors edit in Wealthbox and marketing edits in HubSpot. Every synced field gets one owner, written into the SOW, so the two systems never overwrite each other.
Wealthbox allows about one request per second over a five-minute window and returns 429 above that. The sync reads the activity stream on a schedule, and backfill is paced to fit.
Seven parts of Wealthbox matter to HubSpot. Five carry the integration, one supplies reference data, and one is a scope decision for firms planning a move.
People, households, organizations and trusts. People become HubSpot contacts; households and organizations become companies, with members associated.
New business advisors are working. Opportunities map to HubSpot deals through a stage table; Wealthbox stages are customizable per firm.
Advisor tasks, meetings and notes. They land on the HubSpot timeline so marketing and service see the whole relationship.
Repeatable processes such as onboarding or annual review, built from templates with steps and milestones. Progress shows in HubSpot, and HubSpot can start a workflow.
A feed of changes across the workspace, filterable by contact, type and time. It is how the sync finds what changed without reading every record.
Lists of the firm's users, teams, tags and custom field definitions. They keep owners, segments and field mappings correct.
Firms that plan to run everything in HubSpot can move advisors in waves. The same integration keeps both systems current until the last wave, then Wealthbox history is loaded and the sync is retired.
A CC-built integration layer reads Wealthbox changes on a schedule, applies the field ownership rules, resolves each record to one HubSpot contact, company or deal, and writes in batches. HubSpot sends new prospects, marketing context and workflow starts back to Wealthbox.
Marketing, client data and growth reporting come together in HubSpot. Wealthbox stays where advisors run their day.
Each field syncs in one direction unless the firm chooses otherwise. Advisors own contact type and opportunity stage; marketing owns source and subscription status.
The compliance team approves which fields and note categories reach HubSpot. Planning details such as risk tolerance stay in Wealthbox unless approved.
Each phase ends on a gate the firm signs off before the next begins. Contacts and households go live first; opportunities, activity and workflows follow.
Confirm which teams use each system, the number of contacts, and the target: lasting coexistence or a phased move. Register an OAuth app with Wealthbox, or create an access token for a dedicated integration user.
List every field to sync, choose its owner and direction, and agree match rules: Wealthbox ID first, then email for people and name for households.
Map Wealthbox opportunity stages to a HubSpot pipeline, contact types to lifecycle stages, and workflow templates to the HubSpot events and properties that track them.
Agree the field list, which note categories may be copied, and how client communications sent from HubSpot are archived under the firm's SEC and FINRA recordkeeping obligations.
Create the properties, pipeline and property groups in a HubSpot sandbox. Build the auth client, throttled reader, ownership rules, identity resolver, activity sync and error replay queue.
Load current contacts, households and open opportunities, plus an agreed history window, paced against the throttle.
Run both systems side by side for two weeks with HubSpot workflows paused, review conflicts daily, then switch on prospect hand-off and automations.
Field names follow Wealthbox's API reference where it publishes them. Opportunity field names and the firm's custom fields are confirmed in discovery.
| Wealthbox field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Contacts and households | ||||
| id | wb_contact_id | Contact | WB → HS | Match key. Unique. |
| first_name, last_name | firstname, lastname | Contact | ↔ Both | Owner set in the ownership matrix. |
| email_addresses (principal) | Contact | ↔ Both | Match key #2. Extra addresses stay in Wealthbox. | |
| phone_numbers | phone | Contact | ↔ Both | Principal number. |
| street_addresses | address, city, state, zip | Contact | ↔ Both | Principal address. |
| type | Contact or Company | Contact / Company | WB → HS | Person to contact; Household and Organization to company; Trust decided in discovery. |
| contact_type | lifecyclestage, wb_contact_type | Contact | ↔ Both | HubSpot sets Prospect for new leads; Wealthbox owns Client and Past Client. |
| household | Contact to company association | Contact | WB → HS | Household members associated with a household label. |
| assigned_to | hubspot_owner_id | Contact | ↔ Both | Matched on user email from the users list. |
| tags | wb_tags | Contact | ↔ Both | Multi-select kept in step with Wealthbox tags. |
| client_since | wb_client_since | Contact | WB → HS | Date the contact became a client. |
| referred_by | wb_referred_by | Contact | WB → HS | Referral reporting. |
| external_unique_id | HubSpot record ID | Contact (Wealthbox) | HS → WB | Cross-reference. Confirm it is writable for the firm. |
| Planning profile · compliance-gated | ||||
| investment_objective | wb_investment_objective | Contact | WB → HS | Off by default. |
| risk_tolerance | wb_risk_tolerance | Contact | WB → HS | Off by default. |
| assets | wb_assets | Contact | WB → HS | Off by default. Restricted by field-level permissions. |
| Opportunities | ||||
| id | wb_opportunity_id | Deal | WB → HS | Match key. Unique. |
| name | dealname | Deal | ↔ Both | |
| stage | dealstage | Deal | ↔ Both | Mapped through the signed stage table. |
| Amount | amount | Deal | WB → HS | Amount types and field name confirmed in discovery. |
| Expected close date | closedate | Deal | WB → HS | Field name confirmed in discovery. |
| Linked contact | Deal to contact association | Deal | ↔ Both | |
| Activity and workflows | ||||
| Tasks | Tasks | Task | ↔ Both | Name, due date, assignee and completion. |
| Events | Meetings | Meeting | WB → HS | Client meetings on the timeline. |
| Notes | Notes | Note | WB → HS | Only categories compliance approves. |
| workflows (label, workflow_template) | wb_active_workflows | Contact | WB → HS | Multi-select of active workflow templates. |
| Completed workflow steps | Custom event: Workflow step completed | Contact | WB → HS | Milestones such as onboarding complete. |
| Closed-won deal | Workflow from template | Workflow (Wealthbox) | HS → WB | Starts the onboarding workflow. |
Wealthbox access is self-serve for in-house integrations, and registered through Wealthbox support for OAuth apps. Values Wealthbox does not publish are marked for confirmation.
| Topic | Wealthbox | HubSpot |
|---|---|---|
| Access model | OAuth apps are registered with Wealthbox support for a client ID and secret. Personal access tokens are created in Wealthbox settings for personal and in-house integrations. | Self-serve in the client portal. Field-level permissions need an Enterprise hub. |
| Interfaces | Wealthbox API v1, REST over HTTPS with JSON. Base URL api.crmworkspace.com, paths under /v1. Page-based pagination; the activity stream uses a cursor. | REST APIs: CRM objects, associations, engagements, custom events. |
| Authentication | OAuth 2.0 authorization code and refresh token grants with a Bearer token (scopes: login, data), or a personal token in the ACCESS_TOKEN header. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Token handling | OAuth access tokens last 2 hours; refresh tokens last 90 days. The integration refreshes on schedule and alerts before a refresh token lapses. | Private app tokens do not expire; OAuth tokens refresh. |
| Change detection | No webhooks in the public API reference. The activity stream filters by contact, type, updated_since and updated_before. | Webhooks for HubSpot-side changes; writes are immediate. |
| Rate limits | About one request per second over a five-minute sampling period, with short bursts allowed. Over the limit returns 429. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Client profiles, planning details and advisor notes. Only approved fields and note categories are read. | Sensitive data properties on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
Advisors and marketing both touch contacts. The signed ownership matrix decides each field's owner, and conflicts are logged for review rather than overwritten.
Planning details and advisor notes are sensitive. The compliance team approves the field list and note categories before the build.
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.
At about one request per second, a large book takes hours to backfill. CC paces the load and runs it outside business hours.
Changes are read from the activity stream on a schedule, so HubSpot is minutes behind Wealthbox, not seconds. Agree the interval in discovery.
In Wealthbox a household is itself a contact with members. CC maps it to a HubSpot company and agrees how to handle a person who moves between households.
Every client and prospect across all advisors is in HubSpot, segmented by contact type, tags and household, with the right advisor as owner.
A qualified HubSpot prospect becomes a Wealthbox contact and opportunity for the right advisor, with the marketing history attached.
A closed-won deal starts the Wealthbox onboarding workflow, and completed milestones show on the HubSpot record.
Opportunities, new clients and referrals appear in HubSpot dashboards beside campaign results.
Meetings logged in Wealthbox show when each client was last seen, so HubSpot can flag households overdue for a review.
Firms that choose to consolidate can move advisors to HubSpot in waves, using the same mapping and ownership rules.
The integration is delivered in layers, so each one is working before the next is added. Firms planning a full move use the same layers, then move advisors in waves.
All custom properties use the wb_ prefix in a Wealthbox property group. Values Wealthbox owns are read-only to HubSpot users.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| wb_contact_id | Wealthbox Contact ID | Contact | Single-line text | Wealthbox contact ID; unique |
| wb_household_id | Wealthbox Household ID | Company | Single-line text | Household contact ID; unique |
| wb_contact_type | Wealthbox Contact Type | Contact | Dropdown | Client, Past Client, Prospect, Vendor, Organization |
| wb_tags | Wealthbox Tags | Contact | Multiple checkboxes | Tags list kept in step |
| wb_client_since | Client Since | Contact | Date picker | client_since |
| wb_referred_by | Referred By | Contact | Single-line text | referred_by |
| wb_investment_objective | Investment Objective | Contact | Dropdown | investment_objective; compliance-gated |
| wb_risk_tolerance | Risk Tolerance | Contact | Dropdown | risk_tolerance; compliance-gated |
| wb_assets | Assets (Wealthbox) | Contact | Number (currency) | assets; restricted |
| wb_opportunity_id | Wealthbox Opportunity ID | Deal | Single-line text | Wealthbox opportunity ID; unique |
| wb_active_workflows | Active Workflows | Contact | Multiple checkboxes | Active workflow templates |
| wb_last_meeting | Last Client Meeting | Contact | Date picker | Latest Wealthbox event with the contact |
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.
Based on Wealthbox's public API reference and product materials. Each item marked for confirmation is verified with Wealthbox and the firm during discovery.
Yes. Wealthbox publishes a documented REST API that reads and writes contacts, households, opportunities, tasks, events, notes and workflows, so Campaign Creators builds a direct custom integration on it. Advisors keep working in Wealthbox while HubSpot holds the firm-wide client and growth picture.
People sync to HubSpot contacts, and households and organizations to companies with their members associated. Opportunities become HubSpot deals through a stage table, tasks and events land on the timeline, and active workflows show on the contact. HubSpot sends new prospects, marketing context and workflow starts back to Wealthbox.
Every synced field has one owner, written into the SOW. Advisors own contact type and opportunity stage in Wealthbox; marketing owns source and subscription status in HubSpot. The firm's compliance team decides which fields and note categories reach HubSpot.
Seven phases, each closed by a client sign-off: discovery and access, field ownership and identity, pipeline and workflow mapping, a compliance plan, HubSpot setup and build, a backfill paced to Wealthbox's API throttle, and a two-week parallel run before automations are switched on.
Timeline and cost depend on the objects, custom fields and history in scope, the compliance rules, and whether the firm wants lasting coexistence or a phased move to HubSpot. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.