Migrate from Dashcord to Microsoft Dynamics 365 Sales

Dashcord stores lead records as standard Salesforce Lead objects with additional custom fields for lifecycle stage and scoring. We read Lead records from the Salesforce host org via REST API, enumerate all Dashcord-specific custom fields during pre-flight schema introspection, and map each to a typed Microsoft Dynamics 365 Sales Lead attribute or a custom field created during destination schema setup. The Salesforce Lead ID is preserved as a reference field for audit trails. Owner resolution by email match against the Microsoft Dynamics 365 Sales User table happens before insert.

Contacts are the primary audience records in Dashcord's model. We export all Contact fields including Dashcord-specific custom contact properties. Standard field mapping (Name, Email, Phone, Title, Account) applies; custom Dashcord fields are enumerated during pre-flight and mapped to typed Microsoft Dynamics 365 Sales contact attributes or custom fields. The AccountId lookup resolves at migration time after Account creation.

Dashcord uses Salesforce Accounts to represent company and organization records. We export Account fields including billing address, industry, and any custom fields. Relationships to Contacts and Opportunities are preserved via the AccountId reference. Account is created before Contact import so the parent lookup is satisfied at the moment of Contact insert.

Dashcord wraps Salesforce Campaigns for marketing automation and campaign analytics. We export Campaigns and map them to the Microsoft Dynamics 365 Sales Campaign entity. Campaign member status and response tracking values are enumerated from the Salesforce org's active picklist during pre-flight and normalized to the Microsoft Dynamics 365 Sales campaign member status picklist values.

Campaign Members link Contacts and Leads to Campaigns with status and timing data. We export all member records but status values differ between platforms. We normalize Campaign Member status to Microsoft Dynamics 365 Sales campaign member status values during the transform phase, flagging any unmapped source values for customer review.

Dashcord assigns lifecycle stage values (subscriber, lead, MQL, SQL, customer) stored as custom picklist or number fields on Lead and Contact records. We extract the raw lifecycle stage values and store them as a custom field (dashcord_lifecycle_stage__c) on Microsoft Dynamics 365 Sales Lead and Contact. There is no native lifecycle stage equivalent in Microsoft Dynamics 365 Sales ; the customer configures this as a custom option set and optionally enables Dynamics 365 AI Sales or Customer Insights Journeys for comparable automation.

Dashcord assigns numeric or tiered lead scores stored as custom fields on Lead records. We export the raw score values and the scoring model name or rule set reference if stored in a custom object. These migrate as custom fields on the Microsoft Dynamics 365 Sales Lead entity (dashcord_lead_score__c). Dynamics 365 AI Sales (Enterprise tier) provides predictive lead scoring as a native feature, which the customer can activate post-migration as a replacement.

Dashcord's event management module stores event records as custom Salesforce objects within the host org. Schema varies by Dashcord package version; we discover the active custom object's field definitions via Salesforce Tooling API during pre-flight. Events map to Microsoft Dynamics 365 Sales custom activities or a custom entity created in Dataverse. Customer admins define the target schema during scoping.

Dashcord tracks email sends, opens, and clicks via Salesforce Activity records. We preserve Tasks and Email standard objects linked to Contacts and Leads. Campaign attribution data is included to maintain marketing source context. Activity timestamps preserve the original engagement date for timeline ordering. Microsoft Dynamics 365 Sales stores activities against the Account, Contact, or Lead record.

Any custom fields added by Dashcord or created on top of the package are stored as Salesforce custom fields. We read field metadata via the Salesforce API, enumerate all custom properties on each object, and map them to typed Microsoft Dynamics 365 Sales attributes or custom fields. Picklist value sets are enumerated and recreated as option sets in Dynamics 365. Any unmapped custom properties are flagged in the pre-flight audit for customer review.