Migrate from CaseManager to Freshsales

CaseManager Cases map directly to Freshsales Deals. Case title and description transfer as Deal name and details. Case status values require value-mapping to Freshsales stage names — each distinct CaseManager status maps to a corresponding stage in the target pipeline. Close date maps to Freshsales Close Date.

CaseManager status values (e.g., Open, Pending, Closed, On Hold) map to Freshsales stage names per pipeline. Probability and forecast category are applied per stage after mapping. We preserve the original status-transition timestamps as custom datetime fields if they exist in CaseManager.

CaseManager Contacts and Case Parties map to Freshsales Contacts. Name, email, phone, address, and job title transfer directly. If a Contact is associated with multiple cases in CaseManager, all case associations surface as Deal Contact Roles in Freshsales. Primary role defaults based on most-recent case activity.

CaseManager Organizations map to Freshsales Accounts. Organization name, domain, industry, employee count, and address fields transfer directly. Parent-child organization hierarchies in CaseManager translate to Freshsales Parent Account relationships — parent records must be migrated before child records to resolve foreign key dependencies and maintain the hierarchy intact in Freshsales.

CaseManager Activity records and Notes map to Freshsales Tasks and Appointments. Activity type determines the destination: general notes and updates become Tasks with Type='Note'; scheduled calls and meetings become Appointments. Original timestamps and owner assignments are preserved. Rich-text formatting in CaseManager notes converts to plain text in Freshsales Notes.

CaseManager file attachments on cases download and re-upload to Freshsales Files, linked to the corresponding Deal record. File size limits apply: Freshsales default is 25MB per file. Inline images in CaseManager notes are extracted and rehosted as separate file attachments in Freshsales.

CaseManager custom fields on Cases migrate as Freshsales custom fields on Deals. Field types are preserved where possible: text, number, date, and pick-list types map directly. Multi-select pick-lists in CaseManager map to Freshsales multi-select custom fields. We deliver a custom-field creation plan before migration so your Freshsales admin can pre-configure the schema.

CaseManager custom fields on Contacts migrate as Freshsales custom fields on Contacts. Standard field types map directly. Any pick-list or multi-select fields require value-by-value mapping to Freshsales pick-list options if different values exist. CaseManager contact-specific data (e.g., bar numbers, client IDs) becomes a custom text field on the Freshsales Contact record.

CaseManager users and case owners resolve to Freshsales users by email match. Unmatched owners are flagged before migration — your team either creates Freshsales users first or assigns their records to a fallback owner. All CaseManager user names and email addresses are preserved in a custom field on the Deal record for audit traceability.

CaseManager case types or categories with more than 5–6 distinct values map to a Freshsales custom pick-list field (Case_Type__c) rather than creating separate pipelines. If your team needs pipeline-level filtering by case type, we recommend creating separate Freshsales Pipelines per type on Pro and Enterprise plans — this requires Freshsales admin configuration before migration.

CaseManager priority levels (High, Medium, Low) migrate as a Freshsales custom pick-list field on Deals (Priority__c). Freshsales does not have a native priority field on Deals — the custom field preserves the original CaseManager priority value for sorting and filtering in list views and reports.

CaseManager workflows and automatic assignment rules do not migrate to Freshsales. They require manual rebuild in Freshsales Workflows (Pro and Enterprise plans). We export your CaseManager workflow definitions as a JSON reference document for your Freshsales admin to use as a rebuild guide. The data layer migrates; the automation layer does not.