Migrate from Basic Online CRM to Twenty CRM

Basic Online CRM Contacts map directly to Twenty People records. We preserve name, email, phone, and address fields 1:1. Any non-standard fields land as custom properties in Twenty. We validate email format during transform and flag any malformed addresses for customer review before import. The Twenty People object is created before any Opportunity import so that the Opportunity-to-Person relation is satisfied at the moment of insert.

Basic Online CRM Companies map to Twenty Company records. Companies are a flat list without subsidiaries or hierarchies in Basic Online CRM, and Twenty stores companies as a standard object with no required hierarchy. We import by name match and flag duplicates where the same company name appears multiple times in the source export. The Company record is created before People records that reference it via a domain lookup.

Basic Online CRM Deals map to Twenty Opportunities. The critical difference is that Basic Online CRM exports Deal-to-Contact associations by internal numeric ID, not by name or email. We request a dual export of Contacts and Deals, cross-reference the internal IDs against the contact list during the mapping phase, and recreate the Opportunity-to-Person association in Twenty by matching Contact name. If a Deal references a deleted Contact, we flag it as an orphaned Opportunity for customer resolution before import.

Basic Online CRM pipeline stages are simple text labels exported as strings. We map each stage to a Twenty Opportunity Stage with a matching label. If the customer has configured custom stage names in Basic Online CRM, we preserve those labels verbatim in Twenty so that historical pipeline reports remain readable after migration.

Basic Online CRM custom fields exist but are not typed (all stored as plain strings regardless of intended type). We migrate them as-is to Twenty, creating fields of the appropriate type in Twenty's Data Model before import. Date fields are the highest-risk type: Basic Online CRM exports may show as 'Jan 15 2024' in one export and '15/01/2024' in another. We standardize date formats during transform using ISO 8601 and ask customers to validate custom field mappings before final import.

Basic Online CRM Notes are free-text and untyped. We migrate them as plain-text Note records in Twenty, linked via the standard relation to the parent People or Company record. Note timestamps are not always explicitly set in Basic Online CRM; we preserve whatever timestamp is available and flag any notes with missing timestamps for customer review.

If the Basic Online CRM instance has task records, they are simple title-and-status items with no due-date enforcement and no assignee fields surfaced in exports. We migrate them as Twenty Task records with Status, Priority, and ActivityDate preserved where available. The absence of assignee fields in the source export means we ask customers upfront which team member should own migrated tasks and apply bulk owner assignment during the write-back phase.

Basic Online CRM has a basic user concept but does not surface record-level owner assignment in its exports. We extract the distinct user list from the source and ask customers to specify the corresponding Twenty workspace member for each. We then apply bulk owner assignment during the write-back phase. If a Basic Online CRM user has no corresponding Twenty account, we flag them for the customer to provision before migration proceeds past the owner resolution step.

Basic Online CRM does not host or store file attachments natively. We flag that any documents referenced in Notes or Deal descriptions will not migrate and must be re-uploaded manually. We include a pre-migration checklist item asking customers to identify and inventory any such file references so they can be located and re-attached post-migration in Twenty.

Basic Online CRM's pipeline configuration (stage order, stage labels, probability values if set) migrates as a Twenty Opportunity pipeline. We extract pipeline metadata from the source's pipeline settings export and configure the matching pipeline in Twenty before any Opportunity records are written. The pipeline must exist in Twenty before Opportunities can be assigned to it.

Basic Online CRM does not have a first-class Activity object separate from Notes and Tasks, but if the instance contains email log entries or meeting records in the Notes field, we extract them as standalone Task records in Twenty with the activity type indicated in a custom field. The original timestamp is preserved as ActivityDate.