Migrate from Oncourse CRM to Salesforce Sales Cloud

Oncourse CRM Lead records map directly to Salesforce Lead. The Lead Source property maps to LeadSource and the Oncourse status property maps to Status. We preserve any custom fields from the Oncourse DSL export as typed Salesforce fields. Lead creation in Oncourse CRM is the entry point for unqualified prospects, and we hold the 1:1 mapping unless the customer's sales process involves immediate qualification into Contacts, in which case a pre-migration qualification pass is applied.

Oncourse CRM Contacts with an organization name stored as a Contact property are split into two operations during migration. First, we extract distinct organization names and create Salesforce Account records. Second, we insert Contacts with AccountId resolved via the Account lookup. Contacts without an organization value insert as standalone Contacts with no Account link. The original organization value is preserved in a custom field onc_original_organization__c for reference.

Oncourse CRM Deals map to Salesforce Opportunity. The Deal name maps to Opportunity.Name, value maps to Amount, stage maps to StageName, and owner maps to OwnerId via User email resolution. We extract the pipeline stage configuration during scoping and create corresponding Salesforce Opportunity Stages before migration. Deal properties that have no direct Salesforce equivalent are migrated as custom Opportunity fields.

Oncourse CRM pipeline stages are account-specific and customizable. We extract the customer's active stage names during scoping, create matching StageName values in Salesforce, and assign probability percentages. Stage ordering is preserved. If the customer uses multiple Oncourse pipelines, we create Salesforce Record Types on Opportunity to separate pipeline contexts.

Oncourse CRM Tasks associated with Deals migrate to Salesforce Task records. The WhatId on Task points to the migrated Opportunity. Task Status, Priority, and ActivityDate are preserved. Task assignment migrates by resolving the Oncourse owner reference to the Salesforce User via email lookup.

Oncourse CRM stores activity history as notes rather than structured engagement records. We migrate Oncourse notes as Salesforce Note objects. The Note Body preserves the full text. We link the Note to the appropriate parent record (Lead, Contact, Account, or Opportunity) via ContentDocumentLink using the resolved record IDs from migration. The note creation timestamp becomes the Salesforce Note CreatedDate for timeline ordering.

Oncourse CRM custom fields on Contacts are exposed via the DSL export and migrate as custom fields on the Salesforce Contact object. We apply Salesforce field type mapping (text to Text, number to Number, date to Date, checkbox to Checkbox) and create fields with __c suffix. The customer reviews field names during scoping to avoid naming conflicts with existing Salesforce fields.

Oncourse CRM custom fields on Deals migrate as custom fields on the Salesforce Opportunity object. Custom Deal fields that represent product line, deal source, or renewal type map to custom Opportunity fields of appropriate Salesforce data type. If the custom field is a picklist in Oncourse CRM, we create a corresponding Salesforce picklist with the same allowed values.

Oncourse CRM custom fields on Leads migrate as custom fields on the Salesforce Lead object using __c suffix naming. These are created in the destination org before Lead migration begins to satisfy field existence requirements during insert.

Oncourse CRM owner references on Contacts, Leads, Deals, and Tasks resolve by email match against the destination Salesforce User table. Any owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before the corresponding records load. Migration does not proceed past Owner-dependent objects until the queue is resolved.

Oncourse CRM does not expose a public file attachment export via its standard import/export tooling. Attachments cannot be migrated in automated runs. We recommend a manual export of the Oncourse CRM document store before cutover and a separate file migration using Salesforce Data Loader or the ContentWorkspace API post-migration if the customer requires structured document storage.

Oncourse CRM drip sequences are sales engagement cadences with built-in email steps and delays. These do not migrate to Salesforce. We deliver a written inventory of every active Oncourse CRM drip sequence with its step order, delay intervals, email templates, and a recommended replacement in Salesforce Sales Engagement (High Velocity Sales), Outreach, or Salesloft. The customer's RevOps team rebuilds sequences in their chosen engagement tool.