Migrate from Composity CRM to Twenty CRM

Composity Accounts map directly to Twenty Companies. Composity's Account name, address fields (street, city, country, postal code), industry, status (active/inactive), and domain URL map to Twenty's standard Company fields. Composity's custom Account fields from the Custom Data module map to Twenty custom fields on the Company object. Company is created first so that the People-Company relation is satisfied at Contact import time. Composity's Lite tier limit (1,000 accounts) is checked during discovery to flag whether the migration scope is constrained by plan ceiling before any extraction begins.

Composity Contacts map to Twenty People. Composity's Contact name, email, phone, job title, and role map to Twenty's standard Person fields. The Account-Contact relationship resolves to a Company-People link in Twenty using domain or name matching. Composity's custom Contact fields (defined in the Custom Data module) map to Twenty custom fields on People. Activity associations on Contact records (calls, emails, meetings, notes) link to the migrated Person via the People-Activity relation in Twenty.

Composity Leads with status 'new' or 'contacted' and no associated opportunity map to Twenty People records without a Company link (indicating an unqualified prospect). Composity Leads that have been progressed and have an associated opportunity value map to Twenty People linked to an Opportunity, preserving the Composity lead source, qualification status, and score as custom fields on both the Person and the Opportunity. We define the split rule during scoping based on the customer's Composity lead stage matrix.

Composity Opportunities map to Twenty Opportunities. Deal name, value (amount), stage, expected close date, and probability map to Twenty's standard Opportunity fields. Composity's custom pipeline stage names require explicit mapping to Twenty's Opportunity stage configuration, which we design during schema scoping. Closed-won and closed-lost reasons from Composity custom fields become Twenty custom fields on the Opportunity. Owner assignments resolve via the User mapping (by email) and are preserved as Opportunity owner references.

Composity's user-defined pipeline stages (name, order, win/loss flags) are exported from the CRM settings module and recreated in Twenty's Opportunity stage configuration. Each stage's probability percentage maps to Twenty's stage probability. Composity's custom stage names that do not map to Twenty defaults are added as new stage values. The stage order is preserved so that pipeline visualization in Twenty's kanban view matches the original Composity pipeline.

Twenty does not include a native Invoice object in its standard CRM schema. We map Composity invoices (line items, tax codes, payment status, totals, and due dates) to a Twenty custom object named Invoice. Composity's partially paid invoices require balance carry-forward logic; we preserve the paid amount, outstanding balance, and payment history as custom fields on the Invoice record. Invoice PDFs are exported from Composity as individual files and reattached to the corresponding Invoice record in Twenty using filename matching.

Composity Products (name, SKU, price, description, and custom pricing rules) map to a Twenty custom object named Product. SKU maps to a text field, price to a currency field, and description to a text field. Custom pricing rules defined in Composity are preserved as JSON or multi-select fields depending on complexity. Product associations to quotes and invoices are preserved via lookup fields pointing to the Invoice custom object.

Composity Projects (available in Growth and above) map to a Twenty custom object named Project. Project name, status (active/completed/on-hold), start and end dates, assigned resources (user references), and custom project fields migrate to the custom object. Composity project milestone definitions migrate as a related custom object or as JSON within a milestones field, depending on milestone count and complexity. Projects without an assigned user are flagged for admin review during cutover.

Composity's Production module records (BOM references, production order status, quantities, and bill of materials) have no native equivalent in Twenty's standard schema. We map them to a Twenty custom object named Production Order, preserving BOM line items as a related sub-object or as structured JSON in a custom field. Composity's production order statuses (planned, in-progress, completed) map to a select field on the custom object. This mapping requires explicit schema design during scoping because BOM relationships must be resolved before production order records are imported.

Composity Inventory records (SKU, quantity, warehouse location, reorder level, and quantity discrepancies) map to a Twenty custom object named Inventory Item. We flag any inventory records with negative stock or quantity discrepancies during extraction so that the customer can review before migration. Warehouse location maps to a text or select field depending on the number of unique locations. Inventory quantity adjustments and history do not migrate as separate activity records but are preserved as a snapshot at migration time.

Composity Document Storage exports files one at a time with no bulk download option. We build a file inventory during discovery by requesting exports through Composity's interface, download each file, and reattach it to the corresponding migrated record in Twenty using filename or metadata matching. Files without a resolvable parent record are flagged in a separate queue for manual assignment. File upload dates and metadata (size, type) are preserved as custom fields on the Twenty attachment or the parent record.

Composity Activity tracking (calls, emails, meetings, notes) against Contacts and Accounts maps to Twenty Tasks and Notes. Composity's activity type field determines the Task subtype (call, email, meeting). Activity date, description, and duration migrate to Twenty's Task fields. The linked Contact or Account resolves to a Twenty Person or Company via the migration's lookup table. Activities without a resolvable parent record are held in a reconciliation queue for admin review.