Migrate from Composity CRM to Microsoft Dynamics 365 Sales

Composity Accounts map directly to Dynamics 365 Account. We extract the full Account export from Composity's Account & Contact Management module, map standard fields (name, address, industry, status) 1:1, and handle Composity's address structure by flattening any type-flagged address into separate address-line fields. Custom fields from Composity's Custom Data module that are applied to Account map to typed Dataverse columns created before import.

Composity Contacts map to Dynamics 365 Contact with the parent Account resolved via account name or domain matching. We preserve the Account-Contact relationship by inserting Accounts first and then Contacts with the parentcustomerid_value lookup populated from the matched Account. Custom contact fields from Composity's Custom Data module map to corresponding Dataverse columns on Contact.

Composity Leads from the Campaign & Lead Management module map to Dynamics 365 Lead. Lead status, source, and qualification data transfer to the corresponding Dynamics 365 Lead fields. Any custom qualification properties defined in Composity's Custom Data module and applied to Leads become custom fields on the Dynamics 365 Lead entity.

Composity Opportunities and Quotes map to Dynamics 365 Opportunity. Deal name, estimated value, stage, and expected close date transfer directly. Composity's user-defined pipeline stages are exported as a stage definition list and recreated as StageName values in a Sales Process that we configure at the destination before migration. Closed-won and closed-lost reasons from Composity map to custom fields on Opportunity.

Composity's custom pipeline stages (name, order, win/loss flags) are exported and recreated in Dynamics 365 as a Sales Process with corresponding stage values and probability percentages. We configure the stage probabilities to match Composity's original values and map them to a Sales Process assigned to the Opportunity Record Type.

Composity Sales module Invoices map to Dynamics 365 Invoice. Invoice headers and line items transfer directly; partially paid invoices require balance carry-forward handled as a note on the migrated Invoice record. Note that Microsoft Dynamics 365 Sales does not include full financial management; if the customer needs invoice aging and payment reconciliation, they should license Dynamics 365 Business Central in addition to Sales.

Composity Product catalog entries (name, SKU, price, description) map to Dynamics 365 Product2 records. Standard Price Book entries are created during migration. Product-to-quote and product-to-invoice associations are preserved through the Opportunity Product relationships at the destination.

Composity's Production module stores manufacturing or job data with BOM references and production order records. Microsoft Dynamics 365 Sales has no native production object. We map production records to a custom Dataverse entity with BOM data stored as JSON or as related custom records, or to the Project entity if the customer licenses Dynamics 365 Project Operations. This requires explicit schema design during scoping and is not a standard field-to-field migration.

Composity's Projects module (Growth and above) maps to Dynamics 365 Project if Project Operations is licensed, or to a custom entity in Dataverse. Project name, status, dates, and assigned resources transfer; custom project fields and milestone definitions require explicit field mapping during scoping. The customer chooses the target structure during discovery.

Composity Inventory module records (SKU, quantity, warehouse location, reorder levels) map to Dynamics 365 Product2 with custom fields for quantity on hand, warehouse reference, and reorder level. Quantity discrepancies or negative stock values present in Composity are flagged in a pre-migration data quality report for the customer to resolve before import.

Composity Document Storage exports files one at a time with no bulk download. We build a file inventory during discovery, download files in parallel where possible, and reattach to the correct Dynamics 365 Account, Contact, or Opportunity records using filename or metadata matching. Files attach to SharePoint document libraries linked to the parent entity or to Dataverse file columns depending on the customer's licensing.

Composity activity records (calls, emails, meetings, notes) logged against Contacts and Accounts map to Dynamics 365 Task, EmailMessage, Event, and Note. Activity type, date, description, and linked record are preserved. Activity history export depends on Composity's built-in export availability for the Activities module; if not exportable, activity data migrates as Note records attached to the parent Contact or Account.