Migrate from Lead Docket to Microsoft Dynamics 365 Sales

Lead Docket API cannot update records — migration requires push-then-write pattern

Lead Docket's public API supports only lead creation — integrations can POST new leads but cannot PATCH existing records or retrieve lead data. This means the migration extract relies on Lead Docket's Export Via Push feature and manual CSV exports rather than programmatic read access. We must then write all records to Dynamics 365 via Dataverse API using a write-then-link pattern where foreign keys (AccountId on Contact, parentcustomerid on Lead) are resolved by creating parent records first. For accounts embedded in Lead Docket contacts without a formal Company object, we normalize company names into Dynamics Accounts before contacts land.

11 Lead Docket statuses require value-by-value mapping to Dynamics Lead Status or custom fields

Lead Docket ships with 11 default lead statuses including New, Incoming, Attempted, Contacted, Qualified, Dead, Converted, Retainer Signed, Case Opened, Closed, and Lost. Dynamics 365 Sales has 5 default Lead Status values (New, Contacted, Qualified, etc.). Statuses beyond the 5 defaults must be added as custom pick-list values in the Dynamics solution before migration — otherwise they are rejected by Dataverse validation. We pre-map each of the 11 Lead Docket statuses to either a Dynamics standard value or a custom new_leadstatus field so no data is dropped during the write phase.

Attorney Rotation logic cannot migrate — assigned attorney preserved as reference only

Lead Docket's Attorney Rotation feature distributes incoming leads across attorneys based on configurable round-robin or weighted rules. The rotation assignment itself is not stored as a static field on the Lead record — it is computed at assignment time. When we migrate, the attorney assigned at the time of the last export is preserved in a new_assignedattorney custom lookup field, but the rotation algorithm does not transfer. Dynamics 365 Sales does not have a native attorney rotation equivalent — your admin must configure a Power Automate flow or a custom plugin to replicate the rotation logic using Dynamics security roles and queues.

Lead Docket automations (paid add-on) have a 50-change cap that does not translate

Lead Docket Automations cap each lead at 50 triggered changes to prevent circular loops. This cap is a platform-level setting in Lead Docket with no equivalent in Dynamics 365 Sales. When we migrate leads that have been touched by automations, the change-count history is not accessible via the API export. Power Automate, the Dynamics replacement for Lead Docket automations, has no per-record change cap — so rebuilding automation logic from Lead Docket definitions requires a fresh audit of which triggers and actions were active and translating them into Power Automate cloud flows.

Source Rules in Lead Docket are automation logic, not data — attribution migrates, routing does not

Lead Docket Source Rules automatically assign Marketing Source and Contact Source values to incoming leads based on URL parameters, referral data, or form submissions. The resulting source value is stored as a field on the Lead record and migrates directly to Dynamics Lead Source (leadsourcecode). However, the rule logic itself — the if-this-then-that conditions — is not data that can be exported. Dynamics 365 Sales business rules and Power Automate can replicate the same attribution logic, but the rules must be rebuilt manually using the Lead Docket source-rule definitions as a reference document that we export during the migration kickoff.