Migrate from Column Case Management to Salesforce Sales Cloud

Column Cases map directly to Salesforce Case records. Case number, status, priority, description, and assigned investigator all have Salesforce equivalents. Column's case-specific fields (case type, jurisdiction) become custom fields on the Case object with __c suffix. Pre-create case status values in Salesforce matching Column's pick-list before migration runs.

Column Subjects are persons under investigation. They split into Salesforce Contact records for known persons with a Contact.AccountId pointing to a related Account, or Salesforce Lead records for persons not yet associated with an Account. Subject metadata (status, type, relationship type) migrates as custom fields on the chosen object. Your team decides the split rule before migration — typically by Subject status or type.

Column Complainants are persons or entities filing a complaint. They map to Salesforce Contact records linked to an Account representing their organization. For anonymous complainants without a company affiliation, FlitStack attaches them to a designated default Account so the Contact.AccountId foreign key resolves cleanly.

Column Evidence records carry file references, evidence IDs, upload dates, and file types. The metadata maps to custom fields on the Salesforce Case record (Evidence_ID__c, Evidence_Upload_Date__c, File_Type__c). The actual file content re-uploads to Salesforce Files via ContentVersion. Evidence-to-Case linking uses the Salesforce CaseId field on ContentDocumentLink.

Column Activity records (interviews, updates, evidence reviews) map to Salesforce Task records. The activity description becomes Task.Description, the Column activity date becomes a custom datetime field Task.Activity_Logged_Date__c, and the Column activity type maps to a custom pick-list field Task.Investigation_Activity_Type__c since Salesforce's native Task.Type pick-list does not cover investigation-specific activity categories.

Column stores assigned investigator names on Cases. FlitStack resolves each Column investigator name to a Salesforce User record by email match. Unmatched investigators are flagged before migration — your team either creates Salesforce User accounts for them or assigns their Cases to a fallback Owner. This is the highest-risk foreign key in the migration because a Case without a valid OwnerId fails to insert.

Column's built-in audit log tracks every field change, status transition, and user action with timestamps. Salesforce's native Field History Tracking covers only enabled fields on the Case object and does not preserve a continuous chronological log. FlitStack imports Column's audit history as a series of Task records with a custom activity type Audit_Log_Entry__c, linked to the Case, so investigators retain a full change timeline in Salesforce.

Column links Subjects to Cases with a relationship type field (e.g., Suspect, Witness, Victim) stored at the subject-record level. Salesforce has no native way to store this role label on a Contact-Case relationship. FlitStack creates a custom junction object Subject_Case_Role__c linking Contact to Case with a Role__c pick-list field capturing the Column relationship type value.

Column stores email correspondence threads linked to Cases. Emails map to Salesforce EmailMessage records attached to the Case. Thread metadata and subject lines preserve as EmailMessage headers. Attachments within email threads follow the same ContentVersion re-upload path as Evidence files.

Column's Solvability Matrix is an investigation-specific scoring or categorization tool with no Salesforce standard equivalent. We preserve the matrix name and any associated score or rating as a custom field on Case (Solvability_Matrix_Score__c) and surface the underlying data as a Salesforce Report type so your team can rebuild the matrix logic as a dashboard component in the destination.

Column's custom objects (additional entity types beyond the standard set) map 1:1 to Salesforce custom objects. Custom object fields follow the same __c suffix and type-mapping rules as standard field migrations. N:N relationships between custom objects in Column require junction objects in Salesforce, which FlitStack surfaces in the pre-migration schema plan.