Migrate from BackDocket to Salesforce Sales Cloud

BackDocket contacts map directly to Salesforce Contacts. Each BackDocket contact must resolve to a primary AccountId — contacts without a company in BackDocket attach to a default 'Unassigned Account' record. Email addresses serve as the unique match key for de-duplication.

BackDocket companies map to Salesforce Accounts. Company name becomes Account.Name; domain becomes Account.Website. Parent-child company hierarchies in BackDocket map to Account.ParentId. Multi-company contacts collapse to one primary AccountId with secondary relationships via Account Contact Relations. The mapping also transfers billing address fields (BillingStreet, BillingCity, etc.) and maps the industry pick-list where BackDocket industry values align to Salesforce industry pick-list values. This preserves full company profile information in Salesforce.

BackDocket cases have no native Salesforce equivalent — we create a Case_Matter__c custom object. Fields map to custom properties: Case_Name__c, Case_Type__c, Status__c, Filed_Date__c, Claim_Amount__c. The original BackDocket case ID stores in Source_System_ID__c for traceability. Additional custom fields such as Case_Description__c (textarea) and Assigned_Attorney__c (lookup to User) are included to capture all relevant case metadata. The mapping also preserves the case creation timestamp in a custom datetime field for audit continuity.

BackDocket tasks map to Salesforce Tasks. Subject becomes Task.Subject, status maps to Task.Status (Open/In Progress/Completed), due date maps to Task.ActivityDate. Task WhoId links to the migrated Contact; Task WhatId links to the Case_Matter__c record. Priority also transfers via Task.Priority, mapping BackDocket priority values to Salesforce priority pick-list options. Recurring tasks are flagged in a custom field for admin review, as Salesforce handles recurrence differently.

BackDocket files re-upload to Salesforce Files. Each file becomes a ContentVersion record linked to the appropriate ContentDocumentId. Files attach to the Contact or Case_Matter__c record via ContentDocumentLink. Original filenames and MIME types preserved; Salesforce's 25MB per-file limit enforced. Version history is preserved by storing the original upload date in a custom field, and files exceeding the 25MB limit are flagged during the pre-migration audit.

BackDocket calendar events with start and end times map to Salesforce Events. Event.Subject, Event.StartDateTime, Event.EndDateTime, and Event.Location transfer directly. Owner resolves by email match to Salesforce users. Recurring events map to Salesforce Series if available, otherwise each occurrence is stored as a separate Event record with a custom recurrence flag. The original BackDocket event description copies into Event.Description for audit continuity.

BackDocket staff records map to Salesforce Users by email address. If a BackDocket user email does not match a Salesforce User, the record assigns to a fallback admin owner and flags for review. Role and profile assignment requires Salesforce-side configuration post-migration.

Every BackDocket custom field that has no Salesforce equivalent becomes a custom field on the target object. BackDocket text fields become Text(255) or TextArea; pick-lists become Picklist with value-by-value mapping; numeric fields map to Number; date fields map to Date. The custom field API name follows BackDocket field name conventions with __c suffix.

BackDocket e-signature requests have no direct Salesforce equivalent. We preserve the request metadata (document name, signers, status, timestamp) as a custom Task record with DocuSign_Status__c and Signer_List__c fields for reference. DocuSign integration must be configured in Salesforce separately. The metadata includes envelope ID and original document link for audit reference. Active DocuSign account and Salesforce connector setup are required to recreate envelopes.

BackDocket intake responses that contain prospect information (potential client before engagement) route to Salesforce Lead. Responses that represent active client intake route to Case_Matter__c. The split decision uses the BackDocket intake form type field. Your team defines which forms map to which Salesforce object during planning.