CRM migration
Field-level mapping, validation, and rollback between CompanyHub CRM and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
CompanyHub CRM
Source
Pipedrive
Destination
Compatibility
8 of 11
objects map 1:1 between CompanyHub CRM and Pipedrive.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from CompanyHub CRM to Pipedrive is a migration from an SMB-native platform with heavy customization tooling to a mature, sales-focused CRM with a streamlined pipeline interface. CompanyHub stores domain-specific data in Custom Tables that have no direct Pipedrive equivalent; we pre-provision custom fields in Pipedrive and document each Custom Table for the customer's admin to restructure as a linked object or note-based record. UTrons workflow logic (CompanyHub's flowchart automation engine) does not export via API and must be rebuilt in Pipedrive's workflow builder; we deliver a written rebuild specification as part of the migration handoff. We sequence the migration by Companies and Contacts first, then Deals and pipeline stages, then activity history, preserving all cross-object relationships and custom field values. Email activity bodies may be truncated in the CompanyHub v1 API response; we flag this gap during scoping and offer to supplement with an IMAP export if the customer's email platform supports it.
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 CompanyHub CRM object lands in Pipedrive, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
CompanyHub CRM
Contact
Pipedrive
Person
1:1CompanyHub Contacts map directly to Pipedrive People. Standard fields (name, email, phone, address) migrate as typed fields. All custom fields on the Contact record pre-provision in Pipedrive before import. Email is the dedupe key for preventing duplicate Person records. The CompanyHub contact owner maps to Pipedrive's owner_id by email match. If a CompanyHub Contact has an associated Company record, we create the Organization in Pipedrive first and link the Person to it via the org_id field.
CompanyHub CRM
Company
Pipedrive
Organization
1:1CompanyHub Companies map to Pipedrive Organizations. The CompanyHub company domain becomes the Organization's Website field and serves as a secondary dedupe key alongside name. We create all Organizations before Contact import so that the org_id lookup is satisfied at the moment of Person insert. Address, industry, and custom field data migrate to the equivalent Pipedrive Organization fields.
CompanyHub CRM
Deal
Pipedrive
Deal
1:1CompanyHub Deals map to Pipedrive Deals. The CompanyHub dealstage property maps to Pipedrive stage_id within a configured pipeline. We capture the deal owner, value, expected close date, and associated Company (mapped to the Organization) and Contact (mapped to the Person) during import. Any deal-specific custom fields are pre-provisioned in Pipedrive before migration.
CompanyHub CRM
Pipeline Stage
Pipedrive
Pipeline Stage
lossyCompanyHub's customizable pipeline stage names and order are captured during discovery and provisioned in Pipedrive as a new Pipeline with ordered stages. Stage probabilities migrate from CompanyHub to Pipedrive stage probability values. If CompanyHub has multiple deal pipelines, each maps to a separate Pipedrive Pipeline with its own stage set and Record Type (if applicable).
CompanyHub CRM
Task
Pipedrive
Activity
1:1CompanyHub Tasks map to Pipedrive Activities (type = task). Due date, assigned owner, linked Contact, and linked Deal migrate. Task status (open, completed) maps to Pipedrive's done flag. Tasks auto-generated by UTrons are flagged in the migration with a note that they were automation-created, since the underlying automation does not migrate.
CompanyHub CRM
Custom Field (on Contacts, Companies, Deals)
Pipedrive
Custom Field
lossyCompanyHub unlimited custom fields on Contacts, Companies, and Deals pre-provision in Pipedrive before data import. We capture field type (text, number, date, picklist, checkbox, currency) during discovery and create the matching Pipedrive field. Picklist options migrate as Pipedrive drop-down options. Field labels and help text are preserved in the Pipedrive field configuration.
CompanyHub CRM
Custom Table
Pipedrive
Custom Fields or Note-based record
lossyCompanyHub Custom Tables (Payments, Properties, Courses, and similar domain objects) have no direct Pipedrive equivalent. Pipedrive supports custom fields on People, Organizations, and Deals but not standalone custom object types. We document each Custom Table's schema during discovery and propose a migration strategy: (a) if the table is a domain extension of an existing object (e.g., a Payment linked to a Deal), the row data becomes custom fields or linked notes on that parent record; (b) if the table is a standalone entity, it is documented for the customer to rebuild as a linked object in a separate system or as a structured note attachment in Pipedrive. We do not delete Custom Table data; we deliver it in a structured CSV alongside the Pipedrive import for manual re-entry or future automation.
CompanyHub CRM
Quote
Pipedrive
Smart Docs
1:1CompanyHub Quotes map to Pipedrive Smart Docs (PDF document automation). Quote line items, totals, and template references migrate as Smart Doc templates in Pipedrive. If the customer is on Pipedrive's Advanced or Professional tier (which includes Smart Docs), the templates are created during migration; on the Essential tier, quote data migrates as Deal fields with a note recommending Smart Docs activation if quoting workflows are needed.
CompanyHub CRM
Owner/User
Pipedrive
User
1:1CompanyHub users (owners) map to Pipedrive Users. We resolve by email match. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status and role-based visibility settings are preserved in Pipedrive's user permissions.
CompanyHub CRM
Activity: Email
Pipedrive
Activity (type = email)
1:1CompanyHub email activity logs migrate to Pipedrive Activity records with type = email. Subject, timestamp, recipient, and open status transfer. Full email body text is not guaranteed due to CompanyHub API response truncation; we flag body-less emails during migration and offer to supplement with an IMAP export if the customer has email data available. Each activity is linked to the associated Person and Organization via Pipedrive's person_id and org_id fields.
CompanyHub CRM
Activity: Note
Pipedrive
Activity (type = note)
1:1CompanyHub Notes migrate to Pipedrive Activity records with type = note. Note body, timestamp, and associated Contact and Deal linkages migrate. Rich text formatting is preserved where the CompanyHub API returns it. Notes attached to Companies link to the corresponding Pipedrive Organization.
| CompanyHub CRM | Pipedrive | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Organization1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Task | Activity1:1 | Fully supported | |
| Custom Field (on Contacts, Companies, Deals) | Custom Fieldlossy | Fully supported | |
| Custom Table | Custom Fields or Note-based recordlossy | Fully supported | |
| Quote | Smart Docs1:1 | Fully supported | |
| Owner/User | User1:1 | Fully supported | |
| Activity: Email | Activity (type = email)1:1 | Fully supported | |
| Activity: Note | Activity (type = note)1: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.
CompanyHub CRM gotchas
Admin-only export gate blocks non-admin migration scoping
Custom Table schema is not self-describing in the API
UTrons workflow logic does not survive migration
API key cap of 5 limits concurrent migration jobs
Email body content may be truncated in activity API responses
Pipedrive gotchas
Custom field hash keys differ per account
Export access gated by visibility groups
Token-based API rate limits since December 2024
Sequences and Automations not exposed via REST API
Cost escalates via workflow caps and add-ons
Pair-specific challenges
Migration approach
Discovery and data audit
We audit the source CompanyHub account across all objects: Contacts, Companies, Deals, Pipeline Stages, Tasks, Custom Fields (on each object), Custom Tables (count, schema, row counts), Quotes, Users, and Activity logs. We capture the full pipeline stage list, custom field definitions (name, type, options), and Custom Table schemas via customer-provided documentation. We also document active UTrons automations. The discovery output is a written migration scope with record counts per object, a custom field mapping workbook, and a Custom Table disposition plan.
Schema provisioning in Pipedrive
We create all Pipedrive Pipelines and Stages before any data import. We pre-provision custom fields on People, Organizations, and Deals to match CompanyHub field definitions (text, number, date, picklist, checkbox, currency). We create Pipedrive Users for each CompanyHub Owner resolved by email. Pipedrive's Smart Docs templates are set up if the customer is on a quoting tier. We deploy schema elements via the Pipedrive REST API, validating that field types are correct before data load begins.
Custom Table disposition planning
We present the Custom Table disposition plan to the customer's admin before migration. For each Custom Table, we recommend a specific strategy: (a) extension fields on the linked Contact, Company, or Deal record; (b) structured notes attached to the parent record; (c) a separate CSV deliverable for manual re-entry; or (d) a post-migration automation (via Zapier or Make) to create linked records in a third-party system. The admin selects the strategy per table, and we execute the agreed approach during migration.
Staging migration and reconciliation
We run a full migration into a Pipedrive staging environment using production-like data volume. The customer's admin reconciles record counts (People, Organizations, Deals, Activities), spot-checks 25-50 random records against the CompanyHub source, and validates Custom Table data delivery. Any mapping corrections, field type mismatches, or missing values are addressed here before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Organizations (from CompanyHub Companies), People (with org_id linked), Deals (with person_id and org_id resolved), Activities (Tasks, Emails, Notes via Pipedrive API with pagination), and Custom Field data populated on each record. Custom Table data is delivered as the agreed disposition (fields or notes) in the same phase. Each phase emits a row-count reconciliation report before the next phase begins. We use exponential backoff on 429 rate limit responses from Pipedrive's API.
Cutover, validation, and Utron rebuild handoff
We freeze CompanyHub writes during cutover, run a final delta migration of any records modified during the migration window, then enable Pipedrive as the system of record. We deliver the Utron inventory document with rebuild specifications for Pipedrive's workflow builder. We do not rebuild Utrons as Pipedrive workflows inside the migration scope; that is the customer's admin task. We support a one-week hypercare window for reconciliation issues raised by the sales team.
Platform deep dives
CompanyHub CRM
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 CompanyHub CRM and Pipedrive.
Object compatibility
3 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
CompanyHub CRM: Not publicly documented.
Data volume sensitivity
CompanyHub CRM 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 CompanyHub CRM to Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your CompanyHub CRM to Pipedrive migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave CompanyHub CRM
Other ways to arrive at Pipedrive
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.