Migrate from Link app to Twenty CRM

Message threads flatten into individual Notes with no threaded conversation view

Link App organizes client communication as threaded conversations — each thread shows the back-and-forth in chronological order. Twenty CRM's Notes object is a flat list of entries attached to a record. When we migrate, each individual message becomes a separate Note with the sender role prepended to the body. The chronological thread view that Link App provides does not exist in Twenty CRM, so the visual grouping of a conversation is lost. We preserve message timestamps in a custom field, and the original thread structure is recoverable by sorting Notes by Message_Timestamp__c, but Twenty's native UI will not display them as threaded. Plan for rebuilding communication context in Twenty's activity sidebar or using Twenty's Workflow builder to surface related Notes.

Document attachments do not migrate to Twenty CRM — only file references survive

Link App provides a secure document vault with per-client file uploads. Twenty CRM has no native document management system — it stores file attachments at the record level via its storage service, but there is no equivalent vault concept. We store each document's original filename and URL as a custom text field Document_Reference__c on the corresponding Note. If your documents are hosted on Link App's servers, those links may become invalid after you close the Link App account. Before migration, download your document archive from Link App and re-upload to a storage service (S3, Google Drive, Dropbox) whose URLs you then record in Twenty. We can automate the URL remapping as part of the migration if you have a destination storage plan in place.

Link App has no Opportunity or deal object — pipeline tracking must be designed from scratch

Link App does not have a pipeline or deal management concept — it tracks client communication and document status. Twenty CRM's Opportunities object is where pipeline management lives. If you want to track client matters as Opportunities in Twenty, you must decide which fields from Link App map to Opportunity fields (name, amount, stage, close date) and which Link App concepts (matter status, billing tier) become custom fields. We surface this decision in the pre-migration schema plan. Matters that never had a deal value in Link App will need placeholder amounts or be set to zero — Twenty requires a numeric amount field. Stage mapping from Link App's matter status labels to Twenty Opportunity Stage values must be defined per case type.

Link App API access is export-only — the migration uses CSV extraction from the Link App admin panel

Link App's API is not publicly documented for third-party read access in the way Salesforce or HubSpot provide. The migration path uses the data export function available in Link App's admin panel, which generates CSV exports of client profiles, message threads, and appointments. The export must be requested by an account admin, and large thread histories may be split across multiple export files. We work with your Link App admin to extract all exportable data before mapping begins. If your Link App plan limits export frequency or record counts, coordinate with your account manager to unlock a full export before migration kickoff.

Twenty CRM has no native activity log at the free self-hosted tier

Link App tracks every client interaction — logins, document views, message opens — as a detailed activity log. Twenty CRM's activity tracking at the free self-hosted tier does not include a granular activity log comparable to Link App's. We aggregate interaction counts into a custom integer field Interaction_Count__c on the People record, but individual event records are not migrated. If detailed interaction history is business-critical, consider using Twenty's Workflow builder to log events via its webhook and API when you rebuild client-facing processes in Twenty. Alternatively, retain a read-only archive of the Link App export for historical audit purposes.