Intelligent CRM’s Pipedrive connector is an administrator-managed, one-way migration path. It reads supported Pipedrive records and does not change data in Pipedrive. Reconnecting later does not enable continuous synchronization. Organizations, people, and Deals form the required core; activities and notes are optional history that an administrator can include or leave behind.
The import experience begins with a preview that counts supported entity families and prepares owner suggestions. The administrator reviews warnings, maps Pipedrive users to workspace users, chooses whether activities and notes should be included, and starts a background job. Core records are processed in dependency order so available organization, person, pipeline, stage, and Deal relationships can be resolved before optional history is attached. The job reports created, updated, skipped, and failed outcomes by entity rather than reducing a migration to one total.
This guide reflects the implemented behavior reviewed on October 29, 2026. It covers preflight cleanup, connection and preview, owner mapping, core-record dependencies, optional timeline history, INR and archived-Deal limits, progress, reconciliation, and safe reruns. It does not imply a partnership with Pipedrive or promise that every source value has a destination equivalent. The objective is a destination whose imported records and exceptions can be explained by the team that will operate it.
Separate required core data from optional history
The Pipedrive importer always brings supported core records and lets the administrator choose whether supporting activities and notes should follow.
| Import area | Selection behavior | Migration consequence |
|---|---|---|
| Organizations, people, Deals | Always included in a Pipedrive import | These records establish the customer and pipeline structure. |
| Pipelines and stages | Imported as supporting Deal metadata | Deals require available pipeline and stage context. |
| Activities | Optional | Supported calls, meetings, tasks, and other activities become CRM tasks with available relations. |
| Notes | Optional | A supported note is attached only when an imported Deal, person, or organization can receive it. |
| Writeback or continuous sync | Not enabled | Pipedrive remains unchanged and later imports must be started explicitly. |
Prepare a migration baseline and a clear cutover rule
Begin by recording expected counts for organizations, people, active Deals, users, pipelines, stages, activities, notes, and important custom fields. Segment Deals by currency and status. Every eligible Deal needs a title, primary person, organization, pipeline, expected close date, INR currency, and a resolvable destination stage: an available source stage for an open Deal or a generated terminal stage for a won or lost Deal. Cleaning or documenting exceptions before the run makes the preview warning and final skip totals understandable rather than surprising.
Decide what happens after the final run. The connection is a one-way import, not a live bridge between editable CRMs, so a source change made after cutover will not appear automatically. Name the system that receives new work, the time when sellers stop editing both sides, and the administrator authorized to run a final delta import. Also choose how long Pipedrive remains available for reference. The optional activity and note paths can move supported history, but they should not be treated as proof that every source artifact or attachment has been replicated.
Connect the intended Pipedrive company as a workspace administrator
Only an Intelligent CRM workspace administrator can connect, preview, start, open detailed import-job views, or disconnect a Pipedrive import. Other authenticated teammates can see the connection state and latest import summary, but they do not receive those management controls. Connect the intended Pipedrive company through OAuth and verify the displayed company name or domain before proceeding. A successful connection grants the read access required for migration; it does not give Intelligent CRM permission to rewrite source records.
Make the data boundary explicit to stakeholders. Imported records become an operational dataset in Intelligent CRM. Disconnecting later prevents new imports but leaves records already imported available, and it does not modify Pipedrive. Reconnecting does not activate continuous synchronization. These properties reduce source risk during migration, yet they also require disciplined cutover communication. If a team continues changing Pipedrive, it must schedule and validate another explicit import rather than waiting for invisible background sync that does not exist.
Use the preview to find structural problems before processing
The preview reads Pipedrive data, counts organizations, people, Deals, activities, and notes, lists Pipedrive users and CRM users, and prepares owner suggestions. It also presents a key eligibility warning: only INR Deals with a person, organization, pipeline, expected close date, and resolvable destination stage can import. Open Deals require an available source stage; won and lost Deals use generated terminal stages. Current connector capability marks archived Deals as unsupported, so archived Deals are not included. Compare these counts with the baseline and investigate large gaps before starting the background job.
Preview is a planning aid, not a guarantee that each counted value can be persisted. A record may still be skipped because a required name or association is missing, a custom-field value cannot be represented, a related record failed or was unavailable, or destination uniqueness rules prevent assigning a value. Read every preview warning and preserve it with the migration record. If preview is temporarily unavailable, the interface can still start the import, but owner suggestions are then unavailable and unmatched owners fall back to the administrator; for a production migration, restoring preview is usually the safer choice.
Map Pipedrive users to destination owners
Owner suggestions use matching email addresses between Pipedrive users and Intelligent CRM users. The administrator can provide a different explicit destination, and that override wins. If no explicit mapping is submitted, the worker still applies an exact-email match automatically; only a source owner with no match falls back to the administrator starting the import. The resolved owner supports core records and optional history, including task assignment and note attribution where available. Provision destination users and resolve former employees or shared source identities before the final run rather than allowing a large fallback group to obscure accountability.
After import, compare owner distributions by object. Sample organizations, people, Deals, and activities for every mapped user and for the fallback administrator. Owner mapping does not define provider identity: the durable Pipedrive entity link uses the source company, entity type, and external identifier, so remapping an owner does not create another copy of the record. Still, repeat imports preserve locally edited fields under the merge rules. Test an owner change on a controlled sample and inspect warnings instead of assuming every later mapping will overwrite current destination ownership.
Import core records in dependency order
The background workflow prepares metadata and pipelines, then processes organizations, people, and Deals before optional activities and notes. Organizations become Accounts, people become Contacts, and eligible Pipedrive Deals become Deals. This order allows people to connect to available organizations and lets Deals resolve their required person, organization, pipeline, destination stage, and owner context. A Deal whose related person, organization, or pipeline is unavailable is skipped and warned rather than being created with invented associations.
Deal eligibility is intentionally strict. A Deal needs a non-empty title, primary person, organization, pipeline, valid expected close date, INR currency, and a resolvable destination stage. An open Deal requires its available source stage; won and lost Deals use corresponding generated terminal stages for the imported pipeline. Non-INR Deals are skipped and reported, while fractional INR amounts are rounded to the nearest INR unit with a warning. Unsupported statuses or unresolved stage context cannot produce a trustworthy Deal. Review these conditions before interpreting a smaller destination pipeline as unexplained data loss.
Choose activities and notes as separate history decisions
Activities are optional. When included, supported Pipedrive calls, meetings, tasks, and other activities become Intelligent CRM tasks. The importer carries a subject or generated fallback title, plain-text description, done or to-do status, available priority, assignee, due time, completion time, and supported relationships to Deals, Contacts, Accounts, and additional participants. Values are bounded by destination limits, so long subjects or descriptions can be truncated with warnings, and priorities without an exact representation can arrive with no priority.
Notes are also optional and follow a different path. A supported Pipedrive note becomes a record activity only when it has content and can resolve a target. Deal is preferred, followed by person and organization. A note whose related imported record is unavailable is skipped rather than detached from its context. This distinction is specific to Pipedrive: the current HubSpot importer does not import activities or notes. Choose these options according to retention, usefulness, and validation capacity; more history is not automatically better when the team cannot verify ownership and relationships.
Monitor background progress without depending on the dialog
Starting an import creates a queued job and a background workflow. The dialog can be closed while work continues. Returning to the connector shows the latest phase and server-confirmed totals. Progress includes processed, created, updated, skipped, and failed counts, plus per-entity results for organizations, people, Deals, activities, and notes. A temporary polling interruption causes the interface to retry; it does not by itself prove that the background job failed. Use the job state and error message as the source of truth.
Treat skipped and failed as different outcomes. A skip can express policy, such as a non-INR Deal or a note without an imported target. Failed indicates an individual record could not be persisted, while a broader workflow problem can fail the job. Read warnings for unsupported custom fields, missing relationships, validation, truncation, local conflicts, and provider limitations. The connector also prevents overlapping CRM connector operations in the workspace, so wait for the active operation to finish rather than trying to start a competing import.
Reconcile core structure before optional history
Validate in dependency order. First compare imported Accounts and Contacts with organizations and people, including exact matches that adopted existing local records. Check primary emails, additional addresses or phones, destination uniqueness behavior, owners, and Account relationships. Next sample Deals from each pipeline and status, verifying title, INR amount, expected close date, pipeline, stage, primary Contact, Account, owner, and won or lost context. Only after the core graph is credible should the team validate task and note history.
For activities, sample open and completed items, different priority labels, due dates interpreted in the connected Pipedrive user’s timezone, multiple participants, and each relationship target. A date-only activity defaults to 09:00 in that zone, while a missing or invalid zone falls back to UTC. For notes, confirm plain text, actor, timestamp, and destination record. Reconcile custom-field definitions and representative values on Accounts, Contacts, and Deals. Review warnings where duplicate domains, websites, or email addresses could not populate unique destination fields. Counts alone cannot reveal a task attached to the wrong Deal or a note missing because its source target never imported.
Use a second run to test identity and local-edit protection
Pipedrive records receive durable provider links, and the importer stores a baseline of values it previously supplied. On a later run, a remote field can replace the destination value only when the local value still equals the prior imported value. A user edit or intentional local clear diverges from that baseline and is preserved with a warning. A blank destination is eligible for a supported source value only when no prior imported baseline exists. Exact email can support adopting an existing Contact, while exact domain or website can support adopting an existing Account; ambiguous candidates are imported separately for review rather than being merged recklessly.
Rehearse this behavior. Change one source field while leaving its local copy untouched, edit another destination field locally, update an optional activity or note, and run the import again. Confirm that the untouched field updates, the local edit remains, the same source identities do not duplicate, and history changes follow the selected options. Include a source-linked record deleted locally; the importer’s preserved-deletion outcome should avoid silently recreating it. A second run is also the right time to verify that owner remapping and relationship updates do not break identity.
Move the core pipeline and selected history without changing Pipedrive
A sales team records its organization, person, Deal, pipeline, activity, and note counts, then identifies Deals without expected close dates and Deals in currencies other than INR. A workspace administrator connects the intended Pipedrive company and reviews the preview. Active users map by email; former-user records fall back to a named administrator for later reassignment. The team includes activities because open tasks are operationally important, but includes notes only after confirming its retention policy. The background import processes metadata, pipelines, organizations, people, Deals, activities, and notes while the administrator monitors entity-level results.
Reconciliation explains why archived Deals, non-INR Deals, and Deals missing required relationships did not arrive. Sampled Accounts and Contacts retain available organization-person context, Deals have valid pipeline and stage relationships, activities appear as tasks, and notes attach only to imported records. The team changes one destination field and one source field, repeats the import, and confirms that the local edit is preserved while the untouched value updates. Pipedrive remains unchanged throughout, and new sales work begins in Intelligent CRM after the documented cutover.Pipedrive migration readiness and validation checklist
- Define the final source-edit cutoff, destination system of record, migration owner, and reconciliation owners
- Capture counts for organizations, people, Deals, users, pipelines, stages, activities, notes, and critical custom fields
- Identify archived and non-INR Deals plus missing title, person, organization, pipeline, expected close date, or resolvable stage context
- Connect the intended Pipedrive company through an Intelligent CRM workspace administrator
- Review preview counts, warnings, supported capabilities, and owner suggestions before starting
- Review explicit and automatic exact-email owner matches, then document the no-match administrator fallback
- Choose activities and notes independently based on operational value, retention, and validation capacity
- Monitor queued and running phases plus created, updated, skipped, and failed outcomes by entity
- Validate Accounts, Contacts, Deals, pipelines, stages, owners, custom fields, and required relationships first
- Validate activity-to-task conversion and note targets only after the core record graph is correct
- Review duplicate email, domain, website, unsupported-field, truncation, currency, and relationship warnings
- Run a controlled second import to prove stable identity, remote updates, local-edit preservation, and deletion handling
- Communicate that the migration is one-way, read-only with respect to Pipedrive, and not continuous sync
Move Pipedrive data as a governed graph, not a pile of rows
The Pipedrive importer combines preview counts, email-assisted owner mapping, dependency-ordered core objects, optional activity and note history, background progress, durable source identities, and per-entity outcomes. Those controls let a team move supported customer structure while leaving Pipedrive unchanged. They also make limitations visible: archived Deals are excluded, Deal eligibility requires specific relationships and dates, amounts must be INR, and optional history can attach only when its related imported record exists.
A good migration accepts those boundaries and proves the important behavior. Reconcile core records before history, investigate warnings, sample every pipeline and owner group, and run the import twice with deliberate local and source changes. When the team can explain every major count difference and demonstrate that a rerun neither duplicates records nor erases local work, it has a credible basis for moving daily sales execution to Intelligent CRM.