Migrate from Lead Docket to HighLevel

Lead Docket leads map to HighLevel Contacts as the primary person record. The lead's contact information (name, email, phone, address) migrates directly. Lead-specific custom fields migrate as HighLevel Contact custom fields after the contact is created. This mapping preserves the full lead context, ensuring that historical data tied to the lead, such as case type or referral source, is available on the corresponding Contact for HighLevel's Workflow and reporting tools.

Lead Docket's 11 fixed lead statuses have no native HighLevel equivalent. We map each status value to a custom pick-list field (Lead_Docket_Status__c) on the Contact and create a pipeline stage alignment plan so status-based workflows can be rebuilt using HighLevel's Workflow engine's stage-change triggers.

Lead Docket Contact records (secondary contacts on a lead) map to HighLevel Contacts 1:1. Name, email, phone, and contact-specific custom fields migrate directly. A link back to the primary contact record is preserved via HighLevel's contact relationship field if available or a custom text link.

Lead Docket lead custom fields (case-type, attorney assignment, phase, etc.) are tied to the lead record. We create matching custom fields on the HighLevel Contact object using the same field type (text, number, date, pick-list) and migrate the values. Type mismatches (e.g., a Lead Docket currency field against a HighLevel text field) are flagged for manual correction before migration runs.

Lead Docket contact custom fields map directly to HighLevel Contact custom fields. We match by field name and create the field in HighLevel with the same type before migrating values. Lead Docket's Filevine contact field mapping is preserved as a custom text field in HighLevel for reference.

Lead Docket's marketing source and contact source values, including automated Source Rules, are merged into a custom field (Original_Source__c) on the HighLevel Contact. Source values are also applied as HighLevel tags so they can drive workflow segmentation without querying a custom field.

Lead Docket referral sources have no direct HighLevel equivalent. We create a custom pick-list or text field (Referral_Source__c) on the Contact object and migrate the value. Referral source-specific workflows in Lead Docket must be rebuilt in HighLevel's Workflow builder using this field as a trigger condition.

Lead Docket file attachments on leads are downloaded and re-uploaded to the corresponding HighLevel Contact's file storage. Files are associated by contact ID. HighLevel's 25MB per-file limit is enforced; files exceeding this are flagged for manual chunking or alternative storage before migration.

Lead Docket notes migrate to HighLevel's note system attached to the Contact record. Original create timestamps are preserved as a custom Created_In_Lead_Docket__c datetime field for audit continuity. Rich-text formatting in Lead Docket notes is preserved as plain text in HighLevel notes where possible.

Lead Docket automations are a paid add-on and cannot be exported or migrated. We document each automation's trigger (status change, form submission, timer) and action sequence as a rebuild specification for HighLevel's Workflow builder. Critical automations (follow-up reminders, status-change alerts) are rebuilt and tested before go-live.

Lead Docket's native Filevine sync — including phase mapping, document templates, and case-type configuration — has no equivalent in HighLevel. We export the Filevine phase names and document template list as a reference CSV so your team can rebuild the case workflow in HighLevel or re-establish a Filevine integration via HighLevel's webhook/API connections.

Lead Docket owner IDs resolve to HighLevel users by email match. Unmatched owners are flagged before migration — your team either creates the HighLevel user account or assigns those records to a designated fallback user. Owner resolution is verified during the sample migration phase before the full run commits.

Lead Docket case types define the legal matter category. We create a custom pick-list field (Case_Type__c) on the HighLevel Contact and optionally map each case type to a separate pipeline so stage progression reflects the firm's matter lifecycle. Pipeline creation in HighLevel is scoped during the pre-migration schema planning phase.