Migrate from Captorra to Microsoft Dynamics 365 Sales

Captorra's lead record maps directly to Dynamics 365 Lead. We preserve the original Captorra lead ID in a custom Source_ID__c field for traceability. Lead status values from Captorra's intake-status field map to Dynamics 365 Lead Status pick-list via value-mapping. All standard Captorra lead fields (first name, last name, email, phone, source) transfer directly.

When a Captorra lead becomes a case/matter, we split the record into three Dynamics 365 objects: Contact (the client), Account (the law firm or referring organization), and Opportunity (the case/matter). Captorra's case number becomes the Opportunity name or a custom Case_Number__c field. The relationship is preserved via ContactId and AccountId on the Opportunity.

Captorra referral-source organizations map directly to Dynamics 365 Account records. The organization's name, website, and industry classification transfer as standard fields. Captorra's referral-source type classification—such as attorney referral, digital marketing partner, or general partner—becomes a custom Referral_Source_Type__c pick-list field on Account if the matching options do not already exist in the Dynamics 365 environment.

Captorra's configurable intake-form fields require custom fields in Dynamics 365. We create new_ prefix columns on the Lead or Opportunity table via the Dataverse API before migration runs. Each intake property (e.g., accident_type, injury_severity, insurance_carrier) becomes a corresponding Dynamics 365 custom field with matching data type.

Captorra's intake-stage values (New Lead, Under Review, Consultation Scheduled, Case Opened, Closed Won, Closed Lost) map to Dynamics 365 Lead Status values. Cases that become matters map to Opportunity Stage values. Each stage mapping is defined in a value-map table delivered with the migration plan before the run executes.

Captorra notes and interactions linked to a lead or case transfer as Dynamics 365 Activities. Call logs become Tasks with Type='Phone Call'. Meeting notes become Appointments. General notes become Notes (using the unified Notes experience). All activities retain their original created-on timestamp and owner assignment.

Captorra user assignments map to Dynamics 365 OwnerId by resolving the assignee's email address against the Dynamics 365 user list. Unresolved owners are flagged before migration and assigned to a fallback user or queue specified by the client's admin. This prevents records landing without an owner in Dynamics 365.

Captorra documents attached to leads or cases are downloaded and re-hosted in Dynamics 365's SharePoint integration (if configured) or attached as Note (File Attachment) records. Original filenames and MIME types are preserved. The parent record link to Lead or Opportunity is maintained.

Captorra's referral channel values—including Google Ads, Martindale-Avvo, partner referrals, and walk-in inquiries—map to the standard Dynamics 365 Lead Source field. Any Captorra-specific referral channels that do not correspond to standard Dynamics 365 options are mapped to a custom Captorra_Referral_Channel__c pick-list field on the Lead entity to preserve the full referral attribution history from the source system.

Captorra workflows, intake routing rules, and automated case assignments do not transfer to Dynamics 365. These are platform-specific business-logic constructs that require manual rebuild using Dynamics 365 Workflows, Power Automate, or custom Power Apps. We export Captorra workflow definitions as a reference document for the rebuild phase.