Migrate from HighQ to Twenty CRM

HighQ Sites are workspaces that contain projects, files, and iSheets for a firm or client matter. We map the Site name and metadata (domain, industry, employee count if populated) to Twenty's Company object. Site-level files and sub-objects migrate separately under the same Company linkage.

HighQ Projects track matters — deal reviews, M&A transactions, real estate closings. We map Project name to Opportunity name, project status to pipeline stage, project budget or deal value to Opportunity amount, and target close date to close date. HighQ has no native opportunity object; Projects serve this function.

HighQ Tasks map 1:1 to Twenty Tasks. We preserve the original task name, description, due date, assigned user (resolved by email match to Twenty Members), and completion status. Task creation timestamps migrate as custom datetime fields since Twenty's CreatedDate reflects migration time.

HighQ stores person records on Sites and within Projects as matter contacts. We map first name, last name, email, phone, job title, company association, and address fields to Twenty's People object. Unassigned contacts (no Site linkage) land under a default Company.

HighQ iSheets are configurable relational tables used to track deal terms, clause checklists, counterparty data, and regulatory filings. Each iSheet becomes a named Custom Object in Twenty. Column type mapping: text → TEXT, number → NUMBER, date → DATE, select → SELECT, multi-select → MULTI-SELECT, relation → relation field.

HighQ iSheet columns of type 'relation' create many-to-many links between iSheets. When an iSheet relation maps to a many-to-many cardinality, we create a junction Custom Object in Twenty to preserve the link. One-to-many relations map as a standard relation field on the child Custom Object.

HighQ files stored in Sites and Projects re-upload to Twenty as record attachments. We download files from HighQ (respecting size limits) and push them to Twenty via the API. Files without a parent record association are attached to the parent Site/Company record.

HighQ records matter-level activity including file uploads, task completions, comment threads, and status changes. Twenty has no equivalent collaboration feed; we surface activity as Task records linked to the parent Project or Person. Rich comment threads migrate as Notes attached to the relevant record.

HighQ Workflows, task-metadata iSheets, and rule sets are configuration-layer automation. We export workflow definitions as a structured JSON reference document for the Twenty admin. The automation logic must be rebuilt in Twenty's workflow builder — we do not migrate workflow execution state.

HighQ's site-level role assignments (Admin, Contributor, Viewer per Site) and Thomson Reuters identity permissions have no direct Twenty equivalent. We map HighQ site members to Twenty workspace Members by email resolution during migration. Post-migration, the client's admin must rebuild permission levels in Settings → Members in Twenty — mapping each HighQ role to the appropriate Twenty workspace role (Admin, Standard, or Guest) based on the permission-matrix guide we deliver.

HighQ users assigned to Sites and Projects are resolved by email match against Twenty workspace Members. We flag any HighQ users without a corresponding Twenty invite before migration. Unmatched owners are assigned to a fallback Member specified by the client.