Migrate from Oracle EBS CRM to Pipedrive

Oracle Accounts are stored in the ARHZTARZ base tables and exposed through the APPS schema. We extract account_name, account_number, status, and the primary party site address. The account maps directly to a Pipedrive Organization record using account_number as the dedupe key during import. Party site addresses (HZ_PARTY_SITES) are parsed into Pipedrive address fields on the Organization. Multi-org Oracle EBS installations require scoping by OPERATING_UNIT to avoid duplicating accounts across orgs in a single Pipedrive tenant.

Oracle EBS Contacts reside in base HR schemas (PER_ALL_ASSIGNMENTS_F for employees) or AR schemas (HZ_PARTIES for external parties) depending on the party type. We identify the correct schema at discovery time, extract full name, email, phone, and the party_site_address, and map to Pipedrive Person records. The link between Person and Organization is resolved at migration time by matching the Organization's party_id to the Contact's related_party_id in Oracle. Any Contact without a matching Organization is held in a reconciliation queue for the customer to resolve before final import.

Opportunities in Oracle EBS CRM are stored in the CZ (Collaborative Selling) base tables for modern installations, or the deprecated ASF schema for older CRM module versions. We identify the correct schema at discovery, extract opportunity_name, amount, currency_code, probability, close_date, and stage. Stage values from CZ are mapped to Pipedrive pipeline Stages during transformation. Owner resolution uses FND_USER email matching against the Pipedrive User list. Multi-currency amounts are preserved in a custom field and converted to the customer's Pipedrive base currency for pipeline value reporting.

Sales Activities and Tasks are stored across multiple EBS CRM schemas — the deprecated Teleservice tables or the modern Interaction Center tables — depending on which CRM module is installed. We identify the source schema during discovery, extract activity_type, subject, description, start_date, and status, and map to Pipedrive Activity records of the corresponding type (call, meeting, task, deadline). The activity owner maps via FND_USER email lookup. Closed_date and outcome are preserved in activity notes or custom fields.

Notes and audit history in Oracle EBS CRM are stored in generic note tables (FZ_NOTES or equivalent) or in the application-level audit trail. We extract note text, created_by, and creation_date as a Note body linked to the parent record (Account, Contact, or Opportunity) via a lookup resolution step. If the parent record is not yet created at note migration time, we stage notes by parent_type and parent_id and link after parent resolution.

Oracle EBS Users are sourced from the HR schema (PER_ALL_ASSIGNMENTS_F) with CRM-specific responsibilities assigned via FND_RESPONSIBILITIES. We extract user_name, email, and employee_number from FND_USER and map to Pipedrive Users. FND_RESPONSIBILITY records are parsed to identify which users have CRM-specific roles, and those are prioritized for active Pipedrive User provisioning. Any EBS user without an email address requires manual assignment in Pipedrive.

Oracle EBS CRM Custom Objects are stored in user-defined tables within base product schemas, often with FK columns pointing to RA_CUSTOMERS or OE_HEADERS. We extract the DDL for each custom table during discovery, map the custom columns to Pipedrive Custom Fields on the relevant standard object (Organization, Person, or Deal), and handle data type translation (VARCHAR to string, NUMBER to int/float, DATE to date). Pipedrive does not support standalone custom objects; all custom data maps as fields on standard objects. Multi-select picklist values in Oracle EBS map to Pipedrive multi-select custom fields.

Territory definitions in Oracle EBS CRM are stored in AS_TERRITORIES base tables with hierarchical org structures and assignment rules. Pipedrive does not have a native Territory hierarchy or assignment engine. We flatten the Oracle Territory hierarchy into Pipedrive Labels (one per top-level territory) and create a custom territory_name field on Deals to carry the full Oracle territory path. Territory assignment rules (which reps are assigned to which territories) are documented in the handoff report for the customer's admin to rebuild using Pipedrive's Team features or a third-party territory management app.

Attachments in Oracle EBS CRM are stored as LOB data (BFILE or CLOB columns in the database) or on the file system depending on the attachment configuration. We extract binary attachments as BASE64-encoded blobs and upload them to Pipedrive as Files linked to the parent record (Organization, Person, or Deal). The original filename and MIME type are preserved from the FND_LOBS table. Attachments exceeding Pipedrive's file size limits are flagged and delivered as downloadable archives alongside the migration package.

Oracle EBS Product data (from the Product Information Management tables, if the CRM module includes product catalog access) maps to Pipedrive Products. We extract product_name, product_code (hs_sku equivalent), list_price, and description. Pipedrive Products are created during the import phase and linked to Deals via the deal-product association API endpoint. Products without a pricebook in Pipedrive are created with a default pricebook entry.

Oracle EBS CRM may contain prospect records in the CZ schema or a dedicated lead module depending on the CRM version installed. These map to Pipedrive Leads, which share the same field structure as Pipedrive Deals (pipeline and stages). We extract lead_name, status, source, and owner, and map to the Pipedrive Lead object using the customer's specified pipeline. Unqualified leads that should not enter the sales pipeline are flagged in the mapping for manual review.

Oracle EBS stores Contact-to-Account relationships in HZ_RELATIONSHIPS with relationship_type and direction flags. We extract these relationships and map them to Pipedrive Person-Organization associations using the party_id and related_party_id from the relationship table. Primary Contact flags in Oracle EBS map to a custom is_primary__c field on the Pipedrive Person record. Relationship roles (purchasing contact, technical contact, billing contact) are mapped to custom fields on the Person.