Migrate from Knack to Twenty CRM

Knack Tables holding person records (contacts, employees, leads) map to Twenty's People object. We inspect field types per table and map text fields to name components, email fields to emailAddress, phone fields to phoneNumber, and address fields to the appropriate Twenty address subfields. Any Table without a person-type primary key is evaluated against other standard objects before assignment.

Knack Tables holding organization records (companies, accounts, clients) map to Twenty's Company object. The Table's name field maps to Twenty's name field, domain fields map to websiteUrl, and industry or type fields map to industry where a picklist match exists or to a custom field where it does not. Company records are imported before People records to satisfy the Twenty workspaceKey relationship.

Knack Tables tracking sales opportunities map to Twenty's Opportunity object. We map amount fields, close date fields, and stage fields to their Twenty equivalents. Stage values are captured as OpportunityStage on import and are visible in Twenty's pipeline view. If the source Table has a probability field, we map it to a custom field probability__c since Twenty's standard Opportunity does not include a native probability field.

Knack Tables storing tasks, action items, or notes map to Twenty Task or Note objects depending on whether the record represents a tracked activity (with due date, status, assignee) or a static annotation. We inspect field names (due_date, status, assigned_to vs body, comment, note) to determine the correct target. Completed status maps to Task status completed.

Any Knack Table that does not map to a Twenty standard object (Company, People, Opportunity, Task, Note) becomes a Twenty Custom Object. We pre-create the Custom Object in Twenty's Data Model with the same API-name-friendly slug, add all custom fields before import, and configure field types (text, number, date, select, multi-select, relation) to match the Knack field inventory. Custom Object naming and field creation happens in a staging pass before any records are loaded.

Knack Connection fields link one Table to another (one-to-many or many-to-many). These are Knack-specific foreign keys stored as record IDs in the Knack API response. We extract the source record ID and target record ID from each Connection field, then map them to Twenty Relation fields on the appropriate Custom Object. Many-to-many Connections require a junction object in Twenty, which we create as a custom object during schema setup.

Knack file fields store documents, images, and PDFs accessible via direct URLs after authentication. We download each file from Knack's URL, then re-upload to Twenty as an attached file on the parent record (People, Company, Opportunity, or Custom Object). File naming conventions and the parent-child relationship are preserved during the transfer.

Knack Views are saved filtered or sorted subsets of a Table — a Knack UI concept with no direct equivalent in Twenty. We export a complete inventory of every View: its source Table, filter conditions, sort order, and visible columns. This inventory is delivered as a structured reference document so the customer's admin can recreate equivalent views in Twenty's view builder after migration.

Knack roles control which Pages and Records users can access. We export role names, permission levels, and the associated user assignments. Twenty uses workspace Members with object-level and field-level permissions configured in Settings. We map Knack role names to Twenty permission sets and deliver a role-mapping table for the admin to apply in Twenty Settings post-migration.

Knack Record History tracks field-value changes on Pro (1 month) and Corporate (2 months) plans. We export available history records as a structured audit log and attach them as Note records on the relevant parent record in Twenty, with a custom field audit_timestamp__c to preserve the original modification date. Historical audit data does not become native Twenty activity; it is delivered as reference notes.