Migrate from Assembly Neos to Twenty CRM

Assembly Neos contact records (attorneys, paralegals, opposing counsel, clients) map 1:1 to Twenty CRM People records. Email address is the unique identifier in Twenty — used for deduplication and user resolution during migration. Contacts without an email address receive a placeholder email and are flagged for manual review.

Assembly Neos client firm records map to Twenty CRM Companies. Firm name becomes Company.displayName. Domain maps to Company.website. For contacts with no primary client firm, a default 'Individual' company record is created in Twenty and the contact's companyId points there.

Assembly Neos matters map to Twenty CRM Opportunities — the closest equivalent object in Twenty's schema. Matter number is preserved as a custom Opportunity field (Matter_Number__c). Case status (Open, Pending, Closed) maps to a custom StageName pick-list that must be pre-created in Twenty Settings → Data Model before the import runs.

Assembly Neos activities with type 'Call' or 'Email' migrate as Twenty CRM Tasks with Task.type set accordingly. Meeting activities migrate as Twenty Events with original start/end timestamps preserved. The activity description maps to Task.body or Event.body. Activity owner resolves by email to a Twenty workspaceMember.

Free-form notes logged against a matter in Assembly Neos migrate as Twenty CRM Notes attached to the corresponding Opportunity record. The note title becomes Note.title; the body maps to Note.body. Rich-text formatting in Assembly notes is flattened to plain text during migration.

Assembly Neos billable time records (hours, rate, amount, work date) have no native equivalent in Twenty CRM. FlitStack creates a custom BillableTime object in Twenty with fields for hours (number), rate (currency), total amount (currency), work date (date), and description (text). The custom object is linked to the Opportunity via a relation field.

Assembly Neos document attachments are re-uploaded to Twenty CRM's Files feature. File name is preserved as a custom text field on the file (or as a Note attachment to the parent Opportunity). Large documents that exceed Twenty's file size limits are flagged for chunked upload. Inline images in Assembly notes are downloaded and rehosted.

Assembly Neos custom properties on contacts (e.g., bar_number, practice_areas) require pre-created custom fields in Twenty CRM under Settings → Data Model. All custom fields must exist before CSV import runs — the import creates records, not fields. Contact-type pick-lists in Assembly (Attorney, Paralegal, Client) map to a custom role pick-list field in Twenty.

Assembly Neos custom properties on matters (e.g., court_name, opposing_counsel, insurance_carrier) become custom fields on the Twenty CRM Opportunity. Pick-list values in Assembly map to Twenty pick-list options that must be pre-configured. Multi-select values in Assembly explode into multiple rows or a custom multi-select field type in Twenty.

Assembly Neos workflows, automations, and triggered actions have no direct equivalent in Twenty CRM's workflow engine. FlitStack exports your workflow definitions as a structured reference document for your Twenty admin to rebuild in Settings → Workflows. This is always a manual step — no automated translation is possible.

Assembly Neos document templates for letters, agreements, and court filings do not migrate to Twenty CRM. Twenty does not have a native document template engine. Templates must be exported as reference PDFs and rebuilt using your preferred document generation tool (e.g., DocuGen, Mailmerge) post-migration.

Assembly Neos integrations with Microsoft 365 (Outlook, Teams), DocuSign, QuickBooks, and RingCentral have no direct mapping in Twenty CRM. Each integration requires manual reconfiguration in Twenty's Settings → Integrations section. QuickBooks data (if used for billing) should remain the accounting system of record and not be migrated into Twenty's custom BillableTime object.