Equisoft/connect to HubSpot
Cloud CRM for insurance and wealth advisors that centralizes client, insurance and investment data through carrier and custodian data gateways.
Equisoft/connect data can move into HubSpot, landing mainly in Sales Hub. 1 of 8 mapped objects move directly (Contacts (individuals)); 4 items need manual work and 2 do not move. Plan roughly 3-6 weeks for a small move and 12-24 weeks for a large one.
Migration checklist for Equisoft/connect
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<5k contacts, one adviser group
Mainly waiting on vendor extraction.
Mid migration
5k-50k contacts, multiple users
Includes relationships and document migration.
Large migration
>50k contacts, enterprise or MGA
Needs integration redesign and a compliance review.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Equisoft/connect: what you need to get in, what lands in HubSpot, and what will not.
REST-style API with OAuth2 and a PHP SDK, including legacy kronos.* endpoints; not openly documented. Third-party sources disagree on whether an API exists.
OAuth2 client and access token with crm:* scopes, which is unconfirmed for customers; otherwise a vendor-delivered archive
Choose your route
How will you move the data?
No native connector was found.
- You need: OAuth2 client and access token with crm:* scopes, which is unconfirmed for customers; otherwise a vendor-delivered archive
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Vendor-run manual CSV or archive extraction, which can take weeks and may be charged
- Legacy and OAuth API endpoints for contacts, documents, tasks and events through the SDK, if access is granted
- Per-user document retrieval requested from Equisoft
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 12-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In Equisoft/connect
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts (individuals) | Contacts | yes | Identification, emails, phones, occupation and segmentation fields exist in the SDK models. |
| Organizations | Companies | partial | The SDK has organization identification models; household and relationship links need rebuilding. |
| Segmentation fields (class, distribution list, industry, hobby, source, segments 1-6) | Contacts | partial | Laylah maps these to tags; in HubSpot they need custom properties or lists. |
| Tasks and activities | Tasks | partial | Tasks and activities must be linked to a contact to be imported. |
| Emails, calls, meetings | Emails | manual | Product records and timestamps emails and calls; the export format is not documented. |
| Documents | Files | partial | The API downloads files as base64; the archive needs per-user document assignment. |
| Opportunities/pipeline | Deals | manual | Pipeline tracking exists in the product; the export schema is not confirmed. |
| Insurance and investment gateway data | Custom objects | no | Carrier-synced policy and portfolio data stays in specialist systems. |
What to expect
These are Equisoft integrations and would need rebuilding or stay in source systems.
May require manual export and reformatting.
The extraction is manual and can take weeks.
Records not assigned to the requesting user may be missed.
There is no confirmed native HubSpot mapping for these.
Unlinked activities are not imported.
Order the extraction early and agree the scope in writing.
Keep policy administration and portfolio data in specialist systems and link by client ID.
Ask Equisoft in writing whether API credentials are available to your tenant.
Retain the archive as a compliant record store.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Product, OAuth2 SDK scopes and the vendor-assisted archive export are supported by sources. There is no HubSpot-specific doc and no official Equisoft API docs were visited. Object mapping rests on SDK models and category knowledge. Sources conflict on whether an API exists.
Sources
Related migrations
Frequently asked questions
How do I migrate Equisoft/connect to HubSpot?
1. Ask Equisoft for the archive format, fee and timeline. 2. Confirm API/OAuth access with Equisoft and the scopes needed. 3. Assign each contact and document to its owning user. 4. List the segmentation fields to keep (class, segments 1-6, source).
What data can move from Equisoft/connect to HubSpot?
These objects move directly: Contacts (individuals). Check the mapping table for partial and manual items.
What does not move from Equisoft/connect to HubSpot?
Carrier and custodian gateway feeds and Equisoft/plan financial planning data and FNA. Plan to rebuild or retire these.
How long does a Equisoft/connect to HubSpot migration take?
Small (<5k contacts, one adviser group): 3-6 weeks. Mid (5k-50k contacts, multiple users): 6-12 weeks. Large (>50k contacts, enterprise or MGA): 12-24 weeks. These are planning estimates, not a quote.
What access do I need to export from Equisoft/connect?
OAuth2 client and access token with crm:* scopes, which is unconfirmed for customers; otherwise a vendor-delivered archive
What compliance issues apply when moving Equisoft/connect data?
Check: Financial, Insurance, Investor profile and suitability data and Possible health data in insurance files. Agree consent, retention and access rules before exporting.
Moving Equisoft/connect into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner