Migrate from Rocket Matter to Salesforce Sales Cloud

Rocket Matter clients map directly to Salesforce Contacts. Salesforce requires an AccountId on Contacts — firms with individual clients (solo practitioners) get attached to a default 'Individual Client' Account record. Multi-contact households use Account Contact Relationships in Salesforce to maintain household groupings while preserving individual contact records with full contact details and communication history.

Corporate clients with multiple contacts in Rocket Matter may represent a company. FlitStack maps the primary client contact's company name to an Account record, then links additional client records as Contacts under that Account using Account Contact Relations for N:N scenarios.

Rocket Matter matters have no direct Salesforce equivalent. We create a custom Matter__c object in Salesforce with fields for matter number, practice area, responsible attorney, status, and billing method. This preserves Rocket Matter's case-centric structure in Salesforce's schema while enabling custom reporting, automation, and page layouts tailored to each practice area and matter type.

Billable matters representing revenue-generating cases (contingency matters, fixed-fee engagements, transaction matters) map to Salesforce Opportunities with Amount from the fee arrangement, CloseDate from the matter close date, and StageName mapped from matter status. RecordTypeId varies by matter type, enabling distinct sales processes, validation rules, and reporting views for litigation versus transactional matters.

Rocket Matter time entries (date, duration, attorney, matter, description, billing rate) map to Salesforce Tasks with custom fields for Duration__c, BillingRate__c, and Matter__c lookup. Alternatively, a TimeEntry__c custom object preserves all billing detail if the firm needs granular billing reporting.

Rocket Matter expenses (date, amount, category, matter, description) map to a custom Expense__c object in Salesforce with lookup to Matter__c for direct association with billing records. Expenses do not integrate with Salesforce native expense management solutions but can be linked to custom approval workflows and reporting dashboards if the firm requires expense tracking within Salesforce.

Rocket Matter invoices in LEDES 1998B format export as PDF attachments and are linked to the Matter__c record. Invoice totals, status, and payment history migrate as custom fields on Invoice__c. Original invoice PDFs stored as Salesforce Files attached to the matter.

Rocket Matter trust account transactions (client, matter, transaction type, amount, date, running balance) require a custom TrustTransaction__c object since Salesforce has no native trust accounting model. This preserves audit trails for IOLTA compliance and historical reference, but firms must perform three-way reconciliation (bank statement, client ledger, IOLTA account) in a separate accounting system post-migration.

Rocket Matter tasks map to Salesforce Tasks with Subject, ActivityDate, Status, Priority, and WhatId (linked to Matter__c). Original assignees resolved by email match to Salesforce users for proper task ownership. Overdue and recurring tasks flagged in the migration report for manual review and reassignment before the cutover window closes.

Rocket Matter calendar events (court dates, depositions, client meetings) map to Salesforce Events with StartDateTime, EndDateTime, Subject, WhatId (Matter__c), and WhoId (Contact). Client-facing events link to the relevant Contact record for full visibility into scheduled activities across matters and clients during the migration and post-cutover periods.

Rocket Matter notes migrate as Salesforce Notes (legacy Note object) or ContentNotes (Lightning-compatible rich-text notes). Body text, created date, and author preserved with full fidelity. Notes linked to Matter__c or Contact via ContentDocumentLink records, ensuring searchable content and proper sharing across teams with Salesforce's native access controls.

Rocket Matter document attachments (pleadings, contracts, correspondence) re-upload to Salesforce Files as ContentVersion records. Files linked to the associated Matter__c or Contact via ContentDocumentLink for version tracking and access management. File size limits (Salesforce default 25MB per file) apply — large files flagged for chunking into smaller segments during the migration process.

Rocket Matter matter custom fields (practice area classifications, court information, opposing counsel, statute of limitations) create corresponding __c fields on the Matter__c object. Select-list custom fields map to Salesforce pick-list values with value-by-value mapping, preserving all available options and maintaining referential integrity across the migrated data set.

Rocket Matter client custom fields (bar number, referral source, client classification) map to custom fields on the Salesforce Contact object. Custom field type conversion (date, number, pick-list) handled per field definition in Rocket Matter, ensuring accurate data typing, validation rules, and default values are applied correctly during the migration.