Migrate from PipelineManager to Twenty CRM

PipelineManager Pipelines map to Twenty CRM Opportunity stages. Each PipelineManager Stage within a Pipeline becomes a Twenty Stage value on the Opportunity object. We replicate the Stage ordering (sequence) during migration so the visual pipeline board reflects the original deal flow. If you have multiple PipelineManager Pipelines, we create separate Opportunity views in Twenty rather than separate objects, since Twenty uses a single Opportunity model with Stage filtering.

PipelineManager Deals map directly to Twenty CRM Opportunities. The dealname, amount, closedate, stage, and owner map to Opportunity name, amount, closeDate, stage, and assignee. PipelineManager's Deal custom properties migrate to Twenty custom fields on Opportunity. We flag any Deals that exceed PipelineManager's Develop-tier cap (2,500 active Deals) if that tier was the source, since those records may have been archived or rejected silently before export.

PipelineManager People map directly to Twenty CRM Person records. Fields including name, email, phone, and custom properties migrate. We map PipelineManager's People custom fields to Twenty Person custom fields that you pre-create in Settings → Data Model before import. Email address is the dedupe key for Person records.

PipelineManager Company records map directly to Twenty CRM Company. Company name, domain, address, and custom properties migrate. Companies can be linked to People and Opportunities in Twenty; we maintain the Company-Deal association during migration where PipelineManager supports it.

PipelineManager Activities (call logs, emails, meeting records, notes) map to Twenty CRM Task or Note records. We attach each Activity to its parent record (Person or Opportunity) using Twenty's relationship linking. The original timestamp becomes the Task dueDate or Note creation date. Activity type (call, email, meeting, note) maps to a Task custom field or Note type so the timeline renders correctly in Twenty's UI.

PipelineManager file attachments migrate as file references or are exported to a shared location and relinked in Twenty. We preserve original filenames and attach them to the relevant Person, Company, or Opportunity record. If PipelineManager provides a file download API, we pull attachments directly; otherwise we extract the storage URLs and document the relinking steps for your admin.

PipelineManager custom properties on People, Companies, and Deals map to Twenty CRM custom fields. During discovery we inventory every custom property, classify its data type (text, number, date, select, multi-select), and produce the list of custom fields your admin creates in Settings → Data Model before import. Fields must exist in Twenty before CSV import runs; the import creates records, not fields.

PipelineManager Users referenced as Deal owners, Company owners, or Activity assignees map to Twenty CRM Members. We match by email address. Any PipelineManager Owner without a matching Twenty Member goes to a reconciliation queue; your admin must invite that user to Twenty and wait for acceptance before Owner lookups can resolve. Migration cannot complete with orphaned Owner references on Opportunity or Person records.

If PipelineManager holds custom object records beyond standard People, Companies, and Deals, we map them to Twenty CRM Custom Objects created via the /metadata API. Custom Object fields, relationships, and API names are reproduced in Twenty during the schema setup phase before data import begins.

Each PipelineManager Stage name and position within its Pipeline becomes a Twenty Opportunity Stage value. We preserve the probability percentage (if set in PipelineManager) as a Stage custom field in Twenty. Stage color assignments map to the closest Twenty Stage color options.