Migrate from Lawcus to Freshsales

Lawcus contacts map directly to Freshsales Contacts using the contact's email as the unique identifier. Primary phone, address, job title, and company name all transfer as standard Freshsales Contact fields. Owner resolution happens by email match against Freshsales users.

Lawcus leads with status 'New' or 'Contacted' route to Freshsales Leads. Lawcus leads that have converted (status 'Client') route to Freshsales Contacts. The split ensures unconverted prospects land in Freshsales Lead object for continued nurturing workflow entry.

Lawcus Lead records map to Freshsales Lead records with standard fields: first name, last name, email, phone, company name, lead status, and source. Custom lead fields on Lawcus create corresponding custom fields on Freshsales Lead before migration.

Lawcus Matters have no native Freshsales equivalent. We map matter fields as custom fields on the Freshsales Contact record (for client matters) or as a structured set of custom fields on the Contact object with a naming convention like Matter_CaseType__c and Matter_Stage__c. This preserves all matter data within the contact record in Freshsales.

For matters that represent billable client engagements, we offer a Matter-to-Deal mapping where each Lawcus matter becomes a Freshsales Deal with matter-stage data stored as custom fields on the Deal object (Matter_CaseType__c, Matter_PracticeArea__c, Matter_OpenedDate__c). This enables pipeline-style Kanban views for legal case tracking.

Lawcus activities — calls, emails, meetings, and tasks — map to Freshsales Sales Activities with original timestamps, activity type, owner, and linked contact preserved. Freshsales distinguishes between logged activities (Tasks) and calendar events (Events), which we map from Lawcus's activity type field.

Lawcus tasks map to Freshsales Tasks. Task subject, description, due date, priority, status, and assignee all transfer. Recurring tasks in Lawcus create individual task records in Freshsales since Freshsales handles recurrence through its own scheduler.

Lawcus contact custom fields (e.g., Practice_Area__c, Referral_Source__c) map to Freshsales Contact custom fields. Field data types are preserved: pick-lists become Freshsales dropdowns, text fields map to text, number fields to number. Freshsales requires custom fields to be created in the UI or API before data loads.

Lawcus matter-level custom fields create corresponding custom fields on the Freshsales object where the matter data lands (Contact or Deal). Each custom field is created in Freshsales first, then populated during migration with type-aware mapping from the Lawcus field definition.

Lawcus users are matched to Freshsales users by email address. Unmatched owners are flagged before migration runs. Your team either creates Freshsales user accounts first or assigns unmapped records to a designated fallback owner to prevent orphan records.

Lawcus documents and files attached to contacts or matters are downloaded and re-uploaded to Freshsales Files. File size limits apply (Freshsales file storage limits vary by plan). Inline images in notes are extracted and re-hosted on Freshsales' storage.

Lawcus workflows, email automations, and task assignment rules do not migrate. We export workflow definitions as a structured JSON document so your Freshsales admin can rebuild them using Freshsales Workflows on Growth+ plans or Freshsales Automate on Pro/Enterprise.