Migrate from OnePageCRM to Twenty CRM

OnePageCRM Contacts map to Twenty Person records. The Contact's name, emails, phones, addresses, social URLs, and Next Action date all transfer directly. Next Action text becomes a Task title with the Next Action date as the task due date, linked to the Person. Custom contact fields from OnePageCRM must be pre-created in Twenty's Data Model before import; we provide the checklist during scoping. Tags on the contact migrate as labels on the Person record.

OnePageCRM Organizations map to Twenty Company records. The export includes company name, phone, address, industry, website, and custom company fields. We preserve the contact-to-organization linkage by matching Organization name during Company import, then resolving the Person-to-Company link during Person import using a company lookup field. Custom company fields must exist in Twenty before import.

OnePageCRM Deals map to Twenty Opportunity records. Deal name, amount, stage, close date, and pipeline assignment transfer directly. The OnePageCRM dealstage maps to Twenty's Opportunity stage values. Multi-month deal flags and margin/commission/cost fields migrate as custom Opportunity fields if they exist in the destination schema. Closed Won and Closed Lost deals migrate as historical records with the original stage preserved.

OnePageCRM Status taxonomy (Prospect, Qualified, Customer, etc.) maps to Twenty Opportunity stage values. We configure the destination stage values in Twenty Settings → Data Model before import and document the mapping in the runbook. Statuses that have no Twenty equivalent are created as custom stage values.

OnePageCRM Lead Source (website inquiry, phone call, referral, etc.) migrates as a custom picklist field on the Person object in Twenty. We create the field during schema pre-creation if it does not already exist, and map each distinct OnePageCRM Lead Source value to a Twenty picklist option.

OnePageCRM Tags assigned to Contacts and Deals migrate as labels in Twenty. Tags are stored as a flat namespace; we create the label associations during import by matching the tag name against the pre-provisioned label list. Tags on Deals migrate as labels on the linked Opportunity.

OnePageCRM Predefined Actions are template task sequences users assign to contacts. We map these to Twenty's task records, creating task templates from the Predefined Action name and step list. The template tasks are created as draft tasks attached to the Person record. Active workflow assignments (Autoflow) do not migrate; we document each Autoflow in the automation inventory for rebuild.

OnePageCRM Predefined Items (products and services used in deal creation) map to Twenty Product records. We preserve name, price, quantity, grouping, and Standard Price Book entries. Product groupings map to Twenty's product family or a custom picklist field. Line items on Deals migrate as OpportunityLineItems with Pricebook2 reference resolved at migration time.

OnePageCRM Notes and Call Logs attached to contacts migrate to Twenty Note records linked via content document to the Person. Call disposition and duration migrate as custom fields on the Note record. Note body text migrates as rich text. Email body content cannot be exported from OnePageCRM natively; we attempt partial extraction via API rate-limited reads but document which records have incomplete conversation history.

Admin-created custom fields for contacts, companies, and deals must be pre-created in Twenty Settings → Data Model before any import. We provide a custom field checklist during scoping that covers every source field, its data type, and the recommended Twenty field type. Multi-select picklists in OnePageCRM map to multi-select picklists in Twenty. Unsupported field types (e.g., rich-text areas exceeding character limits) are flagged and resolved during schema review.

OnePageCRM Owners map to Twenty WorkspaceMembers by email address match. We extract every distinct Owner referenced on Contact, Organization, and Deal records and match against the Twenty workspace user list. Any OnePageCRM Owner without a matching Twenty user goes to a reconciliation queue; the customer provisions the missing workspace member before record import resumes because OwnerId references are required on Person and Opportunity imports.