Migrate from ConvergeHub to Pipedrive

ConvergeHub Leads map directly to Pipedrive Leads. We extract all Lead fields including status, source, assignment, and any custom fields, then map them to Pipedrive's Lead object. Lead ownership resolves by matching the ConvergeHub assigned-to email against Pipedrive User records. Note that Pipedrive's Lead object does not support all ConvergeHub Lead custom fields natively; any that cannot map directly are re-created as custom fields in Pipedrive before import.

ConvergeHub Accounts (companies/organizations) map to Pipedrive Organizations. The Account name becomes Organization name, industry maps to Pipedrive's industry picklist, and address fields map directly. Organization ID is extracted from the CSV for use as a foreign key when importing Contacts and Deals that reference the Account. We run deduplication on Account names before import to avoid duplicate Organization records in Pipedrive.

ConvergeHub Contacts map to Pipedrive People. Each Contact's linked Account ID is preserved and resolved to the Pipedrive Organization ID created during the Account import phase. Contact roles, lifecycle stage, phone, email, and any custom Contact fields migrate as People custom fields. We match by email address as the dedupe key; any Contact without an email address is flagged for manual resolution before the final import phase.

ConvergeHub Deals map to Pipedrive Deals. The Deal's linked Account ID and Contact ID are resolved to their Pipedrive equivalents (Organization ID and Person ID) during the transform phase before inserting Deals. Stage name mapping is configurable since ConvergeHub pipeline stages may not share names with Pipedrive stages; we document the stage mapping table during scoping and apply it during import. Owner assignment resolves by email match to Pipedrive Users.

Each ConvergeHub pipeline maps to a Pipedrive Pipeline with corresponding stages. Stage probability percentages migrate from ConvergeHub to Pipedrive's stage probability field. We configure the Pipedrive pipeline layout and stage order during the schema design phase before any Deal records are imported. Pipedrive supports multiple pipelines at all paid tiers, so pipeline count is not gated by plan tier.

Pipedrive does not have a native Case or Ticket object. ConvergeHub Cases (support tickets linked to Contacts and Accounts) are migrated as follows: Case subject and description migrate as a Note attached to the linked Person or Organization; Case status and priority are stored in custom fields on the Person; and the case reference number is stored in a custom field for traceability. This preserves the data without a native equivalent in Pipedrive. Cases with open status are flagged for your admin to review post-migration.

Pipedrive has no native Invoice or billing object. ConvergeHub Invoices with line items, totals, tax, and payment status are migrated by creating a Deal in Pipedrive that references the original invoice number in a custom field, invoice total in a currency custom field, payment status in a picklist custom field, and the original invoice PDF as a Deal attachment. Partial payments and payment gateway history cannot migrate as transactional records; we document the payment history for your admin to reference in the source export.

ConvergeHub Products (catalog items with SKU, unit price, and description) map to Pipedrive Products. Product name is the dedupe key. We create Pipedrive Product entries before importing any Deals that reference them, then link Deals to Products using Pipedrive's deal-product association API. Unit price from ConvergeHub maps to Pipedrive's price field.

ConvergeHub Activities (calls, tasks, events, logged emails) map to Pipedrive Activities with the activity type preserved. Each activity is linked to its parent record (Person, Organization, or Deal) using Pipedrive's API after resolving the source foreign keys to Pipedrive IDs. Timestamps, notes, and owner assignment transfer directly. Note that ConvergeHub's activity timeline depth may exceed what Pipedrive's native activity UI displays; we validate the most recent 12 months of activity first and expand scope based on the customer's requirements.

ConvergeHub file attachments linked to records migrate as Pipedrive Notes with file attachments. We download the original file from ConvergeHub (where accessible via the UI), upload it to Pipedrive's file storage, and link it to the equivalent Person, Organization, or Deal record. File metadata including the original filename and upload date are preserved in a custom field on the Note for traceability. Large files are chunked during upload to avoid Pipedrive's attachment size limits.

Automation rules defined in ConvergeHub's Tools section (triggers, criteria, and action sequences) cannot be exported via any documented path. We capture the active automation logic during discovery via screenshots and structured field notes, then deliver a written inventory document describing each automation's trigger event, conditions, actions, and recommended Pipedrive workflow equivalent. Your admin rebuilds the automations in Pipedrive's workflow builder post-migration. This documentation is included in the standard migration scope.

Custom fields exist across most ConvergeHub modules (Accounts, Cases, Contacts, Deals, Events, Invoices, Leads, Products, Quotations, Targets, Tasks, and Users). We inventory every custom field during scoping, document its data type, required status, and picklist options, and re-create each one in Pipedrive before any data import begins. Pipedrive supports text, number, date, currency, checkbox, dropdown, and multi-select custom field types. Multi-select picklists from ConvergeHub map to Pipedrive multi-select fields. Any ConvergeHub custom field type that Pipedrive does not support is flagged during scoping for an alternative mapping strategy.

ConvergeHub User records (name, email, role, and ACL assignment) are extracted and matched by email against Pipedrive's User table. Owner assignment on Deals, Cases, and Activities resolves via this User lookup. Users without a matching Pipedrive account are placed in a reconciliation queue for your admin to provision before the final import phase. ConvergeHub role names map to Pipedrive's permission model during this phase.

ConvergeHub Quotations carry product line items, pricing, and terms linked to Deals. Pipedrive has no native quotation object. We migrate quotation data by adding quotation-specific custom fields to the associated Deal (quote number, quote date, valid-until date, terms) and attaching the original quotation document as a Deal attachment. Product line items from the quotation are preserved as a Note on the Deal listing each product and quantity.