Migrate from Highrise to HubSpot

Highrise People records map one‑to‑one to HubSpot Contacts, translating standard fields such as first name, last name, email address, phone number, address, and job title without transformation. The original Highrise Person ID is written into a custom property on the HubSpot Contact so the migration team can trace each record back to its source, run de‑duplication checks, and handle delta runs by comparing the stored identifier against later Highrise exports.

Highrise account‑specific custom fields on People are translated into HubSpot custom contact properties. Each field’s data type—text, number, date, or pick‑list—determines the equivalent HubSpot property type, ensuring correct validation and UI rendering. For pick‑list fields, HubSpot property options are created in advance of the migration so that the incoming values map cleanly to the defined choices without manual post‑migration cleanup.

Highrise tags are a flat label set applied to People. FlitStack migrates them as a HubSpot contact property storing all tags as a semicolon-delimited string, and optionally creates HubSpot static lists per tag name for list-based segmentation and workflow triggers.

Highrise Company records map directly to HubSpot Companies, preserving the standard fields name, domain, phone, and address. Parent‑child company hierarchies defined in Highrise are transferred to HubSpot’s Parent Company relationship, so reporting by corporate structure remains intact. The original Highrise Company ID is saved in a custom property for reference and reconciliation after the load.

Highrise custom fields attached to Companies become HubSpot custom company properties, mirroring the field types used in Highrise. Text fields translate to HubSpot single‑line text, numbers to number properties, dates to date pickers, and pick‑lists to option sets. Before the migration runs, each custom property is provisioned in HubSpot with the correct type and label so the incoming data lands without conversion errors.

Highrise Deals map straight to HubSpot Deals, preserving the deal name, amount, currency, expected close date, status, and owner. Each Highrise deal category becomes a distinct HubSpot Pipeline; the flat stage values from Highrise are converted into Stage entries within that Pipeline. Probability and forecast settings are set per Stage, and the original Highrise Deal ID is stored for audit and delta reconciliation.

Highrise deal‑level custom fields are recreated as HubSpot deal custom properties, with data types matched to the original field definitions. Fields such as deal priority or custom probability overrides are exposed as separate HubSpot properties because HubSpot stores default probability at the Pipeline stage level. This approach keeps the migrated data transparent and allows sales managers to filter and report on custom attributes directly in the HubSpot Deal record.

Highrise Cases have no native HubSpot equivalent. Teams choose between HubSpot Tickets (requires a Service Hub subscription) or a custom object named 'Case' with status, priority, and category fields. FlitStack surfaces this choice before migration and creates the target object schema.

Highrise Tasks translate to HubSpot Tasks, carrying the task subject, body text, due date, assigned owner, and completion flag. Open tasks remain open in HubSpot with their original due dates; completed tasks retain the completion timestamp recorded in Highrise, preserving the full activity timeline for audit and follow‑up reporting.

Highrise Notes, Emails, and Comments are imported as HubSpot Engagement records attached to the corresponding Contact, Company, or Deal. Each engagement preserves the original timestamp, owning user, and any inline content, so the activity feed in HubSpot shows a continuous history from the original Highrise entry and supports future reporting on past interactions.

Highrise Party links connect a Person to a Company. When a Highrise Person has one Company, it maps to HubSpot's primary company_id on the Contact record. When multiple Companies are linked, the primary becomes company_id and the rest are stored as additional HubSpot Company Associations.

Highrise deal-contact links map to HubSpot Deal Contact Roles. Highrise contact roles on a deal (if any are defined in the account) translate to HubSpot Deal Contact Role entries so the primary contact on a deal is identified in HubSpot.