Migrate from BackDocket to Microsoft Dynamics 365 Sales

BackDocket Contact records map directly to Dynamics 365 Contact rows via a one-to-one field mapping. The primary email address from BackDocket maps to the standard emailaddress1 field in Dynamics, and the contact's full name splits into firstname and lastname fields. BackDocket contact IDs are preserved in a custom Source_ID__c field on the Contact record to enable de-duplication on delta runs and traceability back to the source system.

When a BackDocket Contact represents a law firm or corporate client rather than an individual, the contact's associated organization maps to a Dynamics 365 Account. The Account name is extracted from BackDocket's organization-name field and created before Contact records are upserted to maintain referential integrity.

BackDocket Matter has no direct CRM equivalent — matters describe legal cases with matter type, status, responsible attorney, and court jurisdiction. We create a custom Matter__c Dataverse table with columns for matter_type, status, assigned_attorney, court_jurisdiction, and opening_date. The custom table is created in the Dynamics environment before migration loads any records.

BackDocket Claim records represent individual legal claims within a Matter. Revenue-generating claims (e.g., plaintiff claims seeking damages) are mapped to Dynamics 365 Opportunities with estimated_value and close_date. Non-revenue claims are mapped to a custom Claim__c table linked to the Matter__c parent record via a lookup relationship.

BackDocket Tasks map to Dynamics 365 Tasks with subject, description, scheduledend (due date), and priority fields carried over directly. The task owner resolves against Dynamics users by matching the assigned user email to the userprincipalname field. Parent references link tasks to the corresponding Matter__c or Contact record, maintaining the relationship hierarchy from the source BackDocket instance.

BackDocket calendar entries for court dates, depositions, and firm meetings map to Dynamics 365 Appointments. Start time, end time, location (court address or meeting room), and required attendees are translated from the BackDocket event fields. Non-Microsoft invitees are flagged for manual re-invitation after migration completion.

BackDocket documents and files are downloaded from the platform's storage, then uploaded to the SharePoint site associated with the target Dynamics 365 environment. A SharePointDocumentLocation record is created linking the file to the parent Contact, Matter__c, or Claim__c record. Inline document previews within BackDocket notes are preserved as Note records with attachment flag.

BackDocket user records map to Dynamics 365 SystemUser entries by matching the email address. The migration plan flags any BackDocket user without a corresponding Dynamics license as 'orphaned owner' — their records are assigned to a designated fallback SystemUser and logged for admin review before cutover.

BackDocket custom properties on any entity are read from the API response and translated to Dataverse custom columns on the equivalent entity or table. Data types are mapped: text strings to nvarchar, numbers to decimal or integer, dates to datetime, and pick-lists to option sets. Each custom column is created in the target Dynamics environment before the full migration run.

BackDocket intake records capturing prospective client information map to Dynamics 365 Leads. Fields like prospect_name, referral_source, case_type_interest, and initial_contact_date are mapped to the corresponding Lead columns. The lead is routed to the responsible attorney based on BackDocket intake assignment rules.