Migrate from Oracle Siebel to Zoho CRM

Every Siebel Account, Contact, and Organization record depends on a corresponding S_PARTY row as its root primary key (PAR_ROW_ID). We extract S_PARTY as the first pass in every migration, preserving the PARTY_UID as the dedupe key and ROW_ID as the parent reference. No Zoho record is created from S_PARTY directly; it is a prerequisite table that all subsequent passes reference. This sequencing is mandatory—attempting to import S_CONTACT or S_ORG_EXT before S_PARTY causes foreign-key violations at the Siebel layer.

Siebel Accounts (S_ORG_EXT) map to Zoho CRM Accounts. The S_PARTY ROW_ID is preserved in a custom field siebel_party_row_id__c for audit traceability. Account Name, Location, Industry, Annual Revenue, and Number of Employees map to their Zoho equivalents. Siebel's multi-address structure (S_ADDR_PER and S_ADDR_ORG) is consolidated into a single Zoho Account address with primary address priority from Siebel's addr_name priority field.

Siebel Contacts (S_CONTACT) map to Zoho CRM Contacts. The S_PARTY ROW_ID becomes siebel_party_row_id__c on the Zoho Contact. We resolve the S_CONTACT.PAR_PARTY_ID reference back to the S_PARTY row to establish the Account link in Zoho. Email, Phone, Title, Department, and custom extension columns on S_CONTACT map to their Zoho equivalents. Contact Owner maps by email lookup against Zoho Users.

Siebel Opportunities (S_OPTY) map to Zoho CRM Deals. The opportunity name, amount, close date, probability, and pipeline stage migrate directly. Siebel's pipeline stage becomes the Zoho Deal Stage, with stage probability percentages mapped to Zoho probability values. The S_OPTY.PAR_BU_ID and S_OPTY.PAR_PARTY_ID references resolve to the corresponding Zoho Account and Owner at import time.

Siebel Quotes (S_DOC_QUOTE with S_QUOTE_ITEM) are complex multi-entity records. Zoho CRM Standard does not include a native Quotes object; we create a Zoho custom Quotes module or map to the Zoho Quotes extension available in higher tiers. Quote header fields (quote number, status, total amount, expiration date) map to the custom module. Line items (S_QUOTE_ITEM) migrate as Quote Line Items with product reference, quantity, unit price, and discount. The Quote-to-Opportunity linkage is preserved as a lookup field in the custom module.

Siebel Orders (S_ORDER with S_ORDER_ITEM) represent the quote-to-cash handoff. Zoho CRM does not include a native Orders module; we create a custom Orders module mirroring the S_ORDER schema. Order header fields (order number, status, order date, total) migrate with the Account and Opportunity lookups resolved. S_ORDER_ITEM records migrate as Order Line Items with product, quantity, and pricing. If the customer uses Zoho Books, we create a Zoho Books Sales Order via API after CRM migration as a separate integration step.

Siebel Service Requests (S_SRV_REQ) map to Zoho CRM Cases or, if the customer uses Zoho Desk, to Zoho Desk Tickets. SR status, priority, category, assigned Position/Employee, and description fields map to their Zoho equivalents. Case-related Activities (S_EVT_ACT with type Task or Call) migrate as Zoho Activities linked to the parent Case. Escalation and custom escalation fields on S_SRV_REQ migrate as Zoho Case custom fields.

Siebel Activities of type Call, Email, Meeting, and generic Task (S_EVT_ACT) map to Zoho CRM Activities linked to the parent Contact or Account record. We preserve activity type, date, owner, duration, subject, and description. For email activities, we migrate the body as an Activity note. Activity timestamps are preserved in Zoho's Activity Date fields. The Siebel Activity owner (S_EVT_ACT.EMPLOYEE_ID) resolves to a Zoho User by email lookup.

Siebel Literature records (S_LIT) store document metadata including name, type, and file path reference to the Siebel File System. We extract the S_LIT metadata, then separately package the referenced files from the Siebel File System and deliver them alongside the database export. Zoho CRM's Documents module is the destination for literature files. The S_LIT URL path becomes a Zoho Document record with the binary file attached. Literature does not migrate automatically via API—file system extraction is a separate manual step coordinated with the customer's Siebel administrator.

Siebel Financial Assets (S_ASSET) map to a Zoho CRM custom Assets module. Asset Name, Serial Number, Status, Installed Product, and the parent Account lookup migrate directly. S_ASSET.PAR_BU_ID resolves to the Zoho Account. If the customer licenses Zoho Inventory, we alternatively map Assets to Zoho Inventory items with the asset flag set, depending on the operational use case.

Siebel custom extension tables built atop the S_ extension pattern (tables with TYPE='EXTENSION') are migrated on a per-table basis. We export the extension table data, map its foreign keys (PAR_PARTY_ID to S_PARTY, PAR_BU_ID to Account) to Zoho lookups, and create a Zoho custom module for each extension table. Field types are mapped: VARCHAR to Single Line, TEXT to Multi-line, NUMBER to Numeric, DATETIME to Date/Time. Siebel Tools SRF compilation requirements are noted as a post-import dependency if the customer continues running Siebel in parallel.

Siebel Positions (S_POSTN) represent organizational job roles and control record visibility. We extract Position records and parent-child hierarchy as structural data and map them to Zoho CRM Roles and Profiles. User-to-Position assignment (S_USER_POSTN) requires the customer's Zoho admin to manually map Siebel Positions to Zoho Users after migration, as the two systems' security models differ structurally.