Migrate from OrangeCRM to Pipedrive

OrangeCRM Customers (the primary account-level object) map to Pipedrive Organizations. Customer name becomes Organization name; domain, address, and custom account-level fields migrate to Organization custom fields. We use Organization name as the dedupe key during import and resolve the Organization ID before importing any related Contacts, so that the Organization lookup is satisfied at the moment of Contact insert.

OrangeCRM Contacts export cleanly with standard fields (name, email, phone, address) and map 1:1 to Pipedrive Persons. Multi-value phone and email fields are split into the primary phone/email and additional phone/email fields. Contact-to-Organization linkage is resolved via the Customer ID mapping to Pipedrive Organization ID.

Fulfillment records track subscription or order fulfillment status tied to OrangeCRM Customers. Since Fulfillment has no direct Pipedrive equivalent, we map each Fulfillment record to a Pipedrive Deal, preserving fulfillment status, fulfillment date, and any proprietary OrangeCRM fields as custom Deal fields. One Customer can generate multiple Deals (one per Fulfillment), creating a 1:N relationship from Organization to Deals. Customers must validate that business logic embedded in fulfillment-specific stages is correctly interpreted as Pipedrive Deal stages.

OrangeCRM Help Desk tickets with status, priority, assignee, and conversation history map to Pipedrive Deals tagged with a ticket-type label. Conversation threads are preserved as Activity notes on the Deal. Pipedrive's optional Service Desk add-on (available on Advanced and above) provides a native ticket object; if the customer enables it, we remap tickets to the Pipedrive ticket object in a post-enablement phase. Without the add-on, tickets land as Deals to avoid data loss.

OrangeCRM email campaign subscriber lists and opt-in dates have no direct Pipedrive equivalent. We preserve subscriber opt-in dates and campaign engagement metrics as custom Person fields. Email campaign membership is preserved as a multi-select picklist on Person. Pipedrive's separate Email Marketing product or third-party integration handles ongoing email campaigns post-migration.

Storefront orders and product records map to Pipedrive Deals (for the order) and Products (for the line items). Order totals, fulfillment status, and proprietary product IDs migrate to Deal custom fields and Product records. We flag any OrangeCRM product variants and map them to Pipedrive Product variants if the customer uses Advanced tier or above.

OrangeCRM Banking module records for payment or ledger tracking map to Organization custom fields on the related Customer-Organization record. Multi-currency handling is flagged as a custom field requirement, and any currency conversion metadata is preserved in a text field for the customer's finance team to reconcile. Pipedrive does not have a native accounting object; banking records are stored as reference data, not transactional accounting.

Event registrations and attendee records in OrangeCRM map to Pipedrive Activities (for the event) with attendee status, session selections, and custom event fields preserved as custom Person fields on the related Contact-Person record. Multiple attendees for the same event are merged into a single Activity with multiple ActivityPerson records. Session and registration-type data migrates as custom Activity fields.

OrangeCRM custom fields per module are extracted from the export schema and generated as Pipedrive custom fields on the equivalent object (Organization, Person, or Deal) during the mapping phase. Field types are matched: text to text, number to number, date to date, checkbox to checkbox. Pipedrive creates custom fields automatically during the import mapping step if the customer selects that option, or we pre-create them via the API before import begins.

File attachments on OrangeCRM records export as URL references or binary blobs. We preserve the original attachment URL in a custom Deal or Person field as a reference link. If OrangeCRM attachments are downloadable, we download and re-upload to Pipedrive using the Pipedrive Files API, attaching each file to the migrated record it was associated with in OrangeCRM.

OrangeCRM user accounts and record owners map to Pipedrive Users. We resolve owners by email match. Any OrangeCRM owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Orphaned assignments are flagged in the migration report with a list of records that need owner reassignment.