Migrate from Onpipeline to Twenty CRM

Onpipeline Contacts map directly to Twenty Person records. Standard fields (name, email, phone, address) migrate 1:1. Tags and Lifecycle Stage migrate as custom fields or labels on the Person record. Phone numbers use Twenty's phone field type with configurable default country code. If the customer's Onpipeline contacts span multiple roles at the same company, each Contact becomes a separate Person; the Company-to-Company linkage is resolved separately.

Onpipeline Company records map to Twenty Company records. Company name, domain, address, and industry fields migrate 1:1. The Person-to-Company linkage migrates as a Twenty workspaceRelation record, preserving the many-to-many relationship where multiple People can be associated with one Company.

Onpipeline Deals are the central object and map to Twenty Opportunities. Deal name, value, expected close date, and stage assignment migrate. The Deal-to-Contact (and optional Deal-to-Company) association migrates by linking the Opportunity to the corresponding Person and Company records in Twenty. Closed-won and closed-lost reason fields from Onpipeline custom fields become Opportunity custom fields in Twenty.

Onpipeline custom stage names and probabilities per pipeline are captured during scoping. Each stage becomes a Twenty Opportunity stage value with its probability percentage mapped to the stage. We configure the stage order in Twenty's Data Model to match Onpipeline's pipeline flow before Opportunities are imported.

Onpipeline Products (name, SKU, price, stock quantity) map to a Twenty custom object named Product if the customer uses product catalog features. We pre-create the custom object schema with name, sku, price, and stock fields before import. If Twenty adds a native product catalog in a future release, the custom object can be deprecated and data migrated to the standard object.

Onpipeline Events (calendar appointments with datetime, duration, assigned user, description) migrate as Timeline entries on the related Person or Opportunity record in Twenty. We preserve the event title, start and end datetime, assigned user, and body text. The calendar-to-user assignment is resolved by matching Onpipeline user email to the Twenty workspace member.

Onpipeline Tasks (title, due date, assigned user, status) migrate as Timeline entries in Twenty. Task status (open, completed) maps to a completion flag on the Timeline entry. We preserve the original due date and assignment by resolving the Onpipeline owner to the Twenty workspace member.

Onpipeline Notes attached to Deals or Contacts migrate as Timeline entries in Twenty with the full note body preserved as rich text. Notes attached to files migrate the file reference; the actual file attachments are downloaded and re-uploaded to Twenty's file storage linked to the Timeline entry.

Onpipeline Quotes have no native Twenty equivalent. We document the customer's Quote schema (line items, pricing, e-signature status, linked Contact and Deal) and configure a Quote custom object in Twenty before migration. Quote line items become related QuoteLine custom object records linked to the Quote. E-signature status is stored as a custom field; the signed PDF is attached as a file to the Quote record. If the customer uses a third-party e-signature tool (DocuSign, HelloSign), we note the integration for rebuild post-migration.

Onpipeline Invoices have no native Twenty equivalent. We configure an Invoice custom object with header fields (invoice number, date, payment status, total) and an InvoiceLine related object for line items. Payment status migrates as a select field. Recurring invoice configurations from Onpipeline Standard and Advanced plans are documented as InvoiceSchedule records in the custom object for manual rebuild; automated recurring invoice generation is not available in Twenty and requires a third-party tool or custom development.

Onpipeline Users are resolved by email against Twenty workspace members. We extract every distinct user referenced as a Deal owner or activity assignee and match against the Twenty workspace. Any Onpipeline user without a matching Twenty member goes to a reconciliation queue for the customer's admin to provision. Inactive Onpipeline users are migrated as inactive Twenty members with their historical assignments preserved.