Migrate from Oracle Siebel to Pipedrive

Siebel Accounts span S_PARTY (root Party row) and S_ORG_EXT (organization extension). We export S_PARTY first, resolve the PARTY_ID as the dedupe key, then import S_ORG_EXT as Organization. Account Name, Location, and Industry map to Pipedrive Organization name and custom fields. Siebel's parent-account hierarchy maps to a Pipedrive custom Organization field if a hierarchical view is needed; Pipedrive does not support nested organization hierarchies natively.

Siebel Contacts span S_PARTY (root) and S_CONTACT (extension). We import S_PARTY first to satisfy the foreign key, then S_CONTACT as a Pipedrive Person record. Contact Name, Email, Phone, and Title map directly. Siebel's Contact-to-Account link resolves to a Pipedrive Person-Organization association during import. Custom S_CONTACT extension fields migrate as Pipedrive Person custom fields.

Siebel Opportunities map directly to Pipedrive Deals. The Opportunity Name becomes Deal title; Close Date, Value, and StageName map to Pipedrive close date, value, and pipeline stage. Siebel's Pipeline Stage history (multiple rows per opportunity) collapses into a single Deal record with the most recent stage as the current Pipedrive stage. Stage probability migrates to Pipedrive's optional probability field per stage.

Each Siebel Pipeline Stage becomes a Pipedrive Stage within the equivalent pipeline. Siebel stage probability percentages migrate as Pipedrive stage probability values. Stage names and order are preserved during configuration. Siebel's Loss Reason and Win Reason (custom properties on Opportunity) become Pipedrive custom fields on Deal.

Siebel Service Requests do not have a direct Pipedrive equivalent. We configure a dedicated service pipeline in Pipedrive and map Siebel Cases to Deals in that pipeline. SR status, assigned Position, priority, and resolution date migrate as Deal fields. SR number becomes a Deal custom field for cross-reference. Open and closed status maps to Pipedrive open/closed Won/Lost state using a status mapping rule defined at scoping.

Siebel Activities map to Pipedrive Activities by type: Call, Email, Meeting, and Task. The parent Contact or Account link resolves to a Pipedrive Person or Organization association. Activity date, owner, and duration transfer directly. Siebel's activity type codes are mapped to Pipedrive's five supported activity types; custom Siebel activity extension fields migrate as custom activity fields. Activity notes migrate as Activity notes.

Siebel Quotes (S_DOC_QUOTE) have no direct Pipedrive equivalent. We migrate Quote header fields (quote number, date, total value, status) as Pipedrive Deal custom fields. Quote line items (S_QUOTE_ITEM) migrate as Deal product items if Pipedrive Products are configured; otherwise they become a Deal notes section with line-item text. Signed quote PDFs export from the Siebel File System and attach to the Deal as a Pipedrive file.

Siebel Orders (S_ORDER) have no native Pipedrive equivalent. We migrate Order header fields (order number, date, total) as Deal custom fields. Closed-won Orders map to Pipedrive Deals with status Won; the order total becomes the Deal value. Order line items migrate as Deal product items if Products are configured. Order documents attach as files to the Deal.

Siebel Assets (S_ASSET) representing installed products or financial holdings migrate as Pipedrive Products with a custom field flagging asset origin. Asset serial number, product name, quantity, and status migrate to Pipedrive Product fields. The Account link on S_ASSET resolves to a Pipedrive Organization during import. Product pricing is set as Standard Price Book entries in Pipedrive.

Siebel Literature records (S_LIT) store document metadata and a file system path reference. The binary files are not in the database. We extract the S_LIT path list, retrieve the corresponding files from the Siebel File System, and deliver them alongside the data export for re-upload as Pipedrive file attachments linked to the parent Organization or Deal record.

Siebel custom tables built atop S_ extension patterns migrate as Pipedrive custom fields on the equivalent standard object. We export each extension table, map its foreign keys to the parent S_PARTY or S_CONTACT row ID resolved during earlier import passes, and create Pipedrive custom fields with matching data types before loading the values. The mapping workbook documents the full extension field inventory for the customer's Pipedrive admin to review.