Migrate from Cirrus CRM to Microsoft Dynamics 365 Sales

Cirrus CRM Contacts map to either Microsoft Microsoft Dynamics 365 Sales Lead or Contact depending on qualification status. Since Cirrus CRM does not have a separate Lead concept, all Contacts enter the migration as Leads by default unless the customer confirms qualification criteria. We ask for explicit criteria during scoping — typically deal association, stage progression, or last activity date — to identify which records should land as Leads versus Contacts. Any existing Contact with a Company association and at least one linked Deal converts to Contact tied to an Account. Original contact creation timestamp and last-modified date migrate as custom fields for audit.

Cirrus CRM Company records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The Company address, credit information, and geographic enrichment (latitude/longitude) map to Account address fields and any custom fields configured for enrichment data. Account is created before Contact import so that the ParentAccountID lookup is satisfied at Contact insert time. We use the Company name as the dedupe key and flag duplicates for the customer's admin to resolve before final import.

Cirrus CRM Deals map to Microsoft Microsoft Dynamics 365 Sales Opportunity. Deal monetary value maps to Amount, stage label maps to the Opportunity Stage name (we treat stage as a text label mapped to a configured Sales Process, not as an inherited pipeline definition from Cirrus CRM), and the Deal's linked Contact and Company resolve to the Opportunity's ContactId and AccountId respectively. Closed-Won and Closed-Lost reason fields migrate as custom Opportunity fields if the customer uses them in Cirrus CRM.

Cirrus CRM pipeline stage definitions live in the pipeline configuration, not the Deal record, and are not exported with deal data. We ask the customer to confirm the stage name and order for each Cirrus CRM pipeline during scoping. Each pipeline becomes a Microsoft Dynamics 365 Sales Record Type with a corresponding Sales Process that whitelists the stage values. Probability percentages from Cirrus CRM map to the Stage Probability field per stage name.

Cirrus CRM Quotes carry line items and product associations linked to Deal records. Quotes map to Microsoft Microsoft Dynamics 365 Sales Quote (available from Professional tier). The Quote-to-Deal association migrates as a custom lookup field Quote_DealReference__c pointing to the Opportunity, because Microsoft Dynamics 365 Sales Quote does not natively store a Deal reference. Product line items migrate as QuoteLineItem records with Product2, Quantity, and UnitPrice resolved at migration time.

Cirrus CRM Orders are generated from Quotes and carry ERP references via the bidirectional sync. Orders are the highest-dependency object in this migration because they reference Quotes, Deals, and potentially ERP invoice records. We migrate Orders in the last position of the data sequence, after Accounts, Contacts, Deals, and Quotes are confirmed in Microsoft Dynamics 365 Sales . The original ERP invoice reference migrates as a custom text field Order_ERPReference__c. If the destination includes Business Central, Order records should land in Business Central rather than Sales and we provide a cross-Dataverse mapping document for the customer's ERP admin.

Cirrus CRM Activities log calls, emails, meetings, and tasks tied to Contact or Deal records. We migrate each activity type to its nearest Microsoft Dynamics 365 Sales equivalent: calls to Task with TaskSubtype=Call, emails to EmailMessage linked to a Task, meetings to Event, and generic tasks to Task. The parent Contact or Deal resolves to WhoId and WhatId respectively. Activity timestamps are preserved as ActivityDate. We flag activities linked to orphaned records (Contacts or Deals that could not be resolved) for manual review.

Cirrus CRM tenants add custom fields to Contacts, Companies, and Deals with no universal schema export. We ask the customer to provide a field configuration screenshot or export before migration scoping. Each custom field is validated for type (text, number, date, picklist) in a test batch of 50 records before the full import. Picklist values require explicit mapping to Microsoft Dynamics 365 Sales global picklist values or a new custom picklist field in the destination org. Custom fields migrate after the standard field mapping is validated in a sandbox run.

Cirrus CRM Users referenced on Deals and Activities map to Microsoft Microsoft Dynamics 365 Sales User records resolved by email address. Any HubSpot Owner (Cirrus CRM uses Owner terminology) without a matching Dynamics 365 User is placed in a reconciliation queue. The customer's Dynamics 365 admin provisions missing Users before the production migration phase begins. Inactive Cirrus CRM Users map to inactive Dynamics 365 Users with a note in the manifest for the admin to activate or reassign records post-migration.