Migrate from webCRM to Pipedrive

webCRM Organisations map directly to Pipedrive Organizations. We use Organisation ID and Organisation Name as dedupe keys during import. webCRM Organisation-specific custom fields transfer to Pipedrive custom fields on the Organization object, which requires Pipedrive Growth tier ($29/user/mo) or above. If webCRM Organisation records contain address blocks, we map these to Pipedrive's address fields (street, city, state, zip, country) and note that webCRM address sub-fields may require flattening.

webCRM Contacts map to Pipedrive Persons. The Organisation ID from webCRM resolves to the Pipedrive Organization ID at import time, preserving the Organisation-Contact relationship. webCRM Contact-specific custom fields map to Pipedrive Person custom fields (Growth tier required). Email address uniqueness is enforced as the dedupe key; contacts with duplicate emails are flagged in a reconciliation report before final import.

webCRM Deals map to Pipedrive Deals. The Organisation and Contact links from webCRM resolve to Pipedrive Organization ID and Person ID respectively. webCRM pipeline stage names are mapped to Pipedrive stage names during import; if the customer has not pre-created matching Pipedrive stages, we use a configuration step to create them before deal import. Deal value and currency fields transfer directly.

webCRM Deliveries are order records exported in webCRM Delivery XML via the Zynk connector. The nested XML structure with line-item detail requires flattening into two objects: the parent Delivery becomes a Pipedrive Deal, and each line item becomes a Product entry linked to that Deal. We parse the XML, extract line-item fields (product name, quantity, unit price, tax, discount), and restructure them into tabular format before loading. This transformation preserves all order detail while conforming to Pipedrive's Deal-with-Line-Items data model.

webCRM Products from the Product Database map to Pipedrive Products. ProductCode, name, description, and pricing fields transfer to the Pipedrive Product record. Standard Pricebook entries are created during import so that Products can be added to Deals. webCRM inventory quantity fields map to a custom field in Pipedrive since Pipedrive does not natively track inventory on the Product object.

webCRM Tasks link to Organisations or Contacts and map to Pipedrive Activities (which encompass calls, tasks, and notes under a single activity model). Task subject, body, due date, and completion status transfer. webCRM task status labels (such as Open, Completed, Overdue) are mapped to Pipedrive Activity type and status values during import. Activity timestamps are preserved to maintain the historical timeline.

webCRM Automation Rules are stored internally with no public export endpoint. Time-based automations, deadline reminders, and inactivity triggers cannot be migrated as code. We identify every active automation during scoping and produce a written inventory documenting the trigger type, conditions, actions, and the Pipedrive Workflow equivalent. The customer's team rebuilds these in Pipedrive's workflow builder post-migration. Budget one to two hours per automation rule for manual rebuild.

webCRM custom fields on Organisations, Contacts, Deals, and other objects are extracted during scoping. Each custom field is mapped individually to a Pipedrive custom field of equivalent type (text, number, date, picklist, checkbox). Pipedrive Growth tier or above is required for custom fields on Persons, Organizations, and Deals. We confirm the customer's Pipedrive plan tier during scoping and flag any fields that exceed the current plan's custom field allowance before import.

webCRM Owner references on Organisations, Contacts, Deals, and Tasks are resolved by matching the owner email address against Pipedrive User records. If a webCRM owner has no matching Pipedrive User, the record is held in a reconciliation queue and the customer's admin provisions the missing User before record import resumes. Active owner assignments on Deals and Tasks transfer as the Pipedrive User ID.

webCRM order history and quote documents attached to Deliveries or Deals are migrated as Notes linked to the corresponding Pipedrive Deal. We extract document content (order numbers, totals, line-item summaries) and attach them as Note records. Binary file attachments (PDFs, spreadsheets) are documented separately for manual re-upload since Pipedrive's native import does not support file attachment migration.