Migrate from Oracle CRM On Demand to Pipedrive

Oracle Accounts map directly to Pipedrive Organizations. Oracle account name, address records, industry, phone, website, and ownership fields map to their Pipedrive Organization equivalents. We normalize address formats during import and use Organization name as the dedupe key. Account hierarchies (parent-child relationships) in Oracle map to Pipedrive Organization hierarchy if the customer's Oracle implementation uses them.

Oracle Contacts map to Pipedrive People with name, email, phone, title, and address fields preserved. Contact-to-Account linking in Oracle maps to the Person's Organization link in Pipedrive. We resolve the Organization reference before inserting People to satisfy Pipedrive's required Organization link on Person records. Email serves as the dedupe key to flag duplicate contacts before insert.

Oracle Leads require a qualification decision before mapping. Leads with status indicating early-stage unqualified prospects (New, Open, In Progress) map to Pipedrive People without a Deal association. Leads with a clear opportunity interest and estimated value map to Pipedrive People linked to a Deal in the relevant pipeline stage. We apply the split rule from the customer's Oracle Lead status matrix during transformation. Note: the Enterprise Lead Referral tier restricts lead access to create-only, which we flag during discovery and handle by extracting via the Contact object if lead history is accessible there.

Oracle Opportunities map to Pipedrive Deals with pipeline stage, revenue amount, probability, expected close date, and opportunity name preserved. Oracle's Opportunity-Account linking maps to Deal-Organization. We configure Pipedrive pipeline stages during schema setup to match the Oracle opportunity stage sequence. Closed-Lost and Closed-Won outcomes from Oracle map to Pipedrive lost and won Deal status.

Oracle Tasks map to Pipedrive Activities attached to the relevant Person or Deal via the WhoId and WhatId resolution. Task Subject becomes the Activity subject, Status maps to done/pending, Priority maps to priority flag, and the original Oracle ActivityDate is preserved. Activities are imported after Organizations, People, and Deals so that all parent-record lookups resolve at insert time.

Oracle Call records (an Activity type with disposition, duration, and notes) map to Pipedrive Activities with call type flagged. Call duration and outcome from Oracle migrate as custom activity fields in Pipedrive if the customer's Pipedrive plan supports custom activity fields. The Call notes field becomes the Activity note body.

Oracle Appointments (meetings with start time, end time, location, and attendees) map to Pipedrive Activities with a meeting flag. If the customer uses Google Calendar or Outlook integration with Pipedrive, we map to Pipedrive's calendar event structure so that meeting records sync bidirectionally post-migration. Attendee lists from Oracle map to the Activity's linked Person records.

Oracle Custom Objects do not have a direct Pipedrive equivalent since Pipedrive has no native custom object support. We reverse-engineer the Oracle custom object schema during discovery, then map each custom object's fields to custom fields on the most relevant Pipedrive object (Organization, Person, or Deal). Picklist values from Oracle become drop-down or radio button custom fields in Pipedrive. Complex multi-level Oracle custom object hierarchies require decomposition into flat custom field sets with a written mapping diagram for the customer.

Oracle Named Users map to Pipedrive Users by email address. We extract every distinct Owner referenced on Account, Contact, Opportunity, and Activity records and match by email against the Pipedrive destination Users. Any Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Oracle users map to inactive Pipedrive users if historical ownership must be preserved.

Oracle record attachments (file blobs and URL-based links) migrate to Pipedrive as Files attached to the parent Organization, Person, or Deal. URL-based attachments from Oracle migrate as external link fields on the Pipedrive record. Blob attachments migrate by downloading from Oracle's attachment API endpoint and uploading to Pipedrive's file storage via the Files API. Attachment volumes are scoped separately because they affect migration duration and storage estimates.