Migrate from Clarra to Freshsales

Clarra Client first_name, last_name, email, phone, and address map directly to Freshsales Contact fields. The client_id is stored as Source_System_ID__c for traceability. If the client is an organization rather than an individual, a parallel Account record is created. Address fields map to Freshsales's compound address, preserving street, city, state, zip, and country. Phone numbers are stored in the Phone field, with secondary numbers captured in a custom Mobile__c field.

When a Clarra Client record lacks a person name and is identified by company_name instead, it maps to Freshsales Account. The account_name becomes Account.Name; company_domain maps to Account.Website; industry maps to Account.Industry via value mapping. Organization address and main phone number map to the Freshsales Account address and phone fields, while any custom fields such as industry classification are transferred via custom Account fields created during setup.

Clarra Matter maps to Freshsales Deal. The matter_identifier (e.g., CLM-2024-0042) becomes Deal.Name. matter_stage maps to Freshsales Deal Stage via value mapping: Open → Open, On Hold → Negotiation, Closed Won → Closed Won, Closed Lost → Closed Lost. The original matter_created_date migrates to a custom datetime field.

Clarra Contract is not a native Freshsales object type. We merge contract fields into the parent Freshsales Deal: contract_number maps to Contract_Number__c, contract_type maps to Contract_Type__c (NDA/MSA/SOW/Custom), contract_value maps to Contract_Value__c, and billing_arrangement maps to Billing_Arrangement__c. Contract status, effective date, and expiration date are stored in custom fields Contract_Status__c, Contract_Effective_Date__c, and Contract_Expiration_Date__c, respectively, ensuring full contract lifecycle visibility within the Deal record.

Clarra calendar events map to Freshsales Sales Activities. The event title becomes the Sales Activity subject; event_start_date and event_end_date map to start_time and end_time; event_type (Meeting / Call / Deposition) maps to the activity type pick-list; attendee_list is stored as a custom text field.

Clarra tasks migrate to Freshsales Tasks. task_title becomes Task.Subject; task_description becomes Task.Description; task_due_date maps to Task.Due Date; task_status (Open / Completed) maps to a custom Task_Status__c pick-list on the Task object. The assigned_to field is resolved to the Task.Owner by matching the user's email, and any task priority or custom flags are transferred to Freshsales custom fields defined during schema setup.

Clarra attorney records (attorney_name, attorney_email) are matched to Freshsales users by email. Unmatched attorneys are flagged in the pre-migration audit — your Freshsales admin either invites them as users or assigns their records to a fallback user. Each attorney's role and department are optionally mapped to Freshsales user fields such as Role and Department, and inactive attorney records are set to a generic inactive user until activation.

The Clarra relationship between a Client and their Matter maps to the Freshsales Account-Deal association. The matter's primary_client_id links to the Freshsales Account so the deal appears on the correct account record. If a client has multiple matters, each matter’s deal is linked to the same Account, and any secondary client associations are preserved via a custom Client_Association__c field on the Deal.

Clarra file attachments on contracts are re-uploaded to Freshsales Files associated with the target Deal. File name, size, and original upload date are preserved. Files over Freshsales's 25MB per-file limit are flagged for manual handling. Each file is linked to the Deal via Freshsales's file association, and file metadata such as MIME type and uploader identity are stored in custom fields for auditability.

All Clarra custom fields require Freshsales custom fields created before migration. billing_arrangement becomes Billing_Arrangement__c (pick-list); case_type becomes Case_Type__c (pick-list); opposing_counsel becomes Opposing_Counsel__c (text); matter_identifier becomes Matter_Identifier__c (text). We deliver a custom field creation plan as part of the pre-migration schema setup.