CRM migration
Field-level mapping, validation, and rollback between PipeRun CRM de Vendas and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
PipeRun CRM de Vendas
Source
Nutshell
Destination
Compatibility
8 of 10
objects map 1:1 between PipeRun CRM de Vendas and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from PipeRun CRM de Vendas to Nutshell is a CSV-coordinated migration constrained by PipeRun's lack of a publicly documented REST API. There is no programmatic pull available; all record extraction requires coordinated CSV exports from the PipeRun web interface, with manual steps from the customer's side. PipeRun's multiple simultaneous Funnels map to separate Nutshell Pipelines, and the platform's title-based deduplication logic requires pre-processing every export file with unique ID prefixes to prevent silent duplicates at import. We preserve deal-stage history, custom field values, pipeline ownership, and proposal content, and we deliver a written inventory of PipeRun automation rules for the customer's admin to rebuild in Nutshell. WhatsApp conversations from PipeRun MAX are not exportable; we flag this upfront and recommend archiving them separately before migration begins.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a PipeRun CRM de Vendas object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
PipeRun CRM de Vendas
Contact (Contato)
Nutshell
Person
1:1PipeRun Contacts map directly to Nutshell Person records. Each Contact carries name, email, phone, and a link to a Company. We export all standard fields plus any custom field values and apply a unique ID prefix to the Contact name field to prevent title collisions during Nutshell import. Email address is used as the dedupe key in Nutshell. The Contact-to-Company link is resolved after Company import completes.
PipeRun CRM de Vendas
Company (Empresa/Organização)
Nutshell
Company
1:1PipeRun Companies are separate records from Contacts and map to Nutshell Company. The Company name becomes the dedupe key for Nutshell Company import. We extract industry, website, and address fields where populated, and apply the same unique ID prefix strategy used for Contacts to avoid name collisions.
PipeRun CRM de Vendas
Deal (Negócio)
Nutshell
Deal
1:1PipeRun Deals are the primary revenue object and map to Nutshell Deal. Each Deal is linked to a Funnel and Pipeline Stage, carries a monetary value, expected close date, and owner assignment. We extract all deal fields and preserve the original Funnel and Stage names as metadata fields in Nutshell since Nutshell uses a single Pipeline model. Deal value migrates directly; currency formatting is normalized during transform.
PipeRun CRM de Vendas
Funnel (Funil)
Nutshell
Pipeline
1:manyPipeRun supports multiple simultaneous Funnels, each with independent stage definitions. Nutshell does not natively support multiple separate Pipelines; it uses a single Pipeline with configurable stages. We map each PipeRun Funnel to a separate Nutshell Pipeline and create matching stage names in the same order as the source. The number of Funnels is confirmed during discovery, as each additional Funnel adds configuration and testing scope.
PipeRun CRM de Vendas
Activity (Atividade)
Nutshell
Task
1:1PipeRun Activities (calls, emails, meetings, notes) logged against Contacts, Companies, or Deals map to Nutshell Tasks. Activity type, timestamp, owner, and free-text body transfer directly. Long free-text notes may be truncated to Nutshell's field length limits. Activity associations to Deals and Contacts are resolved via the unique ID prefixes we embedded during export pre-processing.
PipeRun CRM de Vendas
Proposal (Proposta)
Nutshell
Quote
1:1PipeRun's native CPQ module with ICP-Brasil electronic signature migrates to Nutshell Quote records. Proposal content, line items, and totals transfer. Signature status is preserved as a metadata field since Nutshell does not have native e-signature. PDF attachments linked to proposals are downloaded and reattached to the corresponding Quote record in Nutshell. Customers requiring continued e-signature capability should evaluate DocuSign or AdobeSign integrations post-migration.
PipeRun CRM de Vendas
User / Owner
Nutshell
User
1:1PipeRun Users are assigned as Deal Owners, Activity owners, and stage assignees. We extract all User IDs and names from PipeRun and match them to Nutshell User accounts by email address during discovery. The customer provisions any missing Nutshell Users before migration begins. Owner mapping is validated before Deal and Activity import to satisfy the required OwnerId reference.
PipeRun CRM de Vendas
Custom Field (Campo personalizado)
Nutshell
Custom Field
lossyPipeRun supports custom fields on Contacts, Companies, Deals, and Activities. We export the full custom field schema (field name, type, and values) and map each to a corresponding custom field in Nutshell. Field types (text, date, dropdown, currency) are mapped to the closest Nutshell equivalent. Dropdown values are mapped as custom options in Nutshell. Custom fields are configured in Nutshell before record import begins.
PipeRun CRM de Vendas
Tag / Label
Nutshell
Tag
1:1PipeRun allows tags on Deals and Contacts. Tags migrate as Nutshell Tags, which apply to both Person and Company records. Where tags represent categorical data beyond simple labeling (for example, pipeline segments or lead sources), we map them to Nutshell custom fields or List memberships as agreed during scoping.
PipeRun CRM de Vendas
File / Attachment
Nutshell
File Attachment
1:1Files and attachments linked to Deals or Proposals are downloaded from PipeRun's web interface in batch and re-associated to the corresponding records in Nutshell after import. Attachment metadata (file name, upload date, file size) is preserved. Very large file batches may require additional delivery time.
| PipeRun CRM de Vendas | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Contato) | Person1:1 | Fully supported | |
| Company (Empresa/Organização) | Company1:1 | Fully supported | |
| Deal (Negócio) | Deal1:1 | Fully supported | |
| Funnel (Funil) | Pipeline1:many | Fully supported | |
| Activity (Atividade) | Task1:1 | Fully supported | |
| Proposal (Proposta) | Quote1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Field (Campo personalizado) | Custom Fieldlossy | Fully supported | |
| Tag / Label | Tag1:1 | Fully supported | |
| File / Attachment | File Attachment1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
PipeRun CRM de Vendas gotchas
No publicly documented REST API for programmatic export
CSV import uses title-based deduplication, not record IDs
Multiple Funnels require explicit stage mapping to avoid schema loss
WhatsApp message content is not exportable from PipeRun MAX
Pricing tiers are not publicly tied to feature gates or user limits
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and export coordination
We audit the source PipeRun account across all active Funnels, pipeline stages, custom fields, active automation rules, and proposal templates. We identify the objects available for export and confirm with the customer which Funnels are production vs. archived. We schedule a joint export session with the customer's PipeRun admin to generate CSV files for Contacts, Companies, Deals, Activities, and Proposals, and we provide a pre-flight checklist to ensure all expected fields appear in each export. This step includes a review of any file attachments linked to Deals or Proposals for batch download.
Export pre-processing and deduplication
We receive the PipeRun CSV exports and run pre-processing before any Nutshell import. This includes prepending a unique ID prefix to every record title across all objects to prevent title-based collisions, normalizing date formats to ISO 8601, mapping Brazilian Real currency formatting to numeric values, and validating field counts against the expected schema. Any records with missing required fields (for example, Deals with no owner assignment) are flagged in a reconciliation report for the customer's admin to resolve before import begins.
Nutshell schema configuration
We configure the Nutshell destination environment before importing any records. This includes creating custom fields to match PipeRun's custom field schema, configuring each Nutshell Pipeline to reflect a PipeRun Funnel with matching stage names in the same order, setting up custom options for dropdown fields migrated from PipeRun, and provisioning Nutshell Users for each PipeRun Owner identified during discovery. Nutshell's REST API is used for all record inserts; the Nutshell Import2 tool is not available for this pair.
Owner and account resolution
We extract every distinct PipeRun User referenced as an owner on Deals, Activities, and Proposals and match them to Nutshell User accounts by email. Any PipeRun owner without a matching Nutshell User goes to a reconciliation queue. The customer's Nutshell admin provisions any missing Users before record import resumes, because OwnerId references are required on standard Nutshell objects. Companies are imported before Contacts so that the Company lookup is available at Contact insert time.
Production migration in dependency order
We run production migration in record-dependency order: Companies (from PipeRun Empresa), Persons (from PipeRun Contato, with Company lookup resolved), Deals (with Funnel and Stage mapped to Nutshell Pipeline and stage), Activities (Tasks linked to Person and Deal via ID prefix), and Proposals (Quotes with line items and file attachments). Each phase emits a row-count reconciliation report before the next phase begins. The unique ID prefixes are stripped from display titles after successful import.
Cutover, validation, and automation inventory delivery
We freeze PipeRun writes during a cutover window and run a final delta migration of any records modified during the migration period. We deliver a written inventory of all PipeRun automation rules (ações automáticas) with their trigger conditions and actions, plus a written proposal inventory noting which proposals require re-signature in a tool like DocuSign post-migration. We support a brief post-migration window to resolve data reconciliation issues reported by the customer's team. We do not rebuild PipeRun automations as Nutshell workflows inside the migration scope.
Platform deep dives
PipeRun CRM de Vendas
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across PipeRun CRM de Vendas and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
PipeRun CRM de Vendas: Not publicly documented.
Data volume sensitivity
PipeRun CRM de Vendas doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during PipeRun CRM de Vendas to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your PipeRun CRM de Vendas to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave PipeRun CRM de Vendas
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.