Migrate from Pipeliner CRM to Twenty CRM

Pipeliner Account records map directly to Twenty Company records. The Account name, domain, industry, employee count, address fields, and custom fields migrate as typed Company fields. The Account's industry and type properties map to Twenty's company industry and domainName fields. Company is the primary organizational record and must be inserted before any Person or Opportunity records that reference it.

Pipeliner Contact records map to Twenty Person records. The Contact's name, email, phone, job title, and custom fields migrate as Person fields. Each Person record receives a link to its parent Company (from the Account mapping) via Twenty's companyLinkName field. Email and phone are preserved as typed fields for use in Twenty's activity and task features.

Pipeliner Lead records represent pre-qualified prospects that may not yet have a Company association. Leads with a defined conversion status map to Twenty Person records; Leads that have an associated Opportunity in Pipeliner map to Twenty Person plus an Opportunity. The original Pipeliner lead status and source are preserved as custom fields on the migrated Person for audit and reporting.

Pipeliner Opportunity records map to Twenty Opportunity records. Stage, probability, close date, value (amount), and description migrate. Pipeline stage assignments in Pipeliner can vary per user; we collapse per-user overrides to the primary admin-defined pipeline stage set and preserve the original user-specific stage label as a custom field on the Opportunity. Company and Person links are resolved from the Account and Contact lookups completed earlier in the migration.

Pipeliner pipeline stages (which can differ per user) are normalized to the admin-defined canonical stage set. We map each Pipeliner stage name to a corresponding Twenty Opportunity stage, preserving probability weights where present. The customer defines the stage mapping during scoping based on the primary pipeline configuration.

Pipeliner Quotes linked to Accounts, Contacts, and Opportunities migrate as Twenty Opportunity records with line item details preserved in a custom format. Twenty does not ship a native Quotes object at all tiers, so we work with the customer to determine whether quotes migrate as Opportunity notes, a custom Quote object created in Twenty, or as PDF documents attached to the Opportunity. Line items from Pipeliner Quotes map to Twenty custom fields on the chosen target.

Pipeliner Products migrate to a Twenty custom object named Product with fields for name, SKU, unit price, and description. Products linked to Opportunities via the Product Grid migrate as relationship records linking the custom Product object to the Opportunity. The customer confirms the target custom object name and field structure during scoping.

Pipeliner Projects (date-based records linking Accounts, Contacts, or Opportunities) migrate to a Twenty custom Project object. The custom object schema is pre-created in Twenty before migration, including all date fields, status fields, and lookups to Company and Person. Project stage or status from Pipeliner maps to a Twenty custom picklist field.

Pipeliner Tasks and Appointments migrate to Twenty Task records. Each Task receives a link to its parent record (Company or Person) via Twenty's taskableId and taskableType fields. Task subject, due date, status, and description migrate. Calendar-specific fields (appointment duration, location, attendee list) are preserved as custom fields on the Task record since Twenty's native Task model is simpler than Pipeliner's appointment schema.

Pipeliner Custom Entities migrate to Twenty custom objects with equivalent field structures. We pre-create the Twenty custom object schema (field names, types, and lookup relationships) before any data import. All custom entity records migrate after their referenced standard records (Accounts, Contacts, Opportunities) to satisfy any foreign-key dependencies. The customer confirms custom object names and field types during scoping.

Pipeliner Owner records map to Twenty workspace User records. We match Pipeliner owners by email address against the Twenty workspace User table. Any Pipeliner Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision the User before record import resumes.