Migrate from AgileCase to Freshsales

Cases map 1:1 to FreshSales Deals. Case name becomes Deal name, case value/amount maps to FreshSales Amount, and Case status is mapped value-by-value to FreshSales Deal stage per pipeline. Owner resolves by email match. FreshSales Deal Amount field accepts decimal values; case amounts with currency symbols are stripped of non-numeric characters before insert.

Contacts map to FreshSales Contacts, but FreshSales requires an AccountId on every Contact record. AgileCase contacts without a primary company are linked to a default 'Unassigned Accounts' record or your specified default Account. Email is the unique identifier for deduplication.

Companies map 1:1 to FreshSales Accounts. Company name becomes Account Name; domain/website maps to Account Website. AgileCase parent-child company hierarchies map to FreshSales Parent Account field. Parent records are migrated before child records to resolve the ParentId foreign key correctly.

AgileCase Tasks map directly to FreshSales Tasks. Subject, description, due date, priority, and status all map field-by-field. Owner resolution by email match. Completed tasks carry their completion timestamp; open tasks carry their original due date. FreshSales task status values (Open, Completed) are mapped from AgileCase task status values.

AgileCase Notes map to FreshSales Notes. Note title becomes the Note subject; note body becomes the Note body. Original create date is preserved as a custom Created_Date__c field. Rich-text formatting in AgileCase notes is flattened to plain text for FreshSales Note compatibility.

AgileCase file attachments are downloaded and re-uploaded to FreshSales as Files. File name and description are preserved. FreshSales file size limits (25MB per file by default) apply; files exceeding the limit are flagged for manual handling. Inline images in notes are extracted and rehosted as separate files.

AgileCase users are matched to FreshSales users by email address. Unmatched AgileCase users are flagged before migration; you can either invite them to FreshSales first or assign their records to a fallback user. System-level or admin users without email equivalents are mapped to a designated FreshSales admin.

AgileCase pipeline and case-status names are mapped value-by-value to FreshSales Deal pipeline stages. Each AgileCase pipeline becomes a FreshSales pipeline with its own stage pick-list. Stage probability and forecast category are re-applied from FreshSales defaults or your specified values during mapping setup.

AgileCase tags migrate to FreshSales tags as string arrays. Tags on Cases become tags on Deals; tags on Contacts become tags on Contacts. FreshSales tag API accepts arrays of strings and creates tags on the target record. Duplicate tag names across objects are handled via namespaced prefixes if needed.

AgileCase custom fields on Cases, Contacts, and Companies require pre-created FreshSales custom fields or custom modules before migration. We deliver a custom-field setup plan listing each AgileCase property, its data type, and the FreshSales field type to create. Complex AgileCase custom objects with many-to-many relationships become FreshSales custom modules with lookup fields.

AgileCase automations (task assignments, email triggers, field updates, case-plan rules) cannot be migrated to FreshSales Workflows. The two platforms use different rule engines with different trigger-action models. We export AgileCase workflow definitions as a structured document to serve as a rebuild reference for your FreshSales admin.

AgileCase email templates are not migratable. FreshSales has its own email template system tied to Sales Sequences and Workflows. We export AgileCase template content (subject, body, merge fields) as a reference document for your team to recreate in FreshSales Templates post-migration.