Migrate from Oracle Siebel to Salesforce Sales Cloud

Siebel's party-based architecture roots every Organization and Contact in the S_PARTY base table. We extract S_PARTY rows first in any migration pass, preserve the original ROW_ID as a custom field (siebel_party_id__c) on both the resulting Salesforce Account and Contact, and use this as the foreign-key anchor for all child extension table imports. Skipping this step causes foreign-key violations on S_CONTACT and S_ORG_EXT because their PARTY_ID column references a row that does not yet exist.

Siebel Organizations (Accounts) live in S_ORG_EXT with a required FK to S_PARTY.PARTY_ID. We migrate the S_PARTY row first, then S_ORG_EXT with the siebel_party_id__c anchor, mapping Name to Account Name, Location to Billing City, and any industry classification to a custom industry picklist. Parent-child organizational hierarchies in Siebel (ORG_INT_ID referencing the parent Organization) map to Salesforce Account Hierarchy if the customer uses that feature.

Siebel Contacts extend S_PARTY via PARTY_ID and carry profile data in S_CONTACT. We migrate the S_PARTY row first, then S_CONTACT, and link the Contact to the resolved AccountId via the S_ORG_EXT anchor. Fields like Job Title, Email Address, Phone, and Mailing Address map directly. Any S_CONTACT extension columns (custom fields on the Siebel contact buscomp) are mapped to Salesforce custom fields on Contact.

Siebel Opportunities track Deals through Pipeline Stages. We extract the opportunity record, its Stage (which maps to Salesforce StageName), Revenue amounts, Close Date, and the Opportunity-to-Account link (OPTY_ID to S_ORG_EXT). Stage history and probability percentages migrate as Opportunity History records or a custom stage-history object depending on the customer's reporting needs.

Siebel Quotes (S_DOC_QUOTE) map to Salesforce Quote, available from Sales Cloud Professional. Quote header fields (Quote Number, Status, Effective Date, Expiration Date) migrate directly. Quote Line Items from S_QUOTE_ITEM map to Salesforce QuoteLineItem with PricebookEntry resolved from the Product2 lookup. The Quote-to-Opportunity linkage (OPTY_ID) migrates as the Salesforce Quote's OpportunityId lookup.

Siebel Orders (S_ORDER) map to Salesforce Order when the customer enables Salesforce Order Management. The Order header migrates with Order Number, Status, Effective Date, and AccountId resolved from the Siebel Account anchor. Order Items from S_ORDER_ITEM map to OrderProduct2 records. We preserve the S_ORDER-to-S_DOC_QUOTE linkage (DOC_ID) as a custom field on the Salesforce Order for audit traceability.

Siebel Service Cases map to Salesforce Case if Service Cloud is included in the destination. We extract the case record, its Status, Priority, Owner (Position/Employee), and any related Activity logs. The Siebel case-to-contact link (SR_BU_ID and SR_CONTACT_ID) resolves to Salesforce Case.ContactId. Custom escalation fields from Siebel extension tables map to Salesforce custom Case fields.

Siebel Activities (Tasks, Meetings, Calls) map to Salesforce Task and Event. TaskType, Activity Date, Owner (Employee), and the parent Contact or Account link migrate directly. We resolve the WhoId (Contact) and WhatId (Account or Opportunity) from Siebel's PARTY_ID and OPTY_ID anchors respectively. Duration, location, and status preserve. The Siebel activity type column distinguishes Task from Event in the destination.

Siebel Financial Assets map to Salesforce Asset. We extract the asset record, its relationship to the parent Account (via siebel_party_id__c anchor), and any custom asset extension columns. Serial number, product name, status, and installation date migrate to the equivalent Salesforce Asset fields.

Literature records in Siebel store metadata (name, type, URL/path reference) in S_LIT, but the binary document files live in the Siebel File System and are not included in the database export. We extract the S_LIT metadata, identify the file paths, package the corresponding files from the Siebel File System, and deliver them alongside the migration export for re-upload to Salesforce Files (ContentDocument/ContentVersion). This step requires the customer to provide file system access.

Holdings from Siebel Financial Services (S_FN_HLDNG) link to Financial Accounts (S_ASSET). The holding structure varies by Siebel industry pack (telecom, banking, insurance). We map generic holding fields to a Salesforce custom object (Holding__c) with a lookup to the Asset record. Industry-specific fields require custom mapping during scoping.

Siebel custom extension tables (any S_ table with TYPE='EXTENSION') carry business data added via Siebel Tools. We export each extension table, map its foreign keys to the siebel_party_id__c anchor on the parent Account or Contact, pre-create equivalent custom objects in Salesforce (with __c suffix and matching field types), and import the data with all lookups resolved. SRF recompilation is a post-import customer-admin step if the Siebel schema is still live.