Migrate your Lead Docket data

Leads are the primary object in Lead Docket. We export all standard fields plus any custom properties. The platform supports 11 default lead statuses and allows custom statuses. We map each status label 1:1 into the destination's pipeline stages and preserve the lead's creation and closure dates for reporting continuity.

Contacts are separate from Leads and can be imported alongside them. We map contact records with name, phone, email, address, and any associated custom fields. Source attribution on contacts is preserved so marketing ROI data carries over.

Expenses can be imported via the standard import tool. We extract expense records tied to leads and map them into the destination's financial or billing object. Any expense categories not recognized in the destination require manual mapping during scoping.

Lead Docket supports user-defined custom fields on Leads and Contacts. We detect all custom field definitions during the discovery scan and map them to equivalent custom fields in the destination, flagging any that lack a direct type match for manual review.

Case Types define the legal matter category for a lead. We preserve the Case Type label and associate it with the lead record. Where the destination uses a different taxonomy for matter categories, we map them by name and note any unmapped types for the customer to resolve.

Automations are a paid add-on and are not exposed via API. The automation engine can trigger status changes, send forms, push to Filevine, and send Vinesign templates with a 50-change-per-lead cap to prevent circular loops. We cannot export automations programmatically; they must be manually rebuilt in the destination system after migration.

Roles are labels attached to user accounts that correspond to positions in the firm (e.g., Intake Specialist, Attorney, Paralegal). We export role assignments so they can be recreated in the destination. Role-based permissions are not exported.

Attorney rotation is an optional configuration that distributes incoming leads fairly among attorneys. We document the rotation settings and queue order during discovery so they can be reconfigured in the destination platform's equivalent routing feature.

Lead Docket tracks the marketing channel or referral source for each lead. We preserve the full source attribution chain including UTM parameters, referral URL, and campaign name where available, mapping these into the destination's lead source fields.

Document templates and custom templates are stored in Lead Docket's template library and are not accessible via the export API. We recommend exporting these manually as a separate step before migration cutoff, then re-uploading to the destination.

Lead Docket integrations (including Filevine) can only push new leads into the target system and cannot update existing records. During migration, we flag any active integration connections that need to be reconfigured to point to the new destination, and we warn that two-way sync will not be available without manual re-pairing.