Migrate from Legistify to Salesforce Sales Cloud

Legistify's litigation cases carry case number, court, judge, opposite party, stage, keywords (for portal scraping), and webhook trigger URLs. Migrate as a Salesforce custom object with Status__c, Court__c, Judge__c, Opposing_Party__c, Stage__c, and Source_Keyword__c custom fields. Original Legistify matter ID stored as Legacy_Matter_ID__c for traceability.

Legistify contracts include counterparty, contract type, start/end dates, value, status, clause library reference, and approval state. Map counterparty to AccountId via a lookup, contract type to Type__c pick-list, and dates to Start_Date__c and End_Date__c custom fields. Clause library link migrates as Clause_Library_ID__c pointing to Clause__c records.

Legistify clause templates are stored with clause type, standardised flag, deviation-control settings, and body text. Each clause maps to Clause__c as a child of Contract__c. Clause_Type__c, Is_Standardised__c, Deviation_Control__c, and Body__c (long-textarea) custom fields carry the Legistify data. Approval-chain metadata cannot migrate and must be rebuilt in Salesforce Flow.

Legistify court dates, deadlines, and hearing schedules are calendar events linked to a matter. Migrate to Salesforce Event records with Subject, StartDateTime, EndDateTime, WhatId pointing to the Litigation__c record, and IsAllDayEvent. Original Legistify event ID preserved in Legacy_Event_ID__c custom field for delta-run matching.

Legistify's automated email alerts for case updates and court orders become Salesforce Task records. Task.Subject carries the alert summary, Task.Status tracks completion, and Task.WhatId links to the relevant Litigation__c record. Original alert sender and timestamp preserved in custom fields Legacy_Sender__c and Alert_Timestamp__c.

Legistify stores parties as free-text name and contact fields on matters and contracts. We resolve each party by email address (from Legistify's contact details if available) against Salesforce Contact records. If no match, we create an Account record and optionally a Contact, with Party_Type__c custom field distinguishing 'Opposing Party', 'Counterparty', 'Witness', etc.

Legistify compliance monitoring records hold regulation name, compliance status, deadline, and responsible-team fields. Migrate as a custom object with Regulation__c, Compliance_Status__c, Deadline__c, and Responsible_Team__c fields. Each record links via lookup to the related Account or Contract__c where applicable. We map Legistify's compliance status to a Compliance_Status__c picklist for reporting. If regulation categories, we add a Regulation_Category__c field. Automated alerts and escalation triggers do not migrate; rebuild them in Salesforce Flow.

Legistify stores contract drafts, executed agreements, and court filings as documents attached to matters and contracts. Documents are downloaded from Legistify's storage and re-uploaded as Salesforce Files, linked via ContentDocumentLink to the corresponding Litigation__c or Contract__c record. File size limit of 25MB per Salesforce file applies.

Legistify team members assigned to matters are matched by email address against Salesforce User records. Unmatched team members are flagged before migration — either invited to Salesforce first or assigned to a fallback User record. Legistify role metadata (e.g., 'Lead Counsel', 'Paralegal') migrates as Team_Role__c on a Litigation_Team__c junction object.

Legistify's clause-approval chains, compliance-routing rules, and automated escalation workflows have no Salesforce standard equivalent. We export the workflow definition as a PDF/JSON reference document so your Salesforce admin can rebuild the logic in Flow. This is always disclosed honestly — no automation migrates automatically.