Jack Henry × HubSpot
How a bank on SilverLake, CIF 20/20 or Core Director, or a credit union on Symitar, can bring customers, members and the products they hold into HubSpot for onboarding and cross-sell journeys, without moving account numbers or balances out of the core.
Does Jack Henry integrate with HubSpot?
The Jack Henry core is the system of record for every customer or member and every deposit, loan and card they hold. HubSpot is where marketing and service act on that relationship. This assessment shows how to connect them with the least data necessary.
Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.
Open with conditions. jXchange and SymXchange are documented on Jack Henry's developer site, with a sandbox. Production access is set up per institution through Jack Henry's developer programs.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
The core knows what each member holds; HubSpot turns that into the next conversation.
Campaign Creators assessment
Jack Henry exposes its bank cores through jXchange, a native SOAP interface with XML payloads and a REST translation layer, and its Symitar credit union core through SymXchange, a SOAP web service over account, share, loan and name records. Both are documented on Jack Henry's developer site and come with a sandbox for development. Jack Henry also lists bulk data (Operational Data Integration) and event streaming (Enterprise Event System) for institutions that use them. That makes a HubSpot integration buildable. Two things set the pace: production credentials are issued per institution through Jack Henry, and the institution's compliance team decides which customer data HubSpot may hold.
Ratings are CC judgments from Jack Henry's public developer documentation and product materials. Which interfaces an institution has licensed, and their limits, are confirmed with the institution and Jack Henry in discovery.
Documented core APIs with a sandbox
jXchange and SymXchange are documented publicly, and Jack Henry's Vendor Integration Program provides a development environment with a test database of customer and member accounts.
Holdings, not account numbers
HubSpot needs to know that a member has an auto loan or a CD maturing soon. It does not need the account number or balance. The integration sends product flags, dates and counts by default.
Institution credentials and compliance
Production access is set up per institution, often with its own key pair. The compliance team approves the field list, treating GLBA as a planning item, before any build starts.
Which Jack Henry APIs does the integration use?
Seven Jack Henry interfaces and data sources are relevant to HubSpot. Three carry the integration, three extend it where the institution has them, and one is a scope decision.
jXchange
SilverLake · CIF 20/20 · Core DirectorJack Henry's native SOAP interface to its bank cores, with XML payloads and a REST translation layer that maps XML to JSON.
- Customer and account inquiries
- OAuth 2.0 tokens from a key pair
- Shared DMZ sandbox for development
SymXchange
Symitar · credit union coreA SOAP web service over the Symitar database: accounts with their share, loan, name and card records.
getAccountSelectFieldsfor only the fields needed- Share and loan records give product holdings
- PowerOn specfiles for custom extracts
Nightly batch data
Operational Data Integration · core extractsFull holdings for every customer or member, delivered once a day. Jack Henry lists Operational Data Integration for bulk data; Symitar institutions can also produce an extract with a PowerOn specfile.
- The main source for rollups
- Avoids a core call per customer
- Confirm the method each institution uses
Enterprise Event System
Event streamingEvent streaming from Jack Henry systems, for changes HubSpot should act on the same day, such as a new account.
- Account opened and closed signals
- Reduces polling between nightly runs
- Confirm events available to the institution
Banno Digital Toolkit
Digital banking · APIs, plugins, SSOBanno is Jack Henry's digital banking platform. Its toolkit offers APIs, plugins and an authentication framework.
- Digital banking enrollment
- Last digital login, where available
- Confirm institution-level data access
Jack Henry Platform
Cloud-native modules · Digital Core APIsCloud-native core modules connected to the existing core, which stays the system of record. Digital Core has its own API documentation.
- Same HubSpot data model applies
- Adds API options as modules are adopted
- Review at each core change
Account numbers, balances and transactions
Scope decisionOff by default. Balance bands or masked numbers are added only when the compliance team approves a specific use.
- Product flags and dates instead of numbers
- Balance bands, not balances, if approved
- Transaction detail stays in the core
How does the Jack Henry HubSpot integration work?
A nightly batch carries full product holdings, and core APIs or events carry same-day changes. A CC-built integration layer matches each customer or member to a HubSpot contact, turns account records into product flags and dates, drops restricted fields, and writes in batches.
The core stays the system of record
Accounts, balances and identity verification live in the core. HubSpot holds the relationship view that marketing and service act on.
Send the least data that works
Every field must support a named journey. Product flags, dates and counts by default; account numbers and balances only with written approval.
Batch for breadth, real time for moments
The nightly run keeps every record complete. API calls and events are reserved for changes that need a same-day response.
What does Jack Henry HubSpot integration setup involve?
Each phase ends on a gate the institution signs off before the next begins. Onboarding journeys usually go live first, then cross-sell and life events.
Core and journey inventory
Confirm the core (SilverLake, CIF 20/20, Core Director or Symitar), the interfaces the institution licenses, and the journeys marketing and service want to run from HubSpot.
Access and vendor review
Request jXchange or SymXchange access through the institution and Jack Henry, set up the key pair or credentials, and complete the institution's vendor due diligence on the integration layer.
Compliance and data minimization
Agree the field list, the identity key, how product types map to flags, and whether any balance band or masked number is allowed. GLBA and privacy notices are reviewed by the institution's compliance team.
HubSpot data model
Create the Product Holdings custom object, contact rollups, custom events, owner mapping and property groups in a HubSpot sandbox.
Build
Build the nightly batch first, then the same-day API or event path, with idempotent writes and an error replay queue.
Backfill
Load every active customer or member and their current holdings, then compute rollups once so lists and reports start complete.
Journeys, parallel run & launch
Build onboarding, life-event and cross-sell workflows with sends paused, run two weeks in parallel, then switch on.
What does the Jack Henry HubSpot integration sync?
Field names describe core data as Jack Henry's public documentation presents it. Symitar record types come from the SymXchange documentation. Exact element names for each core are confirmed against the jXchange or SymXchange specification in discovery.
| Jack Henry field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customer or member · contact record | ||||
| Customer ID (bank) or person record (Symitar) | jh_core_key | Contact | JH → HS | One-way hash of the core key. Unique. Never the account number. |
| First and last name | firstname, lastname | Contact | JH → HS | Core is the source; HubSpot edits stay in HubSpot. |
| Email address | Contact | JH → HS | Match key alongside the hashed core key. | |
| Phone | phone, mobilephone | Contact | JH → HS | SMS needs separate consent. |
| City, state, ZIP | city, state, zip | Contact | JH → HS | Street address kept out unless approved. |
| Relationship start date | jh_customer_since | Contact | JH → HS | Tenure for segmentation. |
| Age band | jh_age_band | Contact | JH → HS | Computed from date of birth in the integration layer. Date of birth is not stored. |
| Ownership and organization | ||||
| Primary officer | hubspot_owner_id | Contact | JH → HS | Officer code matched to a HubSpot user. |
| Branch | jh_branch | Contact | JH → HS | Drives branch views and routing. |
| Business customer | name, jh_core_key | Company | JH → HS | Business and its signers associated as contacts. |
| Household | Household (company) | Company | JH → HS | Only where the core or institution defines households. |
| Product holdings · custom object | ||||
| Account (bank) or share / loan record (Symitar) | Product Holding | Custom object | JH → HS | One record per product. No account number. |
| Product type | jh_product_type | Product Holding | JH → HS | Checking, savings, CD, loan, card, mortgage. |
| Product code and description | jh_product_code | Product Holding | JH → HS | Institution's own product codes. |
| Open date | jh_open_date | Product Holding | JH → HS | Starts onboarding timing. |
| Status | jh_status | Product Holding | JH → HS | Open, closed, paid off. |
| Maturity date (CDs and loans) | jh_maturity_date | Product Holding | JH → HS | Drives renewal and refinance journeys. |
| Balance | jh_balance_band | Product Holding | JH → HS | Off by default. Band only, if compliance approves. |
| Rollups and life events | ||||
| Products held | jh_products_held | Contact | JH → HS | Multi-select rolled up from holdings. |
| Product count | jh_product_count | Contact | JH → HS | Relationship depth. |
| New account opened | Custom event: Account opened | Contact | JH → HS | Nightly or same day through events. |
| Loan paid off | Custom event: Loan paid off | Contact | JH → HS | Trigger for the next lending offer. |
| Address changed | Custom event: Address changed | Contact | JH → HS | Moving signal for mortgage and service outreach. |
| Digital banking enrolled | jh_digital_enrolled | Contact | JH → HS | From Banno, where available. |
| Last digital login | jh_last_digital_login | Contact | JH → HS | From Banno. Confirm availability in discovery. |
| HubSpot to core | ||||
| Marketing email opt-out | Customer preference field | Core | HS → JH | Only where the institution wants the core to hold it. Confirm field in discovery. |
| Referral from HubSpot | Officer task or referral record | Core | HS → JH | Opt-in scope. Many institutions keep referrals in HubSpot. |
How are authentication and API limits handled?
Jack Henry documents its core interfaces publicly; production access is set up per institution. Values Jack Henry does not publish are marked for confirmation.
| Topic | Jack Henry | HubSpot |
|---|---|---|
| Access model | Through the institution's Jack Henry relationship and Jack Henry's developer programs (Vendor Integration Program; Fintech Integration Network). Development uses Jack Henry's sandbox. | Self-serve in the client portal. Custom objects and custom events need an Enterprise hub. |
| Interfaces | jXchange: native SOAP with XML payloads, plus a REST translation layer. SymXchange: SOAP web service. Bulk data and event streaming listed on the developer site. | REST APIs: CRM objects, associations, custom events, imports. |
| Authentication | jXchange: OAuth 2.0 client credentials using a public/private key pair; tokens last 10 minutes; production may need a key pair per institution. SymXchange: credentials or a token carried in each request. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Real time vs batch | APIs answer per customer or account. Full holdings for every customer come from a nightly batch. Event streaming adds same-day signals where licensed. | Writes are immediate; batch endpoints handle nightly volume. |
| Environments | jXchange DMZ sandbox (no real personal data), then test or UAT, then the institution's production. SymXchange development against a test database. | HubSpot sandbox for build and parallel run. |
| Rate limits | Not published. Confirm with Jack Henry and the institution. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Account numbers, balances, transactions, tax IDs, dates of birth. The integration hashes the core key and drops restricted fields. | Sensitive data properties available 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
Core data is nonpublic personal information under GLBA. The institution's compliance team decides what HubSpot may hold and how privacy notices apply. CC builds to that decision and documents it in the SOW.
Credentials are issued for each institution and may need their own key pair. Make access and vendor due diligence client-owned dependencies, with dates.
On Symitar the member account number identifies the member. Store a one-way hash as the HubSpot key, never the number itself.
Core processing runs overnight, so most data is a day old. Journeys that need same-day action use events or API calls, and the SOW says which ones.
Each institution has its own product codes. Map them to HubSpot product types in a table the institution owns and updates.
Moving modules to Jack Henry Platform or changing cores changes the interfaces. Keep the core sync module separate so the HubSpot model does not change.
Opportunities in HubSpot
Every new checking account, loan or card starts a timed onboarding journey in HubSpot: welcome, digital banking enrollment, direct deposit, next product.
Members with a checking account and no credit card, or an auto loan and no savings, enter targeted lists automatically each night.
CD maturities, loan payoffs and address changes become prompts for renewal, refinance and mortgage conversations.
Banno enrollment status shows which members still need help going digital, and HubSpot follows up until they enroll.
Each contact is owned by the right officer and branch, so tasks, sequences and reports follow the real relationship.
Product depth, tenure and journey results by branch and segment in HubSpot dashboards, without exporting core reports.
Start with onboarding, then grow the relationship.
Every phase uses the same HubSpot data model, so value arrives in steps. Each step adds a journey, not a new data source.
- Nightly batch of customers or members and product flags, matched to HubSpot contacts.
- Onboarding journeys for every new account, loan and card.
- Cross-sell and life-event journeys from holdings, maturities and payoffs.
- Same-day events and Banno engagement, once the nightly model is stable.
Which HubSpot properties does the integration create?
All custom properties use the jh_ prefix in a Jack Henry property group. Nothing in this schema holds an account number, balance, tax ID or date of birth.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| jh_core_key | Core Key (hashed) | Contact | Single-line text | One-way hash of customer ID or member record; unique |
| jh_customer_since | Customer Since | Contact | Date picker | Relationship start date |
| jh_age_band | Age Band | Contact | Dropdown | Computed in the integration layer |
| jh_branch | Branch | Contact | Dropdown | Primary branch |
| jh_products_held | Products Held | Contact | Multiple checkboxes | Rollup of open product types |
| jh_product_count | Product Count | Contact | Number | Count of open products |
| jh_digital_enrolled | Digital Banking Enrolled | Contact | Single checkbox | From Banno, where available |
| jh_product_type | Product Type | Product Holding | Dropdown | Mapped from institution product codes |
| jh_product_code | Product Code | Product Holding | Single-line text | Institution's product code |
| jh_open_date | Open Date | Product Holding | Date picker | From the core account record |
| jh_status | Status | Product Holding | Dropdown | Open, closed, paid off |
| jh_maturity_date | Maturity Date | Product Holding | Date picker | CDs and term loans |
Interactive scope builder
Choose the data and journeys for this engagement and the direction each field 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 public documentation. Each item marked for confirmation is verified with Jack Henry and the institution during the access phase.
- jXchange · getting started
- jXchange · development using SOAP (protocols, OAuth, environments)
- SymXchange API documentation
- Operational Data Integration overview
- Enterprise Event System
- Vendor Integration Program case study
- Jack Henry technology guide for banks (cores, jXchange, Banno Digital Toolkit)
- Jack Henry Platform overview
Jack Henry HubSpot integration FAQ
Does Jack Henry integrate with HubSpot?
Yes, but access is open with conditions: Jack Henry publishes jXchange and SymXchange documentation with a sandbox, but production access is issued per institution through Jack Henry's developer programs once that institution's agreement is in place. Campaign Creators builds a custom integration layer on those core APIs plus the nightly Operational Data Integration batch.
What data syncs between Jack Henry and HubSpot?
Customers and members sync into HubSpot contacts and companies, and their product holdings (checking, savings, loans, cards, CDs) sync into a Product Holding custom object with open date, status and maturity date, plus custom events such as account opened or loan paid off. HubSpot writes back only limited, opt-in items such as marketing preferences, never account numbers or balances.
Which system owns which data?
The Jack Henry core stays the system of record for account numbers, balances, transactions and identity verification, and HubSpot never edits an account or core record. HubSpot owns the relationship and marketing view: product flags, dates, tenure and journey activity, with account numbers, balances, tax IDs and dates of birth excluded by default.
What does setting up the Jack Henry HubSpot integration involve?
Seven phases, each closed by an institution sign-off: a core and journey inventory, requesting jXchange or SymXchange access and completing vendor due diligence, a compliance and data-minimization review of the field list, the HubSpot data model with a Product Holdings custom object, the build of the nightly batch and same-day event path, a backfill and reconciliation of every customer or member, and a two-week parallel run before onboarding and cross-sell journeys go live.
How long does the integration take and what does it cost?
Timeline and cost depend on which core (SilverLake, CIF 20/20, Core Director or Symitar) and interfaces the institution has licensed, the journeys marketing and service want to run, and how much compliance review the field list requires. 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)