Migrate from OplaCRM to Pipedrive

OplaCRM Accounts map directly to Pipedrive Organizations. We deduplicate by account name and external_id where present. Address data on the Account maps to Pipedrive's address compound field. Owner assignment resolves by matching the OplaCRM owner email to a Pipedrive User email.

OplaCRM Contacts map to Pipedrive People with email as the primary deduplication key. Role fields map to a custom text field if the customer's Pipedrive instance uses person-role tracking. The contact-to-account link migrates via Organization external_id matching so each Person is correctly associated with its Organization at import time.

OplaCRM Opportunities map to Pipedrive Deals. Stage maps via display label (not internal enum) to prevent CLOSE_WON and CLOSE_LOST landing in the wrong terminal stage bucket. Close date, close reason, and win/loss status migrate to standard Pipedrive Deal fields. We update existing Deals in Pipedrive when an external_id match is found rather than creating duplicates.

Stage names in OplaCRM are stored as plain string enums in the sale_process_stage field. We map by display label during scoping so that the OplaCRM stage sequence maps to the correct Pipedrive pipeline stage order. Pipedrive's visual pipeline stages are pre-created in the destination account before migration begins, with stage probabilities set to match OplaCRM's close probability values where present.

OplaCRM Products are line items attached to Opportunities. We map product name and quantity directly. Pricing may need review if OplaCRM stores list price differently from Pipedrive's price book model. If the customer's OplaCRM instance uses a dedicated price book, we provision Pipedrive Products and Standard Price Book entries during the pre-flight phase.

OplaCRM Invoices are created within the Opportunity context. Pipedrive does not have a native invoice generation object at the Deals layer on all tiers. We migrate invoice amount, date, status, and number as custom fields on the Deal, and attempt to attach the invoice PDF if it is stored as a file attachment in OplaCRM. Invoice numbering schemes require explicit remapping if the destination Pipedrive account uses a specific numbering format.

OplaCRM's healthscore is a composite numeric signal per Account and Contact. Pipedrive has no native healthscore feature. We preserve the numeric value as a Pipedrive custom field (numeric type) and document the original value for the customer's admin to use as a reference when rebuilding scoring logic via Pipedrive automations or custom logic post-migration. The opaque algorithm cannot be replicated without OplaCRM documentation.

OplaCRM's locked boolean flag prevents edits on every record type. Pipedrive does not have a record-level lock feature. We replicate the lock flag as a custom property (opla_locked: true) on each affected record and surface the full list in the post-migration handoff. The customer's admin reviews and sets the appropriate read-only permissions in Pipedrive based on this list.

Tags in OplaCRM are stored as label arrays on records. We map them to Pipedrive Labels. Any comma-delimited tag strings in OplaCRM are split into individual label entries. Labels in Pipedrive are available from the Essential tier and appear on the Person, Organization, and Deal detail views.

Attachments are referenced by URL or file ID in OplaCRM. We attempt to download and re-upload files to Pipedrive's attachment storage on the associated Organization, Person, or Deal. Large binary attachments may require extended migration windows. We flag any attachments that cannot be resolved from the source URL for the customer's manual review.

OplaCRM Users carry name and role. We map by email address to match owner assignments on Accounts, Contacts, and Opportunities. Any OplaCRM User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record migration resumes.

OplaCRM uses a UUID field (opportunities_joint_id) to link joint or co-selling opportunities. Pipedrive has no native linked-deals concept. We write each joint relationship as a custom field (opla_joint_opportunity_id) carrying the UUID of the linked opportunity, and include the full joint-relationship table in the post-migration handoff. The customer's admin decides whether to handle joint opportunities as linked Deals manually or via a custom Pipedrive app.