Migrate from Clarra to Salesforce Sales Cloud

Clarra has no native Salesforce-style API authentication that FlitStack can invoke without admin credentials

Clarra's REST API requires admin-level credentials or an API token generated from the platform settings. If those credentials are unavailable or the API token has been revoked, data export relies on the CSV/XLSX bulk export from the Clarra UI. Bulk export files may not include all custom field data or relationship IDs needed for precise Salesforce mapping. We require valid admin API access or a full CSV export that covers all custom fields before scoping a migration — the approach and timeline adjust accordingly if only UI export is available.

Legal matter data has no native Salesforce object — custom schema must be built before records can land

Salesforce's standard Case object is a support ticket construct with fields like Subject, Origin, and Status designed for customer service workflows. Clarra matters track practice area, billing arrangement, assigned attorney, and related parties — none of which exist on the standard Case object. We create a Matter__c custom object with all mapped fields before the migration runs. This requires the Salesforce admin to deploy the custom object metadata (via Setup > Object Manager or a deployment tool) in a pre-migration step. If your org has validation rules or required fields on custom objects, those must be reviewed and potentially relaxed before the bulk load, or records will be rejected at insert time.

Attorney and client contact roles require a junction model that Clarra does not enforce

Clarra allows any number of contacts to be associated with a matter with role labels, and a single contact can have multiple roles simultaneously. Salesforce Contact has no native role attribute — Contact_Role__c is a custom pick-list we add. For multi-role scenarios (an attorney who is also a client contact on the same matter), we create two junction records in Matter_Party__c with different Role__c values. If your team has contacts with more than three simultaneous matter roles, the junction table may need a Role_Display_Order__c field to preserve the sequence Clarra recorded.

Document re-upload is a file-by-file operation with Salesforce file size and format constraints

Clarra stores documents within matter records with version metadata. Salesforce Files use ContentVersion with a 25MB per-file default limit and support for common formats (PDF, DOCX, XLSX, images). Documents exceeding the size limit must be split or stored as external links. Any Clarra-specific file metadata (version author, version timestamp, locked/unlocked status) that does not map to a Salesforce ContentVersion field is preserved in a custom Content_Version_Metadata__c long-text field on the ContentVersion record.

Billing arrangements and trust accounting data have no Salesforce standard field

Clarra tracks billing_method (hourly, fixed, contingency, pro bono) and may include trust account balances or billing notes per matter. Salesforce has no standard field for these legal-specific billing attributes. We migrate billing_method to Billing_Method__c on Matter__c as a custom pick-list. Trust account balances and billing notes migrate as custom currency and text fields respectively (Trust_Balance__c, Billing_Notes__c). If your firm uses a dedicated legal billing or ERP system integrated with Clarra, those integrations must be re-established with Salesforce separately — the billing data itself migrates, but the billing automation logic does not.