Migrate from Lead Docket to Salesforce Sales Cloud

Lead Docket leads map 1:1 to Salesforce Leads. The 11 Lead Docket statuses populate a custom Lead_Docket_Status__c pick-list field on the Salesforce Lead. Original status timestamps are preserved as a custom datetime field if the source exports them. Any status transition history exported from Lead Docket is stored in a related custom object or as a JSON blob in a long-text field for audit trail purposes.

If Lead Docket marks a lead as converted or qualified via a specific status value, those records can land as Salesforce Contacts instead of Leads. The mapping plan defines which Lead Docket statuses trigger the Contact split before migration runs.

Lead Docket stores contact details as sub-properties of a lead record. Salesforce requires a separate Contact object with a valid AccountId. We extract the contact portion, create the Account record first using the company name from the parent lead, then link the Contact to it via AccountId. This ensures referential integrity is maintained during the load sequence.

Lead Docket's company or firm name per lead maps to Salesforce Account.Name. The Account record is created first in the migration sequence to satisfy the Contact.AccountId foreign-key requirement. For solo practitioners where no company name exists, the Account name defaults to the contact's last name and is flagged in the sample migration diff for admin correction.

Every Lead Docket custom field gets a Salesforce __c custom field created by the admin before migration begins. The data type is mapped from Lead Docket's type selector (text, number, date, pick-list, checkbox, etc.) to the nearest Salesforce field type. Custom fields referencing other Lead Docket records (e.g., related lead IDs) require a custom lookup field in Salesforce.

Each of Lead Docket's 11 default status values maps to a corresponding value in the custom Lead_Docket_Status__c pick-list. If the firm has added custom statuses beyond the defaults, those require admin confirmation of intended Salesforce pick-list values before the field is created. The value-mapping table requires sign-off before the load job executes.

Lead Docket's Source Rules auto-populate a Marketing Source or Contact Source value. In Salesforce, the standard Lead Source pick-list captures this for reporting. A custom Marketing_Source__c field preserves the exact source string if the standard pick-list lacks a matching value, ensuring no source attribution data is lost during the migration.

Lead Docket's attorney rotation assigns leads round-robin to attorneys in a defined group. Salesforce has no built-in rotation model. We resolve each attorney to a Salesforce User by email match. The rotation logic itself must be rebuilt as a Salesforce Flow with a custom counter or round-robin assignment tool. We export the attorney group membership and rotation sequence for admin reference.

Lead Docket activity records (calls logged, emails, tasks) map to Salesforce Task records. Task Type, Subject, Description, Status, and ActivityDate transfer directly. Original owner resolved by email match to Salesforce User. Task WhoId links back to the Salesforce Lead or Contact record that was created during migration for proper activity attribution.

Lead Docket file attachments are downloaded from the source system and re-uploaded to Salesforce Files as ContentVersion records. Files are linked to the target Salesforce record (Lead, Contact, or Account) via ContentDocumentLink. Salesforce caps individual files at 25MB by default for standard uploads; larger files require Salesforce Content Delivery or external storage integration.

Lead Docket automations (status-change triggers, form-send triggers, integrations) do not transfer to Salesforce. We export automation definitions from Lead Docket as a written reference document listing every trigger, condition, and action. Your Salesforce admin uses this as a rebuild checklist for Flow before go-live, ensuring no automation logic is lost in the transition.