Migrate from Oncourse CRM to Pipedrive

Oncourse CRM Leads migrate 1:1 to Pipedrive Lead. The lead source and status properties map directly to Pipedrive's Lead standard fields. Lead labels and owner assignment are preserved. Pipedrive uses the same field structure for Leads as it does for Deals, so any custom fields on the Oncourse Lead object map to the Pipedrive Lead custom properties.

Oncourse CRM Contacts map to Pipedrive Person. Name, email, phone, and address fields migrate directly without transformation. The organization name stored as a Contact property is extracted in a pre-pass and held for Organization creation (see Organization mapping). Duplicate detection by email is applied during Pipedrive import.

Oncourse CRM does not have a distinct Account object; organization names live as a property on the Contact record. We extract all distinct organization values, deduplicate by normalized name, and create Pipedrive Organizations. The Person records are then linked to their parent Organization via the org_id lookup after Organization insert. Organizations without a contact association are still created to preserve reporting structure.

Oncourse CRM Deals migrate to Pipedrive Deals. Deal name, value, currency, expected close date, label, stage, and owner assignment map directly. Stage history from Oncourse CRM is not available as a structured object and cannot be reconstructed in Pipedrive; we flag this during scoping so the customer knows the stage transition timeline will begin fresh.

Oncourse CRM pipelines are customizable and vary per account. We extract the customer's active stage names during scoping, create the corresponding pipeline in Pipedrive with matching stage names, and map each Oncourse Deal's stage to the equivalent Pipedrive stage. If Pipedrive's stage count differs from Oncourse's, we map to the closest logical stage and document the delta for the customer's admin to confirm.

Oncourse CRM tasks associated with Deals migrate to Pipedrive Activities linked to the corresponding Deal. Task type (call, email, meeting, task), status, due date, and owner assignment are preserved. The activity detail maps to the Pipedrive Activity note field. Sub-task hierarchies in Oncourse CRM are flattened to individual Activity records with a note annotation identifying the parent task.

Oncourse CRM stores activity history as notes rather than structured activity records. We map these note entries to Pipedrive Note objects, linked to the parent Person, Organization, or Deal. The original timestamp is preserved as the Note creation date. This is a data-shape transformation rather than a direct field copy, and we flag it as a scoping item so the customer understands the Note will appear in Pipedrive's activity feed rather than as a structured Activity record.

Oncourse CRM exposes custom fields via its DSL export. We map each custom field to an equivalent Pipedrive custom field, applying the correct data type (text, number, date, checkbox, dropdown). Custom fields are pre-created in Pipedrive before migration using the Pipedrive API. If a Pipedrive field with the same name already exists, we map to it; otherwise we create and document it.

Oncourse CRM Owners are matched by email to existing Pipedrive User records in the destination account. We resolve owner_id on Deals, Leads, and Activities at migration time. Any Oncourse Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Oncourse CRM does not expose a public file attachment export via its standard import/export tooling. We cannot guarantee attachment migration in automated runs. We recommend a manual backup of the document library before migration and document the folder structure as a handoff for the customer's admin to re-associate files post-migration if needed.