Migrate from Clarra to Twenty CRM

Clarra Clients map directly to Twenty People in a 1:1 relationship. Primary email, phone, address, and name fields transfer without transformation. When a Clarra Client has multiple associated contacts, each contact becomes a separate Twenty People record, and all are linked to the same Company record via companyId to preserve the original relationship structure.

Clarra Matters function as the case or project container in the system, and they map directly to Twenty Companies. Standard fields including industry, employee count, address, and annual revenue transfer as native Company fields. When Clarra Matters have parent-child hierarchies, those relationships convert via Twenty's Company relation field, preserving the organizational structure across the migration.

Clarra Contracts are transformed into Twenty Opportunities. The Contract amount field maps directly to Opportunity.amount, while contract status values (Draft, Active, Under Review, Expired) are mapped via explicit value mapping to Twenty Opportunity stage values. Contract end date becomes the closeDate in Twenty, with a custom status field preserving the original Clarra status for reference after migration.

Clarra Calendar Events are evaluated for their time characteristics. Events specified with a due date but lacking explicit start/end times convert to Twenty Tasks with Type set to Reminder. Events containing both start and end times map to Twenty CalendarEvent records. Throughout this process, all original creation timestamps and assignee relationships are captured as custom datetime fields to maintain complete historical context within Twenty.

Documents and files attached to Clarra Matters and Contracts are downloaded from Clarra and re-uploaded to Twenty as native file attachments on the appropriate record type. People, Company, and Opportunity records each accept file attachments. Since Twenty lacks native version history, Clarra version information is preserved as a custom text field labeled DocumentHistory__c, storing version metadata including version number, uploader, and date in JSON format for audit purposes.

Clarra custom objects map 1:1 to Twenty custom objects. The Twenty custom object must be created in Settings → Data Model before migration. Any N:1 relationships to standard objects require a 'relation' field pointing to the existing Company or People record.

Clarra workflow rules—including deadline alerts, assignment routing, email triggers, and milestone notifications—reside as platform configuration and are not exposed through Clarra's public API, making automated export impossible. To address this, FlitStack documents every active workflow in detail, capturing its trigger conditions, action steps, and filter logic. Your Twenty administrator then uses this documentation to manually rebuild equivalent automations using Twenty's Settings → Workflows interface.

Clarra user accounts are matched to Twenty WorkspaceMembers using email address as the primary key. During the matching process, any Clarra users without a corresponding email in Twenty are flagged in a User Resolution Report for manual handling. Team-level access controls, role hierarchies, and permission structures defined in Clarra cannot be mapped automatically and must be reconfigured manually through Twenty's Settings → Members interface after migration completes.

Clarra tags and labels transfer directly to Twenty's built-in tag field, which is available on People, Company, and Opportunity record types. Since Clarra tags are free-form text entries with no enforced vocabulary or predefined list, they transfer verbatim without any transformation or deduplication. Your team should review the consolidated tag list after migration to identify duplicates or inconsistencies that may have accumulated in Clarra over time.

Clarra's billing rates, billing codes, cost-center assignments, and other financial metadata attached to Contracts lack native equivalents in Twenty's Opportunity object. These fields are migrated as custom fields on the Opportunity record, with names like BillingRate__c and CostCenter__c created in Twenty's Settings → Data Model. For Contracts containing multi-currency amounts, the original currency code is preserved in a companion custom select field (ContractCurrency__c) alongside the numeric amount value.