Migrate from Oncourse CRM to Twenty CRM

Oncourse CRM Leads are distinct source-stage records with lead source and status properties. We migrate them 1:1 to Twenty's Person object, preserving the lead source as a custom field on Person and the lead status as a custom picklist field. If the customer uses Twenty's optional CRM extension (opportunity-based selling), we flag whether the Lead should instead land as a Company-less Person pending qualification.

Oncourse CRM Contacts carry name, email, phone, and address fields that map directly to Twenty's Person standard fields. We apply duplicate detection by email during import. The original Oncourse CRM contact ID is preserved in a custom field for audit traceability.

Oncourse CRM stores organization names as a Contact property rather than a distinct Account object. We extract every distinct organization value from the Contact export, deduplicate, create a Company record in Twenty for each unique organization, and link the Contact (now Person) to the corresponding Company via Twenty's Person-Company relation field. This is the primary schema transformation step and must complete before Person import to satisfy the foreign-key relationship.

Oncourse CRM Deals carry a name, monetary value, stage, and optional owner assignment. We map them directly to Twenty's Opportunity object, preserving the deal name as Opportunity name, monetary value as amount, and stage name as the Opportunity stage. Owner assignment migrates by resolving Oncourse CRM owner email to a provisioned Twenty User record. If the deal references a Contact without an extracted Company, we create a placeholder Company or attach the Opportunity to a Person directly depending on Twenty's current relation model.

Oncourse CRM pipelines are customizable per account with varying stage names. We extract the customer's active stage names from the Oncourse CRM export, create corresponding Opportunity stages in Twenty's Data Model, and map each Deal's stage to its Twenty equivalent. Probability percentages from Oncourse CRM (if available in the export) map to stage probability in Twenty. We flag any Oncourse CRM stages that have no clear Twenty equivalent for customer confirmation before import.

Oncourse CRM associates actionable tasks with Deals. We migrate task records as standalone Task objects in Twenty, linking each to the corresponding migrated Opportunity via Twenty's OpportunitiesTasks relation. Task status, priority, due date, and description migrate directly. Task assignment resolves Oncourse CRM owner email to Twenty User ID.

Oncourse CRM stores activity history as notes rather than structured activity records (calls, emails, meetings as separate objects). We migrate Oncourse CRM notes as Twenty Note records, linking them via ContentDocumentLink to the parent Person, Company, or Opportunity depending on what entity the note was associated with in Oncourse CRM. Note body migrates as plain text. We flag any notes with attachment references for customer awareness that file attachments cannot migrate.

Oncourse CRM custom fields on Contacts are exposed via the onCourse DSL export. We map them to equivalent custom properties in Twenty, applying the correct data type (text, number, date, checkbox, picklist). Type mapping follows: Oncourse CRM text becomes Twenty text, number becomes number, date becomes date, checkbox becomes boolean, and picklist becomes select. Custom fields must exist in Twenty before CSV import; we pre-create them via the Twenty Data Model API.

Oncourse CRM custom fields on Leads migrate to Twenty Person custom fields of the same type. If the customer's Twenty workspace uses a separate CRM extension for Lead tracking, we align field creation to the appropriate object. Any Oncourse CRM lead-specific fields (lead score, qualification status) that have no direct Twenty equivalent are flagged for customer decision during scoping.

Oncourse CRM custom fields on Deals map to Twenty Opportunity custom fields. We preserve field type during transformation and pre-create fields in Twenty's Data Model before the Opportunity import phase. Deal-level custom properties (closed-lost reason, expected close date, renewal flag) are mapped with customer confirmation on the target field name in Twenty.

Oncourse CRM owner assignments on Deals and Contacts are resolved by email match against Twenty User records. We extract every distinct owner email referenced in the Oncourse CRM export and check for a matching User in the destination. Any Oncourse CRM owner without a Twenty User match enters a reconciliation queue for the customer to provision before record import resumes, as Twenty's documentation explicitly requires users to exist before owner lookups can be mapped.

If Oncourse CRM exposes any custom object types beyond Leads, Contacts, Deals, and Tasks via its DSL export, we map them to Twenty Custom Objects using the /metadata API. We pre-create the custom object schema in Twenty (DataSource, Object, Field metadata tables) before importing any records. Custom object records with lookup relationships to standard objects (Person, Company, Opportunity) must import after those standard objects exist to satisfy foreign-key constraints.