CRM migration

Migrate from PipeRun CRM de Vendas to Nutshell

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 logo

PipeRun CRM de Vendas

Source

Nutshell

Destination

Nutshell logo

Compatibility

80%

8 of 10

objects map 1:1 between PipeRun CRM de Vendas and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

PipeRun CRM de Vendas logo

PipeRun CRM de Vendas

What's pushing teams away

  • CSV import is unreliable — it uses title-based deduplication instead of ID matching, causing duplicate records or silent failures when deal names change or repeat.
  • Reporting is described as confusing and limited, making it difficult for managers to get clean pipeline forecasts or activity dashboards without manual export work.
  • The platform lacks a publicly documented REST API, making programmatic integrations and automated data pipelines difficult to build and maintain.
  • Some users report that too many steps and options in the UI create cognitive overload, especially for smaller teams that do not need the full feature set.
  • International users find the platform difficult because documentation, support, and integrations are primarily targeted at the Brazilian domestic market.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How PipeRun CRM de Vendas objects map to Nutshell

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)

maps to

Nutshell

Person

1:1
Fully supported

PipeRun 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)

maps to

Nutshell

Company

1:1
Fully supported

PipeRun 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)

maps to

Nutshell

Deal

1:1
Fully supported

PipeRun 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)

maps to

Nutshell

Pipeline

1:many
Fully supported

PipeRun 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)

maps to

Nutshell

Task

1:1
Fully supported

PipeRun 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)

maps to

Nutshell

Quote

1:1
Fully supported

PipeRun'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

maps to

Nutshell

User

1:1
Fully supported

PipeRun 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)

maps to

Nutshell

Custom Field

lossy
Fully supported

PipeRun 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

maps to

Nutshell

Tag

1:1
Fully supported

PipeRun 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

maps to

Nutshell

File Attachment

1:1
Fully supported

Files 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.

Gotchas + challenges

What specifically takes care here

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 logo

PipeRun CRM de Vendas gotchas

High

No publicly documented REST API for programmatic export

High

CSV import uses title-based deduplication, not record IDs

Medium

Multiple Funnels require explicit stage mapping to avoid schema loss

Medium

WhatsApp message content is not exportable from PipeRun MAX

Low

Pricing tiers are not publicly tied to feature gates or user limits

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • No public REST API; all export is CSV-coordinated with the customer

    PipeRun does not publish a REST API with documented endpoints. All data extraction requires CSV exports generated directly from the PipeRun web interface, which requires the customer's active participation. We coordinate with the customer to generate exports from all objects (Contacts, Companies, Deals, Activities, Proposals) and verify field completeness before migration begins. This manual coordination adds steps that are not present in API-based migrations and can extend the timeline if the customer has limited admin access to PipeRun.

  • Title-based deduplication requires pre-processing to avoid silent collisions

    PipeRun's CSV import uses title-based deduplication rather than ID-based matching. When two Deals share the same name, or a Deal is renamed after export, the import will either create a duplicate or silently overwrite the wrong record. We handle this by prepending a unique ID prefix (for example, PR-[uuid]-) to every record title in every export file before Nutshell import. This ensures a clean 1:1 mapping without silent collisions. The prefix is stripped from display names post-import if the customer prefers clean titles.

  • WhatsApp message content from PipeRun MAX is not exportable

    WhatsApp conversations managed through PipeRun MAX (the Chrome extension) are stored in PipeRun's messaging layer and are not accessible via standard exports. Only conversation metadata such as timestamps and participant identifiers are recoverable. We flag this upfront in every PipeRun engagement so the customer knows WhatsApp conversation history will not migrate. We recommend exporting WhatsApp chat archives separately via the WhatsApp Business app before migration begins and storing them in a separate archive location.

  • Nutshell's native import tool does not list PipeRun as a supported CRM

    Nutshell's built-in Import2 migration tool lists over 25 supported source CRMs including Pipedrive, HubSpot, Salesforce, and Close. PipeRun is not among them. The Nutshell Import2 connector cannot be used directly. We handle the migration via the Nutshell REST API, mapping each object manually with the same deduplication and validation logic used for CSV-sourced migrations. This is a known limitation of the pair and is priced into the engagement scope.

Migration approach

Six steps for a successful PipeRun CRM de Vendas to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

PipeRun CRM de Vendas logo

PipeRun CRM de Vendas

Source

Strengths

  • Brazil-native CRM with Portuguese-language UI, support, and Brazilian commercial workflow assumptions.
  • Integrated WhatsApp Business API for centralized service across multiple channels and tickets.
  • Built-in product catalog with price lists, discounts, and multi-brand proposal generation.
  • Bundled electronic signature for proposals and contracts inside the CRM, removing the need for a separate e-sig tool.
  • Annual upfront prepay earns 20% discount; 14-day free trial available.

Weaknesses

  • Standardised 12-month contract with auto-renewal is heavier than month-to-month CRMs popular outside Brazil.
  • G2 product profile has been inactive for over a year — comparison data is thin.
  • Brazilian focus limits international fit; product UI and support are Portuguese-first.
  • Pricing tiers and per-user rates are not transparently published.
  • Customers needing global multi-currency, multi-language deployment typically choose HubSpot, Salesforce, or Pipedrive.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across PipeRun CRM de Vendas and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    PipeRun CRM de Vendas: Not publicly documented.

  • Data volume sensitivity

    B

    PipeRun CRM de Vendas doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your PipeRun CRM de Vendas to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about PipeRun CRM de Vendas to Nutshell data migrations

Answers to the questions buyers ask most during PipeRun CRM de Vendas to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and three weeks for accounts under 3,000 Contacts and 1,500 Deals with a single Funnel and minimal custom fields. Migrations with multiple simultaneous Funnels, large activity histories (over 50,000 records), or extensive custom field schemas move to four to seven weeks because of the stage-mapping design work, CSV coordination requirements, and deduplication pre-processing. The customer's availability to generate and share PipeRun CSV exports is the most common timeline variable.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PipeRun CRM de Vendas.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day