Migrate from Lawmatics to Freshsales

Lawmatics contacts map directly to Freshsales contacts. Email is the primary match key for deduplication. Contacts without a primary company in Lawmatics land as Freshsales contacts with no AccountId — the admin assigns the AccountId post-migration or the contact remains unlinked.

Lawmatics contacts that are cold prospects (no Matter associated) route to Freshsales Leads instead of Contacts. The split rule checks whether the contact has any linked Matter record — if none exist, the record goes to Lead to keep the Contacts object clean for active clients.

Lawmatics companies map to Freshsales accounts. The firm name maps to Account Name, domain maps to Website, and the industry pick-list maps via value mapping to Freshsales' Industry pick-list. Multi-company contacts (Lawmatics allows N:N) collapse to the primary AccountId with others stored as Account Contact Relationships.

Lawmatics Matter is the central intake record and does not have a direct Freshsales equivalent. The Matter decomposes into an Opportunity record, with Matter-level fields (status, practice area, intake source, date of incident) stored as custom fields on the Opportunity. The Matter's primary contact links to the Opportunity via the standard Contact-to-Opportunity association.

Lawmatics Matter Statuses (e.g., New Intake, Qualified, Signed, Active Matter, Closed) map to Freshsales deal stage values per pipeline. Each practice-area pipeline in Freshsales needs its own stage pick-list — firm-defined Matter Statuses are mapped value-by-value to the corresponding Freshsales stage.

Lawmatics practice areas (Family Law, Personal Injury, Estate Planning, etc.) have no native Freshsales equivalent. We create a custom pick-list field Practice_Area__c on the Opportunity and map each Lawmatics practice area to the corresponding pick-list value. Firms with multiple pipelines may also use Freshsales Pipelines as a practice-area proxy.

Lawmatics tasks map directly to Freshsales tasks. The original assigned user is resolved by matching the Lawmatics user email to a Freshsales user account; unresolved owners are flagged for fallback assignment. Status, due date, and priority transfer without transformation, and any custom task fields are created as Freshsales custom fields. Tasks linked to a Matter are associated with the corresponding Opportunity after decomposition.

Lawmatics events map to Freshsales sales activities with type Event. Original start and end times, location, and assigned user are preserved. The event's linked contact and matter associations are resolved to Freshsales contact and opportunity links after the opportunity migration run.

Lawmatics notes map directly to Freshsales notes. Rich‑text formatting is converted to plain text or preserved as HTML based on the source export format, and any embedded file references are re‑attached to the corresponding Freshsales record. Parent record links to a contact or matter are resolved to Freshsales Contact or Opportunity lookups, preserving the note context across the new CRM.

Lawmatics files attached to contacts, companies, or matters are downloaded and re‑uploaded to Freshsales, preserving the original file name, creation date, and owner. Files are linked to the matching Freshsales Contact, Account, or Opportunity record, and any duplicate file names are handled with a collision‑resolution strategy. Upload respects Freshsales storage limits and enforces permitted file extensions.

Lawmatics custom fields are identified by the field_name(field_type) export header and are created as Freshsales custom fields with matching types. The mapping translates string to text, integer to number, boolean to checkbox, date to date, datetime to date_time, list to picklist, and lookup to lookup. Freshsales API names use a consistent convention (Field_Name__c) and pick‑list options are matched directly; any missing values are added to the picklist before import.

Lawmatics tags migrate as Freshsales tags on the matching record (Contact, Account, or Opportunity). Tags are transferred verbatim, preserving case and spacing, and duplicate tags are merged automatically. No tag taxonomy restructuring is performed unless the migration scope explicitly requests a rename or consolidation of tags. Freshsales tag limits (up to 250 tags per record) are enforced during import.

Lawmatics users are matched to Freshsales users by email address. Unmatched users are flagged before migration — the team either creates Freshsales accounts first or assigns records to a fallback user. Lawmatics custom roles do not map to Freshsales roles and must be rebuilt.

Lawmatics time-and-billing records ($29/user/month add-on) have no native Freshsales equivalent. These records are exported as reference CSVs and can be imported into a separate billing tool (Freshbooks, QuickBooks, LawPay) or preserved as a custom reference object. This is always disclosed upfront and scoped separately.