Migrate from Crust CRM to Microsoft Dynamics 365 Sales

Crust CRM Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (full name, email, phone, address) map to the corresponding Dynamics Contact attributes using the OData field names. The Crust CRM created_date and lastmodified_date migrate as CreatedOn and ModifiedOn on Contact to preserve the original record timestamps. We deduplicate by email match against existing Dynamics Contacts before insert.

Crust CRM Company records map to Microsoft Dynamics 365 Sales Account. The Company name becomes Account Name; the domain or website field maps to Website. Account is created before Contact import so that the Parent Account lookup and the primary contact relationship are satisfied at the moment of Contact insert. We run deduplication against existing Accounts by name and domain before loading.

Crust CRM Deal records map to Microsoft Dynamics 365 Sales Opportunity. The deal amount maps to EstimatedRevenue; close date maps to EstimatedCloseDate; owner maps to OwnerId resolved by email match. The Crust CRM deal stage name translates via a stage-mapping table that we configure during discovery, creating the corresponding stage values in the Dynamics Sales Process.

Where Crust CRM maintains a distinct Lead object separate from Contact, we migrate Lead records to Microsoft Dynamics 365 Sales Lead. Lead_Status from Crust CRM maps to Dynamics LeadStatus with a custom field crust_lead_status__c preserving the original value. If Crust CRM treats Leads as Contacts with a lifecycle flag, we migrate them as Dynamics Contacts with a custom lifecycle stage field instead.

Each Crust CRM pipeline becomes a Microsoft Dynamics 365 Sales Process (a stage whitelist per business process). We collect the full pipeline-stage map during discovery, configure the Sales Process in Dynamics with matching stage names and probabilities, and attach it to the Opportunity Record Type. This ensures Deal records land in the correct stage after migration.

Crust CRM call engagements map to Dynamics 365 PhoneCall activity records. Call duration, disposition, and the related contact or deal reference migrate to the corresponding PhoneCall attributes. The PhoneCall's Regarding lookup points to the resolved Contact or Opportunity. Activity timestamps from Crust CRM set the ActualStart and ActualEnd on the PhoneCall.

Crust CRM email engagements map to Dynamics 365 Email activity records. Email subject, body, from, and to addresses migrate to the Email attributes. The Email's Regarding lookup links to the Contact or Opportunity. We preserve the original sent timestamp as the ActualStart on the Email record.

Crust CRM meeting engagements map to Dynamics 365 Appointment records. Start time, end time, location, and attendee list migrate to the corresponding Appointment attributes. Attendees map to the ActivityParty table linked to the Appointment. The Regarding lookup points to the related Contact or Opportunity.

Crust CRM notes migrate to Dynamics 365 Annotation records. Note body, author, and created timestamp migrate. The Annotation's ObjectId lookup points to the related Contact, Account, or Opportunity. We preserve the Crust CRM note's created_date as the CreatedOn timestamp on the Annotation.

Crust CRM's configurable module architecture means every organization may carry custom modules with custom fields not present in a standard install. We run a pre-migration schema audit to enumerate every custom module, its field types, and dependencies. Each custom module maps to a corresponding Dynamics custom entity built on Dataverse, with fields typed according to Dynamics conventions (text fields become nvarchar, numbers become integer or decimal, dates become datetime). Lookup relationships between custom modules and standard objects are preserved as Dataverse lookups.

Crust CRM Owner records map to Microsoft Dynamics 365 Sales SystemUser by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Activity record and resolve against the destination org's SystemUser table. Owners without a matching Dynamics user go to a reconciliation queue for the customer's admin to provision before record import proceeds.

Crust CRM record attachments migrate as Dynamics Annotation records with the file content stored as base64 in the Annotation's DocumentBody or linked via FileAttachment entities. We preserve the original filename, MIME type, and record association. Attachment migration is handled separately from the main record migration because file size and storage tier affect the import approach.