Highrise to HubSpot
Simple contact, deal and task CRM that stopped taking new signups in August 2018 and is frozen without new development.
Highrise data can move into HubSpot, landing mainly in Sales Hub. 2 of 9 mapped objects move directly (People and Companies); 4 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-10 weeks for a large one.
Migration checklist for Highrise
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 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 and deals
CSV or API extract with few custom fields.
Mid migration
5k-50k contacts, up to 10k deals
API scripting with activity history.
Large migration
>50k contacts with heavy notes and files
Attachment transfer and permissions redesign.
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 Highrise: what you need to get in, what lands in HubSpot, and what will not.
REST (XML over HTTP)
Account subdomain plus an API token or OAuth 2 authorization.
Not confirmed; docs mention a tightened limit on email-address contact searches only.
Choose your route
How will you move the data?
No native connector was found.
- You need: Account subdomain plus an API token or OAuth 2 authorization.
- 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.
- API endpoints for people, companies, deals, cases, notes, emails, tasks, tags, custom fields, users, groups and deletions
- vCard (.vcf) per person or company via the API
- CSV export of contacts, commonly cited by migration guides
Limits: Not confirmed; docs mention a tightened limit on email-address contact searches only.
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: 6-10 weeks, usually phased.
Talk to a partnerWhere each object lands
In Highrise
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People | Contacts | yes | Includes contact data, tags and custom fields (subject_datas). |
| Companies | Companies | yes | Custom fields and tags are exported; the person-to-company link needs checking. |
| Deals | Deals | partial | Deals carry a category id and linked parties; the category must be mapped to a HubSpot pipeline and stage by hand. |
| Notes | Notes | partial | Notes attach to a Party, Deal or Kase and can have attachments by URL. |
| Emails | Emails | partial | An emails endpoint exists; fidelity is untested. |
| Tasks | Tasks | partial | Tasks have categories, and due dates and owners need mapping. |
| Cases (Kase) | Tickets | manual | Cases are a grouping object. You can map them to Tickets or Custom objects, but that is a design decision. |
| Users and groups | Contacts | manual | Users can be read through the API. Owners must be recreated as HubSpot users and then mapped. |
| Attachments | Files | manual | Files are referenced by URL and must be downloaded and re-uploaded. |
What to expect
Highrise per-record visibility has no direct HubSpot equivalent and must be rebuilt as team or permission settings.
The API docs list no workflow or report endpoints, so these must be rebuilt.
Deal categories exist only as ids and must be mapped.
Visibility is set per record in Highrise.
The deal parties list and note subjects must be checked against exported associations.
Custom fields are exported as label and value pairs.
Run a full export soon and keep an offline archive.
Script paginated API extraction per object.
Export deal parties and note subject ids explicitly and reconcile counts.
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.
Official API docs (GitHub) support access and object coverage. Highrise is closed to new customers and its current operating status is unclear. Sources conflict on shutdown. No HubSpot-side docs for a Highrise connector were found, and export/rate-limit/governance details rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Highrise to HubSpot?
1. Confirm the account is still active and get an admin to generate an API token from My Info. 2. Inventory people, companies, deals, cases, tasks, notes, emails, tags and custom fields through the API. 3. Decide whether cases map to Tickets, Deals or Custom objects. 4. Map deal categories to HubSpot pipelines and stages.
What data can move from Highrise to HubSpot?
These objects move directly: People and Companies. Check the mapping table for partial and manual items.
What does not move from Highrise to HubSpot?
Visibility rules (Everyone, Owner, NamedGroup) and Automation and reporting. Plan to rebuild or retire these.
How long does a Highrise to HubSpot migration take?
Small (<5k contacts and deals): 1-2 weeks. Mid (5k-50k contacts, up to 10k deals): 3-6 weeks. Large (>50k contacts with heavy notes and files): 6-10 weeks. These are planning estimates, not a quote.
What access do I need to export from Highrise?
Account subdomain plus an API token or OAuth 2 authorization.
What compliance issues apply when moving Highrise data?
Check: Free-text notes may contain health or financial details; review them before import. Agree consent, retention and access rules before exporting.
Moving Highrise 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