Migrate from Oncourse CRM to Freshsales

Oncourse CRM Leads migrate 1:1 to Freshsales Leads, preserving the lead source and status properties as standard Lead fields. Any Oncourse custom fields on Leads map to Freshsales custom Lead fields. We recommend configuring Freshsales Lead field mapping before migration to ensure that custom field data does not fall during Lead conversion; the customer should define the target Contact, Account, and Deal fields for each Lead custom field in Freshsales Admin settings before the migration runs.

Oncourse CRM Contacts migrate 1:1 to Freshsales Contacts, mapping name, email, phone, and address fields directly. The organization value stored as a Contact property in Oncourse is extracted and held for the Account creation step; after Freshsales Accounts are created, we update each Contact's AccountId lookup to restore the organization relationship. Duplicate detection applies at import to prevent duplicate Contacts for records sharing the same email address.

Oncourse CRM does not maintain a separate Account object; organization names are stored as Contact properties. We extract all distinct non-null organization values from Oncourse Contacts, create corresponding Freshsales Accounts, and link each Contact to its Account via the Contact.account_id field. This reconstruction is the most impactful schema step in the migration because it enables account-level reporting, territory assignment, and the Contact hierarchy that Oncourse's flat model does not support.

Oncourse CRM Deals migrate 1:1 to Freshsales Opportunities. Deal name, monetary value, and owner assignment transfer directly. The Oncourse pipeline stage name maps to Freshsales Opportunity stage; if the stage name does not match a Freshsales standard stage, we create a custom stage value in Freshsales before migration. Closed-won and closed-lost status from Oncourse maps to Freshsales stage with the appropriate probability percentage preserved in a custom field for reporting.

Oncourse CRM pipeline stages are customizable and vary per account. We extract the customer's active stage names during scoping and map them to Freshsales Opportunity stages, creating new stages in Freshsales if the names do not match the standard set (Prospect, Qualification, Proposal, Negotiation, Closed Won, Closed Lost). Probability percentages from Oncourse migrate as custom numeric fields on the Opportunity if the customer requires stage probability reporting that differs from Freshsales defaults.

Oncourse CRM stores activity history as freeform notes rather than structured Task, Event, or EmailMessage records. We import these as Freshsales Notes linked via ContentDocumentLink to the parent record (Contact, Lead, Account, or Opportunity). Because the original activity type (call, email, meeting) is not structurally differentiated in Oncourse, we add a custom field note_type__c on each migrated Note to carry any inferred type or a default value of 'General' so admins can later filter or reclassify. This is a data-shape limitation rather than a data-loss issue; the note content migrates fully.

Oncourse CRM Tasks associated with Deals migrate as standalone Freshsales Task records linked to the corresponding Opportunity via the Task.what_id field. Task subject, status, due date, and owner assignment transfer directly. Tasks not associated with a Deal link to the parent Contact or Account based on the context in which they were created in Oncourse.

Oncourse CRM custom fields on Contacts, Leads, and Deals are exposed via the onCourse DSL export. We map them to Freshsales custom properties using type equivalence: text to string, number to number, date to date, checkbox to boolean. The customer must pre-create the corresponding custom fields in Freshsales Admin settings before migration; we document the required field names, types, and object assignments in the scoping deliverable. Custom fields that cannot be typed-equivalently (e.g., multi-select from Oncourse to Freshsales picklist) are flagged during scoping.