Migrate from Oracle Siebel to Freshsales

Siebel Organizations map to Freshsales Accounts. Both S_ORG_EXT and S_PARTY row IDs are extracted during the party-first pass; we create the Freshsales Account record and store the original S_PARTY ROW_ID as a custom field siebel_party_row_id__c for audit and cross-reference. Siebel's Organization type (House Account, Competitor, Partner) maps to a Freshsales Account custom field rather than a separate record type, since Freshsales does not have a built-in Organization type taxonomy.

Siebel Contacts map to Freshsales Contacts. Each S_CONTACT record requires its parent S_PARTY row to exist in the destination before the Contact is created. We run S_PARTY as a separate first-pass import, then S_CONTACT as the second pass, cross-referencing the S_PARTY ROW_ID to the Freshsales Contact record ID. Any Contact without a corresponding S_PARTY record is flagged as a dangling child and held for manual resolution before the Contact import phase completes.

Siebel Opportunities map to Freshsales Deals. The Opportunity-Account link migrates by resolving the Siebel Account's S_ORG_EXT ROW_ID to the Freshsales Account ID during import. Revenue amounts, close dates, pipeline stage names, and probability percentages transfer directly. Siebel's Opportunity-Contact links map to Freshsales Deal Contact roles.

Siebel pipeline stages map to Freshsales Deal stages. We extract the stage names and probability values from S_OPTY and S_STAGE, then configure matching stage values in Freshsales Deal Stages before migration. The stage ordering is preserved as a custom field siebel_stage_order__c for reporting continuity.

Siebel Quotes map to Freshsales Quotes. Quote headers from S_DOC_QUOTE and line items from S_QUOTE_ITEM migrate as a parent-child set. Quote-to-Order linkage from S_DOC_ORDER is preserved in a custom field siebel_order_ref__c on the Freshsales Quote. Quote status and expiration dates transfer directly. Freshsales Quotes do not support multi-level line item hierarchies, so nested Siebel quote item structures are flattened to a single level.

Siebel Orders do not have a direct Freshsales equivalent. We map Siebel Orders to Freshsales Deals with Products. Order headers become Deal records with a custom field siebel_order_id__c and siebel_order_date__c. Order line items from S_ORDER_ITEM become Deal Product entries. The Quote-to-Order linkage is preserved as a siebel_quote_ref__c field on the Deal. If the customer requires order history visibility, we recommend Freshsales + Freshdesk integration post-migration to handle the order management gap.

Siebel Service Cases map to Freshsales Deal records with a custom Deal type for service. We extract case number, status, priority, assigned employee, and description. Case-to-Contact links are preserved as Deal Contact roles. For organizations requiring full case management capability, we document the Freshdesk Service Cloud integration as a post-migration step because Freshsales CRM does not include native case management.

Siebel Activities (S_EVT_ACT) map to Freshsales Activities (tasks and events). We extract activity type, subject, date, owner, and the parent Contact or Account reference. Notes from S_NOTE migrate as Freshsales Notes linked to the corresponding Contact or Account. Custom Activity extension fields are preserved as custom Freshsales activity fields. Siebel's activity history ordering is preserved by setting the Freshsales activity timestamp to the original Siebel date.

Siebel Financial Assets from S_ASSET link to the parent Account. We migrate Asset records as a custom Freshsales Contact or Account field group (asset name, product, serial number, quantity, status). For organizations with complex asset tracking, we recommend a Freshdesk Asset management integration post-migration because Freshsales CRM does not include a native Asset object.

Siebel Literature metadata from S_LIT migrates as Freshsales Notes with the file path and name preserved. The actual binary document files stored in the Siebel File System require separate file system extraction and re-upload. We extract the path list from S_LIT, package the referenced files, and deliver them alongside the migration package for the customer's Freshsales admin to re-upload manually. We do not migrate the Siebel repository or .SRF file that contains the Literature configuration.

Siebel custom fields built atop the extension table pattern (tables with TYPE like EXTENSION or custom columns added to S_CONTACT, S_ORG_EXT, etc.) are migrated on a per-table basis. We export the extension table data, map its foreign keys to the target Freshsales object, and create corresponding custom fields in Freshsales via Settings. Fields that reference other S_ tables require those tables to be migrated first. If a Siebel administrator has added columns via Siebel Tools, those columns require SRF recompilation in the source environment before the new columns appear in REST API queries.