Migrate from The Attorney Case File to Salesforce Sales Cloud

The Attorney Case File stores client details within the workbook. We extract client name, email, phone, address, and bar number into Salesforce Contact records. A default Account (using the firm name or 'Individual Client' for solo practitioners) is created and linked via AccountId. For corporate clients, the Account represents the company and Contact represents the attorney of record.

Each matter in The Attorney Case File maps to a Salesforce Opportunity. The Opportunity Name becomes the matter title. Practice area determines RecordTypeId — personal injury, corporate transactions, family law, and criminal defense each get their own record type with scoped stage values. Matter status maps to Opportunity StageName via value mapping per record type.

The Attorney Case File's matter-type taxonomy becomes Salesforce Sales Process + Record Type pairs. Each practice area requires a pre-created RecordType in Salesforce so Opportunity StageName pick-list values are scoped correctly. We deliver the record-type setup plan before data migration begins so the schema is ready.

Status values like 'Active', 'Pending', 'Closed Won', 'Closed Lost' map to Opportunity StageName values. Each RecordType has its own stage pick-list, so the same source status may map to different StageName values per practice area. Stage-entered timestamps are preserved as custom datetime fields.

The Attorney Case File tracks billable hours per matter. We create a custom Billing_Entry__c object with fields for hours, rate, total amount, date, attorney reference, and Opportunity lookup. If your firm uses Salesforce Revenue Cloud, billing entries may map to OrderItems instead — we confirm the target schema during discovery.

Files attached to The Attorney Case File matter are re-uploaded to Salesforce Files (ContentVersion) and linked to the corresponding Opportunity via ContentDocumentLink. File size limits apply — Salesforce defaults to 25MB per file. Files over this threshold are flagged for chunked upload or alternative storage (SharePoint, S3) with link fields in Salesforce.

Court dates, deposition schedules, and deadlines from The Attorney Case File calendar map to Salesforce Events. Original start and end times are preserved. Events are linked to the relevant Opportunity (matter) via WhatId. Recurring events are mapped to Salesforce Series events where the source supports recurrence data.

Attorney to-do items and procedural reminders migrate as Salesforce Tasks. Task Subject becomes the description, Status maps to 'Not Started' / 'Completed', and Priority preserves the source urgency flag. Tasks link to the relevant Opportunity via WhatId and to the responsible attorney via OwnerId.

Case notes from The Attorney Case File migrate as Salesforce Notes (new Notes object, not legacy Note). Body content is preserved with original timestamps. Notes attach to the Opportunity record. Rich-text formatting is retained where the source API provides it.

The Attorney Case File stores opposing parties in case notes or custom fields. We create secondary Account records for counterparties and use a custom Matter_Party__c junction object to link the primary matter Account (the client) to opposing parties. This preserves the relationship without conflating clients and adversaries.

The Attorney Case File custom fields on matters (e.g., court jurisdiction, case number, statute of limitations) map to custom fields on Opportunity with __c suffix. Field types are preserved — pick-lists become pick-lists, dates stay dates, text fields map to text. We create the custom fields in Salesforce during the pre-migration schema setup phase.

Client-specific custom fields in The Attorney Case File (e.g., bar number, referral source, client classification) map to custom fields on Contact. Same-type preservation applies. For fields that apply to the corporate entity rather than the individual attorney, we map to custom fields on Account instead.