Migrate from PipelinePRO to Twenty CRM

PipelinePRO Contact records export as CSV with name, email, phone, and custom field columns. We map these to Twenty's Person object, which stores name as firstName and lastName (split from the full name column), email as a verified email record, and phone in the phoneNumber field. Custom properties on PipelinePRO contacts require explicit field-by-field mapping to Twenty's custom field equivalents, which we create in Settings → Data Model before import. Any PipelinePRO contact without an email is flagged for review because Twenty requires an email identifier for person record creation.

PipelinePRO Company records map to Twenty's Company object. Company name, domain, address, and industry fields map directly. The quality of company data depends on how consistently users populated the company field on contacts in PipelinePRO; we flag sparse company records (fewer than two linked contacts) for manual review before bulk import. Company record creation must precede Contact import so that the company relationship is satisfied at the time of person insert.

PipelinePRO Deal records include name, value, stage, owner, and expected close date. We map these to Twenty's Opportunity object, where amount maps to expectedValue, closeDate maps to closeDate, and stage maps to a Twenty pipeline stage value. PipelinePRO pipeline and stage names are configurable, so we build a customer-reviewed stage mapping table before any deal records move. Deal attachments are handled separately as file imports via Twenty's file storage.

PipelinePRO uses customizable pipeline boards with drag-and-drop stage definitions. We extract the pipeline name and stage list from the customer's account and recreate the equivalent pipeline structure in Twenty via Settings → Opportunities → Pipelines. Each PipelinePRO pipeline becomes a Twenty Pipeline with stages created in the same order and with matching names where possible.

Stage names and ordering are configurable per pipeline in PipelinePRO. We map source stages to destination stages using a customer-reviewed mapping table before bulk deal migration begins. Stage probability values from PipelinePRO are recorded as a custom field on the destination stage if the customer uses them for forecasting.

PipelinePRO Lead records function as early-stage contacts with their own status field. We map these to Twenty Person records and preserve the original lead status as a custom property (lead_source_status__c) because Twenty does not have a separate Lead object equivalent. The customer reviews and reassigns any active lead routing logic post-migration.

PipelinePRO custom fields exist per object but there is no bulk schema export. We ask customers to provide a screenshot or list of custom field names and their types before migration so we can create matching fields in Twenty's data model via Settings → Data Model → Add Field. Multi-select picklists and date fields require specific type mapping; multi-select fields have known GitHub issues in Twenty that we flag before use.

Tags on PipelinePRO contacts and deals export as comma-separated values in the CSV. We parse these into a normalized tag list and apply them as native tags in Twenty, where tags are a first-class tagging system on Person and Company records. Tag names with spaces or special characters are normalized to lowercase hyphenated format.

PipelinePRO User accounts export as a simple list with name and email address. We map these to Twenty WorkspaceMember records. Owner assignment on Deals and Contacts resolves by matching PipelinePRO owner email to Twenty WorkspaceMember email. Any PipelinePRO owner without a matching Twenty user is held in a reconciliation queue for the customer to provision before deal import resumes.

Uploaded files attached to PipelinePRO deals or contacts export via download links if accessible through the account interface. We retrieve accessible files and re-attach them to the corresponding migrated records in Twenty. Files that are not retrievable through screen-share access are flagged for manual handling during the migration scoping call.