Migrate from Highrise to Twenty CRM

Highrise People records map to Twenty People. Standard fields (name, email, phone, address, social links) transfer cleanly via CSV export. We parse the CSV output and transform field names to match Twenty's column headers. The email field serves as the dedupe key during import. Any People records linked to Companies carry the Company association through a lookup reference we resolve at migration time.

Highrise Companies (Party type) export alongside People via the parties.xml API endpoint. We separate Company records from People records and write them to the Twenty Companies import. Domain, address, industry, and employee count fields map to their Twenty equivalents. Companies must import before People so the Company-People association is satisfied at the moment of People insert.

Highrise Deals export as plain-text .txt files rather than CSV. We parse the TXT output to extract deal name, stage, value, responsible user, and linked contact or company. These parsed values transform into Twenty Opportunity records. The Highrise dealstage property maps to Twenty's Opportunity stage values. Any complex or unstructured deal data is flagged for manual review before migration.

Highrise Cases export as TXT only. We parse case title, status, linked contact, and timestamps. Cases with simple task-like structure migrate to Twenty Tasks with the case title as task name and the linked People record as the task's target. Teams using Cases for more complex support tracking may choose to create a custom Case object in Twenty before migration; we configure this during the schema design phase.

Highrise Tasks are standard API objects and export cleanly. Completed and open tasks with due dates, assignees, and related party references transfer to Twenty Tasks. Task status (open, completed, deferred) maps to Twenty task status values. Highrise Tasks linked to Deals migrate with the Opportunity association preserved.

Highrise stores all notes, emails, and comments as Recordings linked to People or Companies. Export is TXT only, stripping HTML formatting from emails. We capture the full text, metadata (date, author), and parent record reference. Notes migrate as Twenty Notes linked to the parent People or Companies record. Customers should expect email content to arrive as plain text in Twenty, with any embedded images or HTML formatting lost in the Highrise export.

Highrise custom fields on People, Companies, and Deals are exported via the custom_field_subjects API endpoint. We detect all custom field definitions and their data types, then recreate them in Twenty's Settings Data Model before any record import. Twenty requires fields to exist before the CSV import runs; we handle this schema-first approach by building the destination field definitions during the discovery phase and deploying them before data migration begins.

Highrise tags are flat labels applied to People, Companies, Deals, and Cases. We export all tag assignments and re-apply them as Twenty label values on the corresponding record. Many-to-many tag relationships are preserved by storing comma-separated tags in a Twenty text field or by creating multiple label assignments per record depending on Twenty's current label implementation at migration time.

Highrise Users who own records are extracted by name and email. We map them to Twenty Members by email match. Any Highrise User without a matching Twenty Member goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references on Opportunities and Tasks are required and cannot be nulled during migration.

Highrise deal stages (e.g., New, Contacted, Qualified, Won, Lost) are extracted during scoping and recreated as Opportunity stage values in Twenty. Stage order and probability percentages transfer where supported. We configure the pipeline stage set in Twenty before Deal/Opportunity migration begins.