Migrate from Lead Docket to Twenty CRM

Lead Docket's lead records map directly to Twenty's People object. Standard contact fields (name, email, phone, address) align 1:1. The 11 default lead statuses do not have a native Twenty equivalent and migrate as a custom picklist field on People. Leads with no associated company map as People with no companyId relation.

When a Lead Docket lead has a linked company, the company data extracts into a Twenty Companies record first, then the People record references it via companyId. The import order (Companies → People) follows Twenty's foreign-key constraint — the Company record must exist before the People record that references it.

Lead Docket company records map 1:1 to Twenty Companies. Company name, domain, address fields, industry, and employee count migrate directly. Parent-child company hierarchies in Lead Docket map to Twenty's ParentId field on the Companies object, preserving organizational structures. Any associated phone numbers, websites, and revenue data also transfer directly to the corresponding Twenty Companies fields.

Lead Docket's 11 default lead statuses (New, Working, Qualified, Consultation Scheduled, etc.) require value-by-value mapping to a Twenty custom picklist field (Case_Status__c). Status change timestamps from Lead Docket migrate as a separate custom datetime field (Status_Changed_At__c) if available via export.

Lead Docket's Case Type concept has no direct equivalent in Twenty. We represent it as a custom picklist field (Case_Type__c) on People, mapping each Lead Docket case type value to the corresponding picklist option. Teams using case-type-specific custom fields flatten those into Twenty custom fields applied universally to the People object.

Lead Docket's custom fields scoped to specific case types or intake form locations (Above Incident Details, Contact Information, etc.) cannot replicate their visibility rules in Twenty. We create flat custom fields on the People object under Settings → Data Model before import. Field order and visibility are not preserved — the admin recreates display logic in Twenty's view configuration post-migration.

Lead Docket's attorney rotation feature — which distributes inbound leads across attorneys based on a round-robin or weighted rule — has no equivalent in Twenty. We surface this in the migration plan as a rebuild item: either create a custom object in Twenty to track attorney assignments, or document the rotation logic for manual recreation in Twenty's task assignment system.

Lead Docket Automations (up to 50 status changes per lead) trigger on lead qualification events, sending forms, posting to Filevine, or routing to Vinesign. Twenty's workflow builder handles basic conditional routing but lacks native sequencing. We export the automation definitions as a rebuild reference document for your Twenty admin.

If Lead Docket stores deal or case-value data alongside leads (e.g., estimated case value, referral source linked to a revenue figure), that data migrates as Twenty Opportunities. The Lead's owner maps to the Opportunity's assignee relation via email match against Twenty workspace members.

Lead Docket integrations post lead data to external systems via an endpoint URL in real time. Twenty has no native integration endpoint receiver. Integration connections must be rebuilt as Twenty webhooks (outbound) or by reconfiguring the third-party system to point at Twenty's API.

Lead Docket users and lead owners resolve by email match against Twenty workspace members. If a Lead Docket user has no matching email in Twenty, their records assign to a fallback owner specified by the client. Unmatched owners are flagged before migration so the team can invite them to Twenty first.