Migrate from openCRX to Pipedrive

openCRX LegalEntity records (the company-side of Account) map to Pipedrive Organisation. Company name, industry, revenue tier, and address fields migrate directly. The openCRX Account full-text search index does not have a Pipedrive equivalent; we do not replicate it. Multi-entity openCRX deployments require a segment-level filter during export that we apply before the Organisation import batch.

openCRX Contact records (the individual-side of Account) map to Pipedrive Person. Each Contact retains a link to its parent LegalEntity Organisation via the openCRX primaryAccount reference, which we resolve as a Pipedrive Organisation ID during the Person insert. openCRX Contact phone numbers and postal addresses (modelled as separate value objects) collapse into Pipedrive's flat Person fields.

openCRX Opportunities inherit from abstract contract classes and carry stage, rating, owner, and estimated value. We map the openCRX opportunityState and salesPhase properties to Pipedrive Deal stage names, with a custom field ocrx_original_stage__c preserving the source value. openCRX contract-position detail (product, quantity, price) migrates to Pipedrive Deal products as line items if the Advanced plan is active; otherwise it is stored as structured text in a custom field ocrx_line_items__c.

Pipedrive has no native Quote object at Essential or Advanced tiers; only Smart Docs (Professional+) offers a structured Quote feature. For most openCRX-to-Pipedrive migrations, we treat Quotes as Deals with a custom field ocrx_quote_status__c and the quote body stored as structured text in a notes field. If the customer is on Pipedrive Professional or above, we evaluate Smart Docs as the Quote replacement and migrate quote line items as Deal products.

openCRX Sales Orders inherit from the same contract hierarchy as Quotes and Opportunities, with order positions modelled as contract positions. Pipedrive has no native Sales Order object. We map order headers to Deals with custom fields ocrx_order_id__c and ocrx_order_status__c, and order positions to structured custom fields or Deal products depending on plan tier. Order-to-Invoice lineage is preserved in a custom text field for audit.

openCRX Invoices are terminal contract objects. Pipedrive does not have a native Invoice object. We migrate invoice headers and line items as custom fields on the parent Deal (ocrx_invoice_id__c, ocrx_invoice_total__c, ocrx_invoice_date__c) and flag that the customer should evaluate Pipedrive's billing integrations or a dedicated invoicing tool post-migration if invoice tracking inside the CRM is required.

openCRX Products with bundles and design-to-order configurations map to Pipedrive Products. openCRX run-time pricing rules and multi-currency price lists are flattened into Pipedrive Product prices; we capture the base currency price and note any multi-currency variants in a custom field ocrx_additional_currencies__c for the customer's admin to configure in Pipedrive's multi-currency settings.

openCRX Activities are first-class objects with time-tracking and Activity Tracker grouping. We map call activities to Pipedrive call Activities, email activities to Pipedrive email Activities, meeting activities to Pipedrive meeting Activities, and task activities to Pipedrive task Activities. openCRX Activity Tracker grouping (which associates multiple activities under a single theme or campaign) cannot be reproduced natively in Pipedrive; we document the tracker groupings in a written handoff and the customer's admin can recreate them as Pipedrive labels or custom tag fields.

openCRX Notes attach to objects as CrxObject attributes. We migrate note title and body to Pipedrive Notes linked via the activity reference to the parent Person, Organisation, or Deal. If the note contains embedded binary content, we extract the text and flag the attachment for manual re-upload in Pipedrive's file section.

openCRX Workflow Processes are segment-scoped infrastructure objects that are not standalone data records and cannot be exported and re-imported. We do not migrate them. During scoping we enumerate every openCRX Workflow Process definition and deliver a written inventory with its trigger conditions, actions, and a recommended Pipedrive Workflow Automation equivalent. The customer's admin rebuilds them in Pipedrive's Automation editor (available from Advanced plan).

openCRX Topics drive email notifications based on object lifecycle events and are tightly bound to the running openCRX instance. We do not migrate them. We document every active Topic subscription with its trigger object, event type, and notification target and deliver this as part of the automation handoff for the customer's admin to implement as Pipedrive Workflow Automation triggers or email notification rules.

Custom fields defined via openCRX DataBinding PropertySet are feature definitions in the UI customising layer, not data records. We enumerate all active PropertySet attributes during scoping, identify their bound object and data type, and deliver a custom field creation checklist for Pipedrive. The customer's admin creates the corresponding custom fields in Pipedrive before migration begins. We do not create Pipedrive custom fields programmatically as that requires the customer's Pipedrive admin credentials and direct API access.