Migrate from Goodlegal to Freshsales

GoodLegal contacts (individuals associated with legal matters or documents) map 1:1 to Freshsales contacts. We preserve the contact's name, email, phone, and address fields, then attach the contact to the mapped Account (legal entity) via Freshsales' account_id lookup. All custom properties on the GoodLegal contact become Freshsales custom fields on the contact record.

GoodLegal legal entities — the organizations that are clients or counterparties in legal matters — map to Freshsales accounts. We preserve the entity name, address, industry classification, and owner. GoodLegal entity hierarchies (parent firm / subsidiary relationships) map to Freshsales' parent_account_id field where the hierarchy exists.

Each GoodLegal matter (a legal engagement tied to a client entity) becomes a Freshsales deal. The matter name maps to deal name, matter status maps to Freshsales deal stage via value mapping, and matter type or practice area maps to a custom field since Freshsales deals do not natively store matter category. The mapped Account (legal entity) links as the deal's primary account.

GoodLegal matter statuses (e.g., Intake, Active, Under Review, Closed) map value-by-value to Freshsales deal stage pick-list values. We map each GoodLegal status string to the closest Freshsales stage; probability percentages are assigned per stage per Freshsales' forecast category model. Unmapped statuses default to the Open stage with a flag for admin review.

GoodLegal documents and templates do not have a direct Freshsales equivalent. We export each document as a file and attach it to the corresponding Freshsales record — documents tied to a matter attach to the Deal, documents tied to a contact attach to the Contact, and entity-level documents attach to the Account. Version history is preserved as separate file versions where GoodLegal exposes version metadata via API.

GoodLegal contact status roles (Client, Lead, Counterparty, Witness) have no native Freshsales equivalent. We create a custom pick-list field (Contact_Role__c or Legal_Status__c) on the Freshsales Contact object and populate it with the source role value. This field is available on all Freshsales plans without a tier upgrade.

GoodLegal records document version changes, approvals, and comments as matter activity. We map these as Freshsales notes attached to the relevant contact, account, or deal record with a custom field noting the activity type (Version Change, Approval, Comment) and a timestamp sourced from GoodLegal's activity log. This preserves the full matter audit trail within Freshsales' timeline.

GoodLegal users who are assigned as matter attorneys, paralegals, or administrators map to Freshsales users by email address. Unmatched users are flagged before migration — your Freshsales admin either creates the user account first or assigns records to a fallback owner. GoodLegal role permissions (Attorney vs. Paralegal vs. Client Portal) do not migrate; Freshsales profile and permission set configuration is a separate destination-side step.

GoodLegal matter custom fields — practice area, jurisdiction, billing arrangement, related court — have no Freshsales deal native equivalent. We create matching custom fields on the Freshsales Deal object (e.g., Practice_Area__c as a pick-list, Jurisdiction__c as a text field) and populate them from the GoodLegal API. These are created in Freshsales settings before migration data lands.

GoodLegal automation rules (document generation triggers, matter routing, deadline reminders) cannot be auto-migrated to Freshsales Workflows 2.0. We export every GoodLegal workflow definition — trigger conditions, actions, and rules — as a structured JSON document that your team uses as a rebuild reference. Rebuilding these in Freshsales requires the Pro plan ($39/user/mo) for advanced workflow actions.