Migrate from Lead Docket to HubSpot

Lead Docket API cannot update existing records — delta runs require re-export or manual reconciliation

Lead Docket's API is write-limited: integrations can only create new leads in Lead Docket. This is a documented constraint confirmed on LinkedIn and in Lead Docket's own integration documentation. For migration, it means any records modified in Lead Docket after the initial export snapshot (during the delta-pickup window) must be either manually re-entered into HubSpot or reconciled by your team. We flag records with changes during cutover so nothing silently drops, but the Lead Docket API cannot push those updates automatically the way HubSpot's full CRUD API can on the destination side. This is a source-platform limitation, not a FlitStack constraint.

Lead Docket's eleven fixed statuses have no direct HubSpot lifecycle stage equivalent

HubSpot's lifecycle_stage property uses a fixed set of values (subscriber, lead, MQL, SQL, customer, evangelist) that are designed for B2B marketing and sales funnels, not legal intake stages. Lead Docket's eleven statuses — New Lead, Attempted Contact, Qualified, Dead, Converted, and others — don't map 1:1 to any HubSpot native property. We create a custom pick-list property (Lead_Status__c) on the HubSpot contact and map each Lead Docket status to a value your team defines. The risk is that HubSpot's reporting and automation triggers are keyed to lifecycle_stage, not your custom status — if your firm relies heavily on intake-stage reporting, plan for custom dashboards and workflow enrollment criteria using your custom property rather than the native lifecycle_stage field.

Lead Docket automations and attorney rotation rules do not migrate — rebuild is required

Lead Docket's automations (status-change triggers, lead form routing, Filevine push on conversion) are a paid add-on and operate under Lead Docket's proprietary automation engine. HubSpot's workflow builder handles enrollment-based automation with branching logic and delayed actions, but the two engines share no migration path — every automation must be rebuilt from scratch. Similarly, Lead Docket's Attorney Rotation feature (which assigns leads round-robin among attorneys) has no HubSpot native equivalent. We export both as reference documents for your HubSpot admin or implementation partner. The rebuild effort scales with the number of active automations — a firm with five automations pays significantly less rebuild-scope than one with twenty.

Lead Docket's Filevine integration pushes signed cases as projects — this routing logic has no HubSpot equivalent

Many law firms use Lead Docket's Filevine integration to automatically create a Filevine project when a case converts. This is an outbound routing action with no direct HubSpot CRM equivalent — HubSpot can create records via workflow, but the Filevine integration and its project mapping must be rebuilt in Filevine's own integration settings or via a middleware tool like Zapier. We preserve the Filevine project ID as a custom property on the HubSpot deal if it was stored in Lead Docket, but the push-on-conversion logic is not part of the migration scope.

Lead Docket's expense tracking has no standard HubSpot CRM counterpart — financial data requires custom object or external tool

Lead Docket supports expense tracking (legal fees, case costs, settlement amounts) as part of its legal-intake model. HubSpot CRM has no native expense or financial tracking object at the Starter or Professional tier — this requires either a custom object (Enterprise) or a separate financial tool integrated via HubSpot's API. We can migrate expense records as custom properties on the HubSpot deal for reference, but ongoing expense logging should be planned as a post-migration configuration decision or maintained in a dedicated financial tool.