Migrate from Oncourse CRM to Microsoft Dynamics 365 Sales

Oncourse CRM treats Leads as a distinct source-stage record type separate from Contacts. We map Leads directly to Dynamics 365 Lead, preserving the lead source and status as standard properties (leadsource, statecode). Any Oncourse Lead-specific custom fields migrate to Lead custom fields in Dataverse with type mapping applied (text to single-line text, number to whole number or decimal, date to datetime). The Lead Status values are preserved as a custom field for reconciliation after migration.

Contacts migrate to Dynamics 365 Contact with a pre-created parent Account lookup. We extract the organization property from each Oncourse Contact during the transform phase, deduplicate the organization list, and resolve each Contact's AccountId from the Account mapping. Contacts without a populated organization property in Oncourse are flagged as standalone Contacts without a parent Account. Standard fields (fullname, emailaddress1, telephone1, address) map directly to Dynamics field names.

Oncourse CRM does not expose a distinct Account or Company object. The organization name is stored as a property on the Contact record. We extract every distinct non-null organization value from Contact records, deduplicate across the full Contact set, create Account records in Microsoft Dynamics 365 Sales , and use the resulting AccountId as the parent lookup on each Contact during Contact import. The Account name maps to the name field; the primary contact's email becomes the account's email address where available.

Oncourse Deals map directly to Dynamics 365 Opportunity. The deal name maps to the Opportunity name field, deal value maps to estimatedvalue, and the Oncourse pipeline stage maps to the stage name in the configured Dynamics Sales Process. The owner from Oncourse resolves to a Dynamics User via email match before Opportunity import. Closed-won and closed-lost statuses from Oncourse map to the corresponding Opportunity statecode in Dynamics.

Oncourse CRM pipelines are per-account and fully customizable. We extract the customer's active pipeline stage names and stage order from the source export, then configure corresponding Opportunity Sales Processes in Microsoft Dynamics 365 Sales before any Opportunity records load. Each stage receives a probability percentage mapped from the Oncourse stage weights. New stages are created in Dynamics if the customer's active stage names do not match any existing Sales Process values.

Oncourse CRM captures engagement history as timestamped free-form notes rather than structured Task, Event, or EmailMessage records. There is no type classification distinguishing calls, emails, or meetings in Oncourse's standard export. We migrate the full note body and timestamp as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. We preserve the original Oncourse note creation timestamp in a custom field original_created_date__c for audit continuity. Customers who require typed activity records (Task, Event) for reporting should budget for a post-migration data enrichment pass to classify migrated notes into the correct activity types.

Oncourse CRM associates actionable tasks with Deals. We migrate task records as standalone Dynamics 365 Task objects linked to the corresponding Opportunity via the regardingobjectid lookup. Task subject, status (open, completed), priority, and due date map directly. Task assignment resolves the Oncourse owner to a Dynamics User via email match before Task import. Completed task dates are preserved as ActivityDate.

Custom fields on Contacts, Leads, and Deals are exposed via the Oncourse DSL export. We map each custom field to an equivalent Dataverse custom column, applying the correct data type mapping: text to single-line or multi-line text, number to whole number or decimal, date to datetime, checkbox to two options. Unsupported field types (e.g., Oncourse-specific structured objects with no Dataverse equivalent) are flagged during scoping for customer decision on whether to drop, flatten, or store as JSON in a text field.