Migrate from PipeRun CRM de Vendas to Twenty CRM

PipeRun Contacts map directly to Twenty People records. We export via CSV from PipeRun's web interface and map: nome to name, email to emails primary email, telefone to phones primary phone raw, empresa to company link Relation field. The Contact-to-Company link migrates as a Relation field pointing to the target Company record. We prepend a unique PipeRun record ID prefix to every name in the export file to prevent title-collision deduplication in Twenty's import.

PipeRun Companies export 1:1 to Twenty Companies. Domain, industry, employee count, and address fields map to Twenty Company fields where available. The domain field on a PipeRun Company populates Twenty's domain field, which Twenty uses for Company-Person linking via its Relation model. If PipeRun has no domain, we use a normalized slug derived from the Company name.

PipeRun Deals are the primary revenue object and map to Twenty Opportunities. The Deal name maps to Opportunity name. Deal value (valor) maps to amount amount, expected close date maps to closeDate, and owner maps to opportunityOwner User. The source Funnel name is preserved in a custom field funnel_source__c for audit. We resolve the Funnel-to-Pipeline stage mapping (see object 4) before import so that each Deal lands in the correct Twenty Pipeline stage.

PipeRun's multiple simultaneous Funnels are a platform-specific concept. Each Funnel is extracted as a separate Twenty Pipeline with stages created in the same order and named to match PipeRun. Stage probabilities are mapped from PipeRun's stage win-rate data to Twenty's stage probability values. If PipeRun's Acceleration tier is active (single Funnel cap), we create a single Pipeline. Corporate and Enterprise tiers with multiple Funnels result in multiple Pipelines, each mapped explicitly.

PipeRun Activities include calls, emails, meetings, and notes. We classify by PipeRun activity type and map: email to Note with body preserved, call to Task with TaskSubtype=Call and call outcome in description, meeting to Task with date and duration, and free-text notes to Note. The link to Contact or Deal migrates as a Twenty Relation field pointing to the target Person or Opportunity. Long notes may be truncated to fit Twenty's field length limits.

PipeRun's native CPQ proposal module generates proposals with ICP-Brasil electronic signatures. Proposal content and line items do not have a direct Twenty CRM equivalent because Twenty has no native proposal module. We export the Proposal CSV (name, linked Deal, value, status) as Opportunity fields and attach the proposal PDF files as Twenty Attachments linked to the Opportunity via the file field. Signature status and signer metadata are preserved in a custom field proposal_status__c. The customer rebuilds the proposal workflow using Twenty's external document tools or a third-party CPQ integration.

PipeRun custom fields on Contacts, Companies, Deals, and Activities require explicit type mapping to Twenty field types. We use: text fields map to Text, numeric fields to Number, date fields to Date, dropdown selections to Select, multi-select tags to Multi-Select, and currency fields to Currency. Twenty custom fields are created in Settings > Data Model before CSV import, matching PipeRun's field names as closely as the Two-word naming convention allows. Field-level validation rules in PipeRun are noted for manual recreation in Twenty.

PipeRun Users are assigned as Deal owners, Activity owners, and stage assignees. We extract all distinct user IDs referenced on records and match by email address to Twenty Users. Any PipeRun Owner without a matching Twenty User is held in a reconciliation queue; the customer provisions missing Users in Twenty before record import resumes. Inactive PipeRun users map to inactive Twenty Users to preserve historical assignment audit trails.

PipeRun tags applied to Deals and Contacts migrate to Twenty's Tag system if the customer uses Twenty's tagging feature, or to a multi-select custom field if Twenty's tagging is not active at migration time. Tags with high cardinality (more than 50 distinct values) are migrated as multi-select fields with a picklist of valid values rather than free-form tags to maintain data quality.

Files and attachments linked to PipeRun Deals or Proposals are batch-downloaded from the web interface and re-associated to the corresponding Twenty Opportunity records. The file name and original upload timestamp are preserved. Attachments exceeding Twenty's file size limits are flagged for the customer to store externally and link via URL.

PipeRun workflow automation rules are platform-internal triggers that cannot be exported in a portable format. We do not migrate them. We deliver a written inventory of every active PipeRun Automation with its trigger conditions, actions, and recommended Twenty equivalent (manual rebuild in Twenty Settings or a no-code automation tool such as n8n connected to Twenty's GraphQL API). The customer or their admin rebuilds automations post-migration.

WhatsApp conversations managed through PipeRun MAX are stored in PipeRun's messaging layer and are not included in standard CSV exports. Only metadata (conversation timestamps, participant identifiers) is recoverable. We flag this upfront so the customer knows full message history will not migrate. We recommend exporting WhatsApp chat archives separately via the WhatsApp desktop app before migration begins. Conversation metadata is preserved as Notes on the related Contact record.