Migrate from Oncord to Pipedrive

Oncord Contact maps 1:1 to Pipedrive Person. Standard fields (name, email, phone, address, source) transfer directly. The Contact's associated company property maps to a separate Pipedrive Organization record that we create before the Person import so the Org ID lookup is satisfied at insert time. Oncord's activity feed (call, email, meeting records) maps to Pipedrive Activity records linked to the Person. Historical activity timestamps are preserved by setting the Activity date to the original Oncord engagement date.

Oncord Contacts that carry a company name or domain property generate a Pipedrive Organization record. We extract the company name from the Contact's associated-company field, create the Organization first, then link each Contact to it via the Person's org_id field. Organization names are used as the dedupe key to prevent duplicate Organizations when multiple Contacts share the same company. If Oncord's contact data has no company field, Organizations are not created and Contacts migrate as standalone People.

Oncord CustomFields exposed through its internal API component map to Pipedrive custom fields. We handle type mapping: Oncord text fields map to Pipedrive varchar, numbers to double, dates to date, and dropdowns to enum. Multi-select Oncord fields map to Pipedrive set (multi-select). We pre-create the Pipedrive custom field definitions before data import so that the field IDs are available for the value insert phase. Type mismatches that arise from Oncord's loosely-typed custom field schema are resolved during the transform phase with a type-inference pass.

Oncord Groups function as static segmentation lists and map to Pipedrive Tags. Each Group name becomes a Tag label on the associated Person record via the PersonTag join table. We extract all Group memberships per Contact and translate them to multiple Tag inserts per Person. On Lite plans, Oncord restricts filters to Groups only, so Groups carry additional structural weight on Lite accounts. We document the full Group membership matrix so the customer can decide whether Tags or a custom segmented pipeline stage is more appropriate in Pipedrive.

Oncord Products (available only when the Commerce add-on at $40/month is active) map to Pipedrive Products. We export product name, description, SKU (Oncord hs_sku to Pipedrive code), price, inventory quantity, and images. Products are inserted into Pipedrive before any Deals are created so that the product catalog is available for Deal line-item attachment. If Oncord Products carry custom product fields, those map to Pipedrive custom fields on the Product object. Products are only migrated when the Commerce add-on scope is confirmed active during discovery.

Oncord Events with RSVP data, attendee lists, capacity, and location map to Pipedrive Activity records of type meeting. The attendee list (linked to Oncord Contacts) resolves to the corresponding Pipedrive Person records via email match, and Pipedrive ActivityParticipants are created for each attendee. Event date and time transfer as the Activity start and end timestamps. Oncord Events without Contacts (no attendee list) migrate as standalone Activity records. Events are only migrated when the Marketing add-on scope is confirmed during discovery.

Oncord Deals (present only on base plan and above, absent on Lite) map to Pipedrive Deals. We extract deal title, value, stage, owner (hubspot_owner_id resolved to Pipedrive User ID), expected close date, and any custom deal fields. The Oncord deal stage maps to a Pipedrive Pipeline stage that we configure before migration, creating the pipeline if it does not already exist in the destination. If Oncord has no Deals (Lite plan), this step is skipped. Closed-won and closed-lost statuses from Oncord map to Pipedrive status=won and status=lost respectively.

Oncord Marketing automation workflows (triggers, conditions, time delays, and CRM actions) are documented but not migrated as executable code. Oncord and Pipedrive use fundamentally different automation models: Oncord uses contact-triggered branching with built-in delays, while Pipedrive Workflow Automation uses event-based triggers (deal stage change, activity completed, form submitted) with conditions and actions. We deliver a written inventory of every active Oncord workflow with its trigger type, conditions, and action sequence, plus a recommended Pipedrive Workflow Automation equivalent and the estimated rebuild effort. The customer's admin rebuilds them post-migration.

Oncord Web Forms capture contacts and carry custom field mappings per form. We export form definitions and their field-to-contact-property mappings as a written inventory. Pipedrive's Web Forms tool or a third-party form builder (Typeform, JotForm) replaces Oncord forms. We provide a field-mapping table that maps each Oncord form field to its Pipedrive equivalent (Person field or custom field) so the customer's admin or marketing team can rebuild forms with the correct field associations. Form logic and conditional branching are documented for manual rebuild.

Oncord unlimited admin users on base plans map to Pipedrive Users. We extract user records (name, email, role) and match by email against the Pipedrive destination account. Oncord's role semantics (admin, editor, viewer) differ from Pipedrive's permission sets, so we document the role mapping and flag any Pipedrive permission set assignments that need to be configured manually post-migration. Active Oncord users become active Pipedrive Users; inactive Oncord users become inactive Pipedrive Users to preserve historical owner assignment on Contacts and Deals.