Migrate from Oncourse CRM to HubSpot

Oncourse contacts migrate as HubSpot contacts. The primary company link (Oncourse's associated company per contact) becomes a HubSpot company association via the contact's company_id field. Oncourse contact status maps to HubSpot lifecyle_stage, or the contact lands with lifecycle_stage set to 'lead' if no status field exists in the source.

Oncourse companies map to HubSpot companies. Domain, industry, employee count, and address fields translate directly to HubSpot company properties. Industry pick-list values are mapped using a value table; any Oncourse industry not in HubSpot's default list is saved as a custom property for manual cleanup. HubSpot auto-links contacts with matching email domains when the company creation option is enabled during import.

Oncourse deals migrate as HubSpot deals. The deal's associated pipeline in Oncourse becomes a HubSpot pipeline with stages mapped value-by-value. Deal amount, close date, owner, and stage status translate directly. HubSpot deal properties include pipeline, dealstage, closedate, amount, and hubspot_owner_id (resolved by email).

Oncourse pipelines require creation in HubSpot before the migration runs. Each Oncourse pipeline stage name maps to a HubSpot dealstage within the target pipeline. Stage probability values from Oncourse are translated into HubSpot's stage probability setting per stage, and forecast category is assigned based on stage position (e.g. Closed Won maps to Closed Won).

Oncourse users are matched to HubSpot users by email address. Users who exist in Oncourse but have no corresponding HubSpot account are flagged before migration. You can choose to assign their records to a fallback owner or invite them to HubSpot before the cutover run.

Oncourse task records categorized as calls, emails, or meetings migrate as HubSpot engagements with the original timestamp and body content preserved. Oncourse task subject maps to the engagement title; task body maps to the engagement notes. Owner attribution is preserved by email match.

Oncourse notes attached to contacts or deals become HubSpot notes or engagement notes. The note body and create timestamp are preserved. If the note contains rich text, we extract the plain text content and flag any formatting that cannot be rendered in HubSpot's note editor.

Oncourse file attachments linked to contacts, companies, or deals are downloaded from the source and re-uploaded to HubSpot Files. Files are associated to the corresponding HubSpot record after upload. HubSpot's 115MB file size limit applies; files exceeding this are flagged for splitting before migration.

Oncourse custom fields defined on the contact object require corresponding HubSpot custom properties created in HubSpot Settings before import. We generate a setup checklist naming each custom field with its Oncourse data type so your HubSpot admin creates the matching property with the correct type (text, number, date, dropdown, etc.).

Oncourse custom fields on deals migrate as HubSpot deal custom properties. Value-mapping applies for pick-list fields where the Oncourse pick-list values need to be recreated as HubSpot option labels; multi-select pick-lists map to HubSpot's checkbox or multi-checkbox property type. Numeric, currency, and date fields translate directly using the corresponding HubSpot property types, preserving format and precision. We include the full value-mapping table, property type recommendations, and any validation rules in the migration plan.

If Oncourse tracks lead status as a separate field from the deal pipeline, we map those status values to HubSpot lifecycle_stage labels (e.g. 'New' → 'lead', 'Qualified' → 'SQL'). The original Oncourse status value is also preserved in a custom property called Oncourse_Legacy_Status__c for reference.

Oncourse workflows, automations, and task-trigger rules do not migrate. They live in Oncourse's workflow engine and cannot be exported in a form that HubSpot can interpret. We export your Oncourse workflow definitions as a structured reference document so your HubSpot admin can rebuild them using HubSpot workflows and sequences.