Migrate from Oracle Siebel to Odoo CRM

Siebel Organization records map to Odoo res.partner with type=company. We extract S_PARTY.ROW_ID as the dedupe key and carry it into a custom field x_siebel_party_id on the Odoo partner for audit traceability. Organization name, address, industry, and primary contact fields map to the corresponding Odoo res.partner fields. Multi-company Siebel deployments with separate business unit Organizations map to separate Odoo company partners; Odoo's multi-company security model can be configured to enforce data isolation per partner if the customer requires it.

Siebel Contact records map to Odoo res.partner with type=contact. Each Contact's S_CONTACT.PAR_BU_ID is resolved to the parent Organization's S_PARTY.ROW_ID, which we use to look up the previously migrated company res.partner and set parent_id on the contact partner. Contacts without a parent Organization link in Siebel are migrated as individual res.partner records with type=individual. Name, email, phone, function, and custom extension fields migrate directly. The original S_PARTY.ROW_ID is preserved in x_siebel_party_id on each contact partner.

Siebel Opportunities map to Odoo crm.lead records. The Siebel pipeline stage maps to an Odoo stage within the CRM pipeline, with the stage name and probability preserved. Revenue amounts map to Odoo's expected_revenue and planned_revenue fields. The Opportunity-Account link resolves to the migrated res.partner parent_id. Stage history from Siebel's Pipeline Stage tracking migrates as Odoo lead kanban stage transitions with dates preserved in the lead's history. Closed-Lost and Closed-Won outcomes from Siebel map to Odoo's lost and won stage states respectively.

Siebel Quote header (S_DOC_QUOTE) maps to Odoo sale.order in draft or sent state depending on Siebel quote status. Quote line items (S_QUOTE_ITEM) map to sale.order.line with product, quantity, and pricing. The Quote-to-Order linkage in Siebel (for quotes converted to orders) maps by matching Siebel order number to Odoo sale.order origin field. Quote status in Siebel—Draft, Active, Accepted, Lost—is preserved in a custom field x_siebel_quote_status on the sale.order. Accepted Siebel quotes that correspond to Odoo sale orders carry the order number in the origin field.

Siebel Orders map to Odoo sale.order records. Order header fields (S_ORDER) map to sale.order fields: order number, order date, partner_id (resolved to the Organization res.partner), shipping address, and total amount. Order items (S_ORDER_ITEM) map to sale.order.line with product, quantity, unit price, and taxes. Document attachments from S_ORDER_DOC migrate as ir.attachment records linked to the sale.order. The Account link and Quote link are preserved as a custom field and the origin field respectively.

Siebel Service Request (S_SRV_REQ) records map to Odoo helpdesk.ticket. Case status, priority, category, and assignment fields migrate to the corresponding Odoo ticket fields. The assigned Position or Employee from Siebel is resolved to an Odoo res.users record by email match and mapped to the ticket's user_id. Case-related Activities (S_EVT_ACT with type SR) migrate as mail.message records linked to the helpdesk.ticket. The ticket description field carries the Siebel SR description text. Customers on Odoo plans without Helpdesk can opt to map Cases to crm.lead instead.

Siebel Activities (calls, emails, meetings, tasks) map to Odoo mail.message records linked to the parent Contact res.partner or Organization res.partner. Activity type, date, owner, duration, and outcome migrate as mail.message fields or custom fields on the message. Meetings with attendees link to mail.activity records. The parent record resolution uses the Siebel Contact's S_PARTY.ROW_ID mapped to the migrated res.partner x_siebel_party_id to locate the correct Odoo partner. Activity ordering is preserved by setting mail.message.date to the original Siebel timestamp.

Siebel Literature metadata (S_LIT) migrates as Odoo ir.attachment records. We extract the file path from S_LIT.PATH, retrieve the corresponding binary file from the Siebel File System, and deliver it as a base64-encoded payload for Odoo attachment re-upload. The literature name and type map to ir.attachment.name and ir.attachment.type. Literature is typically linked to the parent Account or Opportunity in Odoo. If the customer has Odoo Documents installed, we can link literature to the Odoo Documents app for organized content management.

Siebel Financial Assets (S_ASSET) represent installed products or holdings linked to an Account. If Odoo Inventory is in scope, assets migrate as product.product records with type=product and tracked by serial number (stock.quant). If only Odoo CRM is in scope, assets migrate as custom res.partner fields on the Organization partner. Asset linked to S_ORG_EXT is resolved to the migrated res.partner by x_siebel_party_id.

Siebel Positions (S_POSTN) represent organizational roles and control record visibility through Siebel's position-based access control. Positions migrate as hr.employee records in Odoo with the position name as employee name. The position hierarchy (parent-child S_POSTN relationships) can be mapped to Odoo's department structure if Odoo Employees is in scope. User-to-Position assignments in Siebel (S_USER_POSTN) require manual reconciliation: the customer's Odoo admin provisions res.users accounts and assigns employee records post-migration. This mapping is configuration-dependent on whether Odoo Employees is active.

Siebel custom extension tables built atop Siebel's extension table pattern require per-table analysis. We inspect each S_* EXTENSION table's foreign keys, column types, and SRF-compiled field definitions, then map them to Odoo res.partner custom fields (x_* columns created via Odoo Studio or Python) or to new Odoo model columns if the extension represents a distinct object type. Custom extension tables referencing S_PARTY are the most common and map cleanly as custom fields on the res.partner. We deliver a written extension table inventory with column-level mapping and Odoo field type recommendations.

Siebel Financial Services Holdings (S_FN_HLDNG) represent financial instrument positions linked to Financial Accounts (S_ASSET). If Odoo Accounting is in scope, holdings migrate as account.move.line records tied to a financial account res.partner. If Odoo CRM only is in scope, holdings migrate as custom fields on the related Account res.partner. This mapping depends on the customer's Odoo module scope and whether Odoo Financial services-specific configuration is required.

Siebel's EAI integration layer—including EAI adapters, business services, SOAP/REST connectors, and inbound/outbound web services—is tightly coupled to the Siebel runtime environment and stored in the Siebel repository. These cannot be exported as portable data and do not migrate. We deliver a written inventory of every Siebel integration endpoint, its data flow direction, and the recommended Odoo replacement approach (native Odoo integration, third-party connector, or custom XML-RPC/XML-RPC/JSON-RPC development). The customer's integration team rebuilds these post-migration.

Siebel Workflow Processes are stored in the Siebel repository (SRF) and define business process automation including approval chains, data propagation rules, and process-driven UI. These are not portable data and do not migrate to Odoo. We deliver a written workflow inventory documenting every active Siebel Workflow Process with its trigger conditions, process steps, and a recommended Odoo equivalent (Odoo Studio automation, server action, or computed field). The customer's Odoo administrator or an Odoo implementation partner rebuilds these as part of the post-migration configuration scope.