CRM migration
Field-level mapping, validation, and rollback between eSalesTrack and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
eSalesTrack
Source
Pipedrive
Destination
Compatibility
9 of 11
objects map 1:1 between eSalesTrack and Pipedrive.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from eSalesTrack to Pipedrive is a structural consolidation for small teams that have outgrown entry-level CRM tooling. eSalesTrack uses unified Lead and Contact objects alongside Accounts and Opportunities; Pipedrive separates People into Organization-linked contacts and individual persons, with Deals tied to pipeline stages rather than generic Opportunity records. We extract eSalesTrack data via CSV export, deduplicate across all four record types, and load into Pipedrive in dependency order: Organizations first, then People with AccountId resolved, then Deals with stage mapping, then Activity history via API. eSalesTrack's basic workflow automation does not migrate; we deliver a written inventory of every active workflow for the customer's admin to rebuild in Pipedrive's automation builder. The visual pipeline metaphor in Pipedrive requires pipeline and stage configuration before Deal import so that stage assignment is valid at insert time.
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 eSalesTrack 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.
eSalesTrack
Contact (role=Lead)
Pipedrive
Person
1:1eSalesTrack stores unqualified prospects and inbound leads in the Contact object with a role or type field set to Lead. These map directly to Pipedrive Person records with no Organization link. We extract first name, last name, email, phone, and any custom fields from the eSalesTrack Contact record and insert them as Person records in Pipedrive. Source-system lead status is preserved in a custom field esalestrack_lead_type__c for reference during Pipedrive setup.
eSalesTrack
Contact (role=Account Contact)
Pipedrive
Person + Organization link
1:1eSalesTrack Contact records with a role indicating they are associated with an Account map to Pipedrive Person records linked to the corresponding Organization. We resolve the eSalesTrack AccountId to the newly created Organization record and set the Person's organization_id at insert time. If the eSalesTrack Contact has no AccountId, we insert as a standalone Person and flag for the customer admin to link manually in Pipedrive.
eSalesTrack
Account
Pipedrive
Organization
1:1eSalesTrack Account records map to Pipedrive Organization. The Account name becomes the Organization name, domain maps to the Website field, and address fields map to city, state, country, and postal fields. Organization is created before any Person import so that organization_id is available at Person insert time. The domain field is used as the deduplication key when multiple eSalesTrack Accounts share the same company name.
eSalesTrack
Opportunity
Pipedrive
Deal
1:1eSalesTrack Opportunity records map to Pipedrive Deal. The Opportunity name becomes the Deal title, amount maps directly, close date maps to the close date field, and stage maps to a Pipedrive Stage. Owner assignment migrates by email-to-user lookup. We create the target Pipeline and Stage structure in Pipedrive before Deal import so that stage_id is valid at insert time. Closed-Lost and Closed-Won status from eSalesTrack map to the corresponding Pipedrive Stage entries.
eSalesTrack
Pipeline Stage
Pipedrive
Stage
lossyEach eSalesTrack Opportunity stage value becomes a Pipedrive Stage entry within a Pipeline. We create the Pipeline in Pipedrive first, then add Stage rows in order matching eSalesTrack's stage sequence. Stage probability percentages from eSalesTrack migrate to Pipedrive Stage probability fields, rounded to the nearest whole number. The customer admin approves stage ordering and naming during the scoping review before migration runs.
eSalesTrack
Owner
Pipedrive
User
1:1eSalesTrack Owner records (sales reps and managers assigned to Contact, Account, and Opportunity) map to Pipedrive User by email address. We extract every distinct owner email referenced on source records, match against the existing Pipedrive User table, and flag any owner without a matching Pipedrive User in a reconciliation queue. The customer admin provisions any missing Pipedrive Users before record import begins because OwnerId is a required field on Deal in Pipedrive.
eSalesTrack
Engagement: Call
Pipedrive
Activity (type=call)
1:1eSalesTrack call records map to Pipedrive Activity with type=call. Call duration, disposition, and direction migrate to Pipedrive Activity's custom fields if present, otherwise to standard fields. Activity date and time are preserved from the source timestamp. The activity links to the resolved Person and Deal via activity_type_id references.
eSalesTrack
Engagement: Meeting
Pipedrive
Activity (type=meeting)
1:1eSalesTrack meeting records map to Pipedrive Activity with type=meeting. Start time, end time, location, and attendee list migrate to the corresponding Pipedrive Activity fields. Meeting notes migrate as the Activity description. Links to Person and Deal records are resolved via Pipedrive's activity_type_id and person_id references at migration time.
eSalesTrack
Engagement: Task
Pipedrive
Activity (type=task)
1:1eSalesTrack task records map to Pipedrive Activity with type=task. Task subject, due date, priority, and completion status migrate directly. The status field maps to Pipedrive's done flag (0 for open, 1 for completed). Links to the associated Person or Deal are resolved through lookup during migration.
eSalesTrack
Engagement: Note
Pipedrive
Note
1:1eSalesTrack notes attached to Contact, Account, or Opportunity map to Pipedrive Note records. Note content, author, and timestamp migrate directly. Pipedrive Note is linked to the target Person, Organization, or Deal via the pins array at insert time. If eSalesTrack notes include attachments, we attach them separately as Activity attachments through Pipedrive's attachments endpoint.
eSalesTrack
Custom Field
Pipedrive
Custom Field
lossyeSalesTrack custom fields on Contact, Account, and Opportunity migrate to Pipedrive custom fields. We create the destination custom fields in Pipedrive under Settings > Customize fields before any data import begins, matching the field type (text, number, date, dropdown, checkbox) as closely as possible. Pipedrive field-level security is set to visible and editable for the migration user during import. Fields that cannot be exactly type-mapped (e.g., eSalesTrack picklist with values not supported by Pipedrive dropdown) are documented with a conversion recommendation during scoping.
| eSalesTrack | Pipedrive | Compatibility | |
|---|---|---|---|
| Contact (role=Lead) | Person1:1 | Fully supported | |
| Contact (role=Account Contact) | Person + Organization link1:1 | Fully supported | |
| Account | Organization1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Pipeline Stage | Stagelossy | Fully supported | |
| Owner | User1:1 | Fully supported | |
| Engagement: Call | Activity (type=call)1:1 | Fully supported | |
| Engagement: Meeting | Activity (type=meeting)1:1 | Fully supported | |
| Engagement: Task | Activity (type=task)1:1 | Fully supported | |
| Engagement: Note | Note1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | 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.
eSalesTrack gotchas
Implementation, training, customisation, and migration are billed separately
Custom object support is not publicly documented
Reporting templates are fixed — advanced analytics require external BI
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 CSV extraction audit
We request and review eSalesTrack CSV exports for Contact, Account, Opportunity, and any available engagement log data. We audit record counts per object, identify the Lead-versus-Contact role field values, count distinct owners by email, and flag custom fields present in the export. We also request a separate export of eSalesTrack workflow rules so we can build the automation inventory. The discovery output is a written scope document with record counts, the split rule definition, custom field list, and any known export gaps requiring customer action.
Pipedrive pipeline and schema configuration
Before any data import, we create the target Pipeline and Stages in Pipedrive matching eSalesTrack's stage sequence. We configure custom fields in Pipedrive Settings to match the eSalesTrack schema, set field types correctly, and grant the migration user edit access. We also provision Pipedrive Users for each eSalesTrack Owner email that has a match, and document any Owner without a Pipedrive User for the customer admin to resolve. Schema configuration happens in a staging phase separate from data import to catch field type mismatches early.
Data cleaning and deduplication
We parse the eSalesTrack CSV exports, identify duplicate Contact records (same email, different eSalesTrack IDs), duplicate Accounts (same name or domain), and orphaned Opportunities (no valid AccountId). We remove exact duplicates and flag near-duplicates for the customer admin to review before migration. The dedup output is a cleaned dataset and a duplicate decision log that the customer signs off on. Running deduplication before import prevents duplicate Pipedrive records that are significantly harder to clean up after the CRM is live.
Sandbox migration and mapping validation
We run a full migration into a Pipedrive trial or sandbox account using the cleaned dataset. The customer admin reviews a sample of 25-50 records per object type (People, Organizations, Deals, Activities) against the source CSV to confirm field mapping accuracy, Organization linkage on Person records, and stage assignment on Deals. We correct any mapping errors identified in review before promoting to production migration. This step is the last opportunity to change field mapping without affecting live data.
Production migration in dependency order
We run production migration in record-dependency order: Organizations first (Accounts from eSalesTrack), then People with OrganizationId resolved (Contacts split by role), then Deals with stage_id and owner_id resolved, then Activities. Each phase emits a row-count reconciliation report showing records inserted, skipped, and errored. We resolve any errors before proceeding to the next phase. Activity history is loaded last because it has the highest volume and requires Person and Deal lookups to be valid first.
Cutover, validation, and workflow handoff
We freeze new eSalesTrack writes during cutover, run a final delta migration of records modified during the migration window, then present a reconciliation summary showing total records migrated per object type. We deliver the workflow automation inventory document to the customer admin for Pipedrive rebuild. We support a three-day post-migration validation window where we resolve record linkage issues and data discrepancies. We do not rebuild eSalesTrack workflows as Pipedrive automation sequences inside the migration scope; that work is a separate engagement or an internal admin task.
Platform deep dives
eSalesTrack
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across eSalesTrack and Pipedrive.
Object compatibility
1 of 8 objects need a manual workaround.
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
eSalesTrack: Not publicly documented.
Data volume sensitivity
eSalesTrack 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 eSalesTrack to Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your eSalesTrack 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 eSalesTrack
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.