Migrate from CaseManager to Salesforce Sales Cloud

CaseManager cases map directly to Salesforce Case records. The CaseNumber, Subject, Description, Status, Priority, and origin fields align to Salesforce standard fields. CreatedDate and LastModifiedDate are preserved via Original_Create_Date__c custom fields since Salesforce's system timestamps reflect migration time. OwnerId resolves by email match to Salesforce Users.

CaseManager party contacts with an email address map to Salesforce Contact records linked to an Account. Contact.FirstName, LastName, Email, Phone, and Title map directly. CaseManager parties without email become Contacts on a default 'Unresolved Party' Account for review. Role type (Plaintiff, Defendant, Witness) is preserved in a Role__c custom field on the Contact record.

CaseManager party records that represent organizations (not individuals) map to Salesforce Account records. Account.Name, Website, Industry, and BillingAddress map directly. CaseManager does not always separate individual and company parties, so parties with a company name but no individual name become Account records; parties with both become both Account and Contact.

CaseManager allows multiple parties of different types per case (e.g., one case with a Plaintiff, two Defendants, and a Witness). Salesforce Case does not natively support multi-party roles. We create a Case_Party__c junction object with Case__c (lookup), Contact__c (lookup), and Role__c (picklist) fields so each party-role assignment is preserved as a separate record.

CaseManager tasks attached to a case map to Salesforce Task records with WhatId pointing to the Case. Subject, Status, Priority, ActivityDate, and Description map directly. Task.Type defaults to 'Case Task' for traceability. Completed tasks with a completed date map with Status = 'Completed' and CompletedDateTime preserved via a custom field.

CaseManager meetings and calendar entries map to Salesforce Event records linked to the Case via WhatId. Subject, StartDateTime, EndDateTime, Location, and Description map directly. Recurring meetings in CaseManager generate multiple Event records — one per occurrence — to match Salesforce's non-recurring Event model.

CaseManager case notes map to Salesforce Notes attached to the Case. Note.Title becomes the CaseManager note subject or a truncated body. Rich-text formatting is preserved where CaseManager exports HTML content. Salesforce Notes (modern) rather than the legacy Note object is used. Owner of the note resolves by email match to the Salesforce User who created it in CaseManager.

CaseManager file attachments are uploaded to Salesforce as ContentVersion records, creating ContentDocument links to the Case via ContentDocumentLink. File name, description, and content type (MIME type) are preserved as ContentVersion metadata. Files over 25MB require chunked upload via the Salesforce Bulk API. CaseManager document version history maps as separate ContentVersion records ordered by version number.

Every CaseManager custom property on a case requires a corresponding Salesforce custom field created before migration. We generate the field creation plan (name, type, pick-list values) based on CaseManager's field metadata. Pick-list value mappings are applied per value; date fields use Salesforce Date type; numeric text fields use Number type.

Custom properties on CaseManager parties migrate as custom fields on Salesforce Contact. For organization-type parties that map to Account, those custom fields migrate to the Account custom fields. Field type mapping follows the same logic as case custom fields — pick-list to pick-list, date to date, text to text.

CaseManager AssignedTo is a user reference that maps to Salesforce Case.OwnerId. Resolution uses email matching — if a CaseManager user email matches an existing Salesforce User email, OwnerId is set directly. Unmatched users are flagged before migration; your team either invites them to Salesforce or assigns their cases to a fallback Salesforce Queue.

The CaseManager internal case identifier is stored as a custom text field (Legacy_Case_ID__c) on the Salesforce Case record for full traceability, cross-referencing between systems, and delta-run deduplication. This custom field is indexed in Salesforce for fast lookups during the cutover delta-pickup window, ensuring efficient reconciliation of records modified during the migration run.