CRM migration

Migrate from Lead Docket to Freshsales

Field-level mapping, validation, and rollback between Lead Docket and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Lead Docket logo

Lead Docket

Source

Freshsales

Destination

Freshsales logo

Compatibility

100%

12 of 12

objects map 1:1 between Lead Docket and Freshsales.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Lead Docket logo

Lead Docket

What's pushing teams away

  • Reporting is weak—reviews across G2 and Capterra cite poor reporting accuracy and limited analytics as a persistent pain point for data-driven firms.
  • The platform's API is severely limited: integrations and external calls can only create new leads, not update existing records, which breaks live sync setups.
  • Messaging and communication features have reliability issues according to verified reviews, with users reporting dropped texts or notification failures.
  • The Filevine integration has known quirks—reviewers note minor but recurring issues when syncing lead data to Filevine case files.
  • Some users report billing surprises, particularly around the paid add-on model for automations, which are not included in base subscriptions.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Lead Docket objects map to Freshsales

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

maps to

Freshsales

Lead

1:1
Fully supported

Lead 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

maps to

Freshsales

Contact

1:1
Fully supported

Lead 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

maps to

Freshsales

Lifecycle Stage + Custom Pick-list

1:1
Fully supported

Lead 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

maps to

Freshsales

Custom Field (text or pick-list)

1:1
Fully supported

Lead 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

maps to

Freshsales

Lead Source

1:1
Fully supported

Lead 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

maps to

Freshsales

Owner / Custom Field

1:1
Fully supported

Lead 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

maps to

Freshsales

Task

1:1
Fully supported

Lead 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

maps to

Freshsales

Appointment

1:1
Fully supported

Lead 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

maps to

Freshsales

Custom Fields

1:1
Mapping required

All 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

maps to

Freshsales

Custom Fields (on Contact)

1:1
Fully supported

Lead 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

maps to

Freshsales

Files

1:1
Fully supported

Lead 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

maps to

Freshsales

Custom Fields / Activity Log

1:1
Fully supported

Form 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.

Gotchas + challenges

What specifically takes care here

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 logo

Lead Docket gotchas

High

API write-only limitation blocks record updates

High

Automations are excluded from all export methods

Medium

Filevine integration has documented one-way sync issues

Medium

50-automation-change cap per lead

Low

Custom fields require manual recreation and type mapping

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Lead Docket automations do not migrate to Freshsales Workflows

    Lead Docket's automations are a paid add-on and operate on an event-trigger model tied to lead status changes, form submissions, and timer-based triggers. Freshsales Workflows use a condition-based trigger model that evaluates field values at the time of record save. These are architecturally incompatible—no automation logic transfers automatically. We export the automation definitions from Lead Docket as a rebuild reference document, but every automation must be manually recreated in Freshsales Workflows by your admin or our team as a post-migration service.

  • Lead Docket's API cannot update existing lead records

    Lead Docket's API only supports creating new leads; integrations pushing data to Lead Docket cannot update existing records or write to custom fields. This is a known platform limitation documented in Lead Docket's integration docs. Freshsales' full CRUD API resolves this, but any integrations built against Lead Docket's write-only API must be reconfigured to target Freshsales endpoints post-migration. We provide an integration audit as part of the migration plan so your team knows which integrations need updating.

  • Attorney rotation rules have no Freshsales equivalent

    Lead Docket's attorney rotation feature distributes incoming leads across attorneys based on configurable round-robin rules. Freshsales lacks a native rotation or fair‑distribution mechanism; the OwnerId field must be assigned manually or through territory rules. If your firm relies on attorney rotation, this logic must be rebuilt using Freshsales Workflows or a third‑party assignment tool after migration. We capture the full rotation order, any case‑type routing conditions, and the number of attorneys involved so the rebuild can replicate the original behavior precisely. This documentation is included in the migration plan and shared with your admin before the cut‑over.

  • Lead status mapping requires manual value alignment

    Lead Docket's 11 legal-industry lead statuses (Consult Scheduled, Contract Sent, etc.) have no direct Freshsales lifecycle stage equivalents. We create a custom pick-list field (LD_Lead_Status__c) and map each value individually, but your team should verify that the mapped statuses align with your Freshsales reporting categories and sales process stages. Some firms prefer to collapse the 11 Lead Docket statuses into 3–4 Freshsales lifecycle stages for cleaner pipeline reporting. We validate the mapping before migration and flag any missing pick‑list entries, then preserve the final LD_Lead_Status__c values on the Freshsales lead for historical reference and use them in Freshsales Workflows to trigger downstream actions.

  • Filevine sync mappings are not transferable

    Lead Docket's native Filevine integration syncs contact and case data bidirectionally. Freshsales does not have a native Filevine integration. If your firm uses Filevine, the sync relationship breaks at migration—you must set up a new integration between Freshsales and Filevine (via Zapier, Make, or a dedicated Filevine-Freshsales connector) post-migration. Lead Docket contact fields mapped to Filevine contact fields during the Filevine sync are preserved as reference notes in the migration export.

Migration approach

Six steps for a successful Lead Docket to Freshsales data migration

  1. 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).

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Lead Docket logo

Lead Docket

Source

Strengths

  • Purpose-built for legal intake rather than adapted from a horizontal CRM, with native case type and attorney rotation concepts.
  • Granular lead source attribution shows exactly where each case originated for marketing spend accountability.
  • User-friendly dashboard keeps all leads visible and organized without requiring technical training.
  • Automation engine can trigger status changes, send intake forms, and push leads to Filevine or Vinesign in real time.
  • Supports custom fields on leads and contacts, allowing firms to tailor the data model to their practice areas.

Weaknesses

  • API is write-only: external systems can only create new leads, not update or deduplicate existing records.
  • Reporting is widely cited as weak and inaccurate, limiting data-driven decision-making for firm management.
  • Automations are gated behind a paid add-on, increasing total cost of ownership beyond the base subscription.
  • Integrations are one-directional and unreliable for two-way sync, particularly the Filevine connection which has documented quirks.
  • Messaging features have reliability issues reported by multiple reviewers, including dropped texts and notification failures.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Lead Docket and Freshsales.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Lead Docket: Not publicly documented.

  • Data volume sensitivity

    B

    Lead Docket doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Lead Docket to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Lead Docket to Freshsales data migrations

Answers to the questions buyers ask most during Lead Docket to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Lead Docket to Freshsales migrations complete in 24–72 hours for under 5,000 records. Larger datasets with 5,000+ records or extensive custom field schemas (case types, multi-source attribution, attorney assignments) extend to 3–5 days. The longest planning step is auditing Lead Docket's custom fields and configuring the corresponding Freshsales schema—typically 1–2 days of your admin time concurrent with our field setup.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Lead Docket.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day