Migrate from Knock CRM to Twenty CRM

Knock contacts map directly to Twenty People records. Email, phone, name, job title, and address fields carry over directly. The Knock contact owner resolves by email match to a Twenty Workspace Member. Knock contacts without a primary company land as standalone People records.

Knock companies (property listings) map to Twenty Companies. Property name, address, domain/website, industry classification, and unit count fields translate to their Twenty equivalents. Multi-property companies in Knock become multiple Company records in Twenty linked by a parent-company custom field. This ensures that each individual property location retains its own company identity in Twenty while maintaining the parent-child relationship through the custom field reference.

Knock deals representing lease opportunities map to Twenty Opportunities. Deal name, amount (rent or fee), stage, close date (lease start), and owner transfer directly. Knock's deal-stage values map to Twenty Opportunity Stage pick-list values per configured pipeline. Stage-enter timestamps from Knock are preserved as custom datetime fields on the Twenty Opportunity, maintaining your stage-transition history and allowing you to analyze pipeline velocity through the original timestamps.

Each Knock deal pipeline stage maps value-by-value to a Twenty Opportunity Stage within the same Opportunity. Knock stage-enter timestamps are preserved as custom datetime fields on the Opportunity for stage-history continuity. We surface stage-probability assumptions for your Twenty admin to configure.

Knock tasks map to Twenty Tasks with full assignment, due date, completion status, and parent-record links preserved. Tasks linked to Contacts, Companies, or Deals carry their Twenty equivalents as relation fields. Open versus completed status maps directly. Task priority levels migrate as a custom select field when present in Knock. Recurring task patterns are flagged for manual recreation in Twenty's task system.

Knock notes migrate as Twenty Notes attached to the relevant People, Company, or Opportunity record. Original create timestamps and author information are preserved. Rich-text formatting in Knock notes converts to Twenty's note body format. Any embedded file references or links within notes are flagged as requiring post-migration verification.

Knock custom properties on contacts (e.g., application_status, leasing_agent, preferred_move_in_date) require pre-created custom fields in Twenty via Settings → Data Model before import. FlitStack generates a custom field creation plan based on your Knock property inventory. Text, date, select, and number field types map directly.

Knock deal custom fields (unit_number, lease_term_months, security_deposit, application_received_date) map to Twenty custom fields on Opportunities. These fields must exist in Twenty before the migration runs. We deliver a field creation checklist ordered by object so your admin pre-stages the schema.

Knock owner IDs resolve by email match to Twenty Workspace Members. Before migration, your Twenty workspace must have all active team members invited and accepted. Unmatched owners receive a fallback assignment or are flagged — no record lands without a valid Twenty owner.

Knock's contact-to-company and contact-to-deal associations map to Twenty relation fields (companyId on People, opportunityId on Opportunities). When a contact has multiple associated companies, the primary company maps as companyId and the rest surface as a custom relation note or are logged for manual re-linkage.

Knock file attachments (lease documents, application PDFs, property images) are exported to local storage and re-uploaded to Twenty's file attachment field or external storage linked from the record. We flag any files exceeding Twenty's storage limits for manual handling. Files are organized by record type and linked to their corresponding People, Company, or Opportunity records to maintain the original attachment context.

Knock leasing sequences, task triggers, and attribution automations do not migrate. We export your Knock workflow definitions as a JSON/CSV rebuild reference so your Twenty admin can recreate logic in Twenty's workflow builder. Scheduling triggers and sequence steps require manual reconfiguration.