Migrate from Capsule CRM to Microsoft Dynamics 365 Sales

Capsule Parties of type person map to Dynamics 365 Contact records. We resolve the Party's linked Organisation (if any) and set the parentaccountid lookup to the corresponding Account record created from the linked Capsule Organisation. Email, phone, address, job title, owner (mapped by email to the Dynamics 365 User), and all custom field values cast from Capsule's field definitions migrate directly. Tags on the Party are stored in a custom multiselect field or written to a related Tag entity as a migration design decision confirmed during scoping.

Capsule Parties of type organisation map to Dynamics 365 Account records. The organisation name becomes the Account Name, and any registered address fields map to address composites. Industries and custom fields (fetched from the /fields/definitions endpoint for the parties entity) cast to their correct target field types before insert. Accounts are created before Contacts so that parentaccountid can be resolved at Contact insert time, avoiding orphaned Contact records.

Capsule Opportunities map to Dynamics 365 Opportunity records. Pipeline name and stage name from Capsule map to a Microsoft Dynamics 365 Sales Process and stage value; if the destination org uses multiple sales processes, we configure a Record Type per Capsule pipeline before migration. Probability percentage, expected close date, estimated value, currency, and owner migrate directly. The linked Party (as organisation or contact) is resolved to its Account or Contact reference for the regardingobjectid lookup.

Capsule Cases migrate to Dynamics 365 Case records. Status maps to Case Status, priority to Priority, assignee (owner) to OwnerId resolved by email match to the Dynamics 365 User table, and description to Description. If the destination org includes Dynamics 365 Customer Service, Cases land in the Customer Service app with a Case Title reconstructed from the Capsule case subject. Custom case fields require field-definition resolution from Capsule's /fields/definitions endpoint for the cases entity before value casting.

Capsule Tasks migrate to Dynamics 365 Task records. Due date, priority, status, subject, and description preserve. Owner resolves by email match to Dynamics 365 User. Tasks linked to a Party or Opportunity carry the regardingobjectid set to the migrated Contact, Account, or Opportunity. Tasks without a linked Party or Opportunity are migrated as standalone Tasks with no regardingobjectid, which is valid in Dynamics 365.

Capsule Activities by type map to Dynamics 365 equivalents: emails to EmailMessage records linked to a Task; calls to Task with TaskSubtype = Call and CallDurationInSeconds in a custom field; meetings to Task with TaskSubtype = Meeting and location preserved; notes to Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. All activity timestamps and owner assignments preserve. This migration uses the Dataverse API in batch mode with parent-record lookup resolution.

Capsule Projects (available on Starter and above) have no native Dynamics 365 equivalent. We offer two options during scoping: create a custom Project table in Dataverse (available from Professional tier) with a lookup from Opportunity and Task, or flatten Project milestones into Tasks with a custom projectmilestone flag field on the Task entity. The customer selects the approach before migration begins. If the destination Dynamics 365 edition does not support custom tables, we default to milestone-as-Task and document it in the handoff.

Capsule Users referenced as owners on Parties, Opportunities, Cases, and Tasks are resolved by email match against the Dynamics 365 User table. Any Capsule User without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record migration resumes. Inactive Capsule users are mapped to inactive Dynamics 365 Users with the same handling.