CRM migration
Field-level mapping, validation, and rollback between Lead Docket and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Lead Docket
Source
Freshsales
Destination
Compatibility
12 of 12
objects map 1:1 between Lead Docket and Freshsales.
Complexity
BStandard
Timeline
24–72 hours
Overview
Lead Docket and Freshsales both manage contacts and leads, but their data models diverge significantly on the details that matter for legal intake teams. Lead Docket organizes data around case types, lead statuses specific to law firms, attorney rotation rules, and paid-automation triggers. Freshsales uses a standard CRM object model with Leads, Contacts, Accounts, and Deals, plus lifecycle stages, territory management, and Freddy AI scoring. We map Lead Docket leads directly to Freshsales leads, preserving all standard fields and custom properties. Lead Docket's legal-specific fields—case types, lead statuses, and attorney assignments—migrate as custom fields in Freshsales since no native equivalent exists. Automations built in Lead Docket (which require a paid add-on) do not migrate and must be rebuilt using Freshsales Workflows, which operate on a different condition-based trigger model. Files and attachments from Lead Docket re-upload to Freshsales Files. We sequence the migration so foreign keys resolve correctly: contacts first, then leads, then custom field data attached to each record.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Lead Docket object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Lead Docket
Lead
Freshsales
Lead
1:1Lead Docket leads map directly to Freshsales leads. All standard fields (name, email, phone, address) transfer as-is. Custom lead properties migrate as Freshsales custom fields. The Lead Docket lead ID is preserved in a Source_System_ID__c field for delta-run deduplication. We also verify that any required pick-list values exist in Freshsales before migrating, and we set field-level security so the admin profile can read and edit the new custom fields.
Lead Docket
Contact
Freshsales
Contact
1:1Lead Docket contacts (related contacts on leads) map to Freshsales contacts. Contact custom fields migrate as Freshsales custom fields. The primary contact relationship to a lead is preserved via Freshsales' lead-conversion linking model. We also create contact custom fields in Freshsales before migration, set field visibility for the admin profile, and store the original Lead Docket contact ID in Source_System_ID__c for delta runs.
Lead Docket
Lead Status
Freshsales
Lifecycle Stage + Custom Pick-list
1:1Lead Docket's 11 legal-industry lead statuses (New Lead, Consult Scheduled, Contract Sent, etc.) do not have direct Freshsales lifecycle stage equivalents. We map each status to a custom pick-list field (LD_Lead_Status__c) on the Freshsales lead and optionally route values into lifecycle stages for reporting parity.
Lead Docket
Case Type
Freshsales
Custom Field (text or pick-list)
1:1Lead Docket's case-type classification has no Freshsales native equivalent. We create a Case_Type__c custom field on the Freshsales lead record and map values value-by-value. If the firm uses a finite case-type list, we configure this as a pick-list; otherwise it transfers as a text field.
Lead Docket
Lead Source / Marketing Source
Freshsales
Lead Source
1:1Lead Docket's source tracking fields (Lead Source, Marketing Source, Referral Source) map directly to Freshsales' standard Lead Source field. Multi-source setups that use all three fields require a custom field for the additional attribution data. We create Marketing_Source__c and Referral_Source__c as custom fields in Freshsales, map the values directly, and set field-level visibility for the admin profile before migration.
Lead Docket
Attorney Assignment
Freshsales
Owner / Custom Field
1:1Lead Docket's attorney assignment maps to Freshsales OwnerId by email match. If the firm uses attorney rotation rules, we flag this for manual rebuild in Freshsales Workflows since rotation logic is not a native Freshsales feature. The original assigned attorney is preserved in a custom field if rotation changes the owner at migration time.
Lead Docket
Task / Follow-up
Freshsales
Task
1:1Lead Docket tasks and follow-up items migrate to Freshsales Tasks with original due dates, owners, and status preserved. Task subject, description, and priority transfer directly. Tasks linked to specific leads carry the parent-record association. We also map any custom task fields, set the owner based on the Lead Docket user email, and preserve the original Lead Docket task ID in a Source_System_ID__c field for future delta runs.
Lead Docket
Appointment / Meeting
Freshsales
Appointment
1:1Lead Docket calendar appointments migrate to Freshsales Appointments with start time, end time, location, owner, and linked lead preserved. Conference or Zoom link fields map to the location field. We also capture any appointment description, set the owner by email lookup, and store the original Lead Docket appointment ID in Source_System_ID__c for delta synchronization.
Lead Docket
Lead Custom Fields
Freshsales
Custom Fields
1:1All Lead Docket lead custom fields (text, number, date, currency, pick-list) require corresponding Freshsales custom fields. We create the destination fields first, then map values. Field type compatibility is validated—currency maps to currency, dates to dates—to prevent type-mismatch errors. We also set field-level security for the admin profile and store the original Lead Docket field ID in a reference note for traceability.
Lead Docket
Contact Custom Fields
Freshsales
Custom Fields (on Contact)
1:1Lead Docket contact custom fields migrate to Freshsales custom fields on the Contact object. Contact-level custom fields tied to related contacts (not just primary contacts) transfer to the corresponding Freshsales contact record. Filevine sync mappings on Lead Docket contact fields are preserved as reference notes for manual reconfiguration.
Lead Docket
Attachment / File
Freshsales
Files
1:1Lead Docket files and attachments on leads and contacts re-upload to Freshsales Files, linked to the corresponding record. File size limits apply (Freshsales default 25MB per file). Inline images in notes are downloaded and rehosted as Freshsales attachments. We also verify that each file is under the 25MB limit and flag any oversized files for manual handling before the migration run.
Lead Docket
Lead Form Submission Data
Freshsales
Custom Fields / Activity Log
1:1Form field responses captured by Lead Docket lead forms migrate as custom field values on the Freshsales lead. If the form submission includes free-text notes, we also create a Timeline note entry for audit continuity. We map each form field to a corresponding Freshsales custom field, set field visibility for the admin, and preserve the original Lead Docket form submission ID in a Source_System_ID__c field for future reference.
| Lead Docket | Freshsales | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Lead Status | Lifecycle Stage + Custom Pick-list1:1 | Fully supported | |
| Case Type | Custom Field (text or pick-list)1:1 | Fully supported | |
| Lead Source / Marketing Source | Lead Source1:1 | Fully supported | |
| Attorney Assignment | Owner / Custom Field1:1 | Fully supported | |
| Task / Follow-up | Task1:1 | Fully supported | |
| Appointment / Meeting | Appointment1:1 | Fully supported | |
| Lead Custom Fields | Custom Fields1:1 | Mapping required | |
| Contact Custom Fields | Custom Fields (on Contact)1:1 | Fully supported | |
| Attachment / File | Files1:1 | Fully supported | |
| Lead Form Submission Data | Custom Fields / Activity Log1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Lead Docket gotchas
API write-only limitation blocks record updates
Automations are excluded from all export methods
Filevine integration has documented one-way sync issues
50-automation-change cap per lead
Custom fields require manual recreation and type mapping
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit Lead Docket data model and custom fields
We pull a full export of your Lead Docket data via the API and CSV export, catalog every custom field on leads and contacts, and map the 11 lead statuses and any case-type configurations. This audit identifies all custom fields that need Freshsales equivalents, flags any value-mapping requirements for pick-list fields, and surfaces integrations that write to Lead Docket's API (which must be updated post-migration).
Create Freshsales custom fields and configure the schema
We create all required custom fields in Freshsales: LD_Lead_Status__c (pick-list), Case_Type__c (text or pick-list), Marketing_Source__c, Referral_Source__c, Original_Create_Date__c, Original_Attorney__c, and Source_System_ID__c on the Lead object; and Source_System_ID__c on Contact. We configure pick-list values value-by-value based on your Lead Docket status and case-type lists, set appropriate field-level security so the admin profile can read and edit, then share the field configuration with your admin for review before records land. Any pick-list value that does not yet exist in Freshsales is added during this step to avoid mapping errors during migration.
Resolve owners by email and pre-map lead statuses
We match Lead Docket's assigned attorneys and user records to Freshsales users by email. Any attorneys without Freshsales accounts are flagged before migration so your team can invite them or assign their leads to a fallback owner. Simultaneously, we finalize the lead status value map so every Lead Docket status has a corresponding Freshsales pick-list value before the migration run.
Run sample migration with field-level diff
A representative slice of 100–300 leads migrates first, spanning multiple lead statuses, case types, and attorney assignments. We generate a field-level diff between the Lead Docket export and the Freshsales records so you can verify that custom field values populated correctly, lead status mappings rendered as expected, and owner resolution resolved all attorneys. No full run commits until the sample is approved.
Execute full migration with delta-pickup window
The full record set migrates into Freshsales. A 24–48 hour delta-pickup window captures any leads created or modified in Lead Docket during the cutover. All operations are logged in an audit trail, and one-click rollback is available if reconciliation reveals a mapping error. After go-live, we deliver a migration summary report showing record counts, unmapped values (if any), and owner resolution status.
Deliver rebuild reference for automations and integrations
We export your Lead Docket automation definitions (trigger conditions, actions, and timer logic) as a structured reference document for rebuilding in Freshsales Workflows. We also provide an integration audit listing every external tool that writes to Lead Docket's API, with updated Freshsales API endpoint guidance for each. These deliverables are shared on day one of the engagement so your admin can begin the rebuild in parallel with the migration.
Platform deep dives
Lead Docket
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Lead Docket and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Lead Docket: Not publicly documented.
Data volume sensitivity
Lead Docket doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Lead Docket to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Lead Docket to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Lead Docket
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.