Migrate from Oracle Siebel to Nutshell

Siebel Organizations extend S_PARTY as the root record with S_ORG_EXT as the extension table. We extract the S_PARTY row first (preserving PAR_ROW_ID as the dedupe anchor), then S_ORG_EXT fields. In Nutshell, Companies are created as the parent record before any Contact import so that the Company lookup is satisfied at import time. Industry-specific fields in S_ORG_EXT (financial services account types, telecom service tiers) that have no Nutshell equivalent are flagged in the migration report as candidates for Nutshell custom fields or Forms.

Siebel Contacts extend S_PARTY similarly to Organizations, with S_CONTACT holding the contact-specific fields. We resolve the S_CONTACT.S_PARTY_ID foreign key to the S_PARTY row to retrieve the contact's name, email, and phone, then attach S_CONTACT extension fields (title, department, primary organization link). The Nutshell Person is created with the parent Company resolved from S_CONTACT.PR_OU_ID to S_ORG_EXT. Any Siebel contact without a linked Organization is imported as a standalone Person with a flag in the migration report.

Siebel Opportunities track Deals through Pipeline Stages with revenue amounts and Opportunity-to-Account links. We map Opportunity records to Nutshell Leads, preserving the opportunity name, amount, close date, probability, and stage name. Siebel pipeline stage names migrate to Nutshell pipeline stages; if Nutshell's pipeline stage count is exceeded, we consolidate into the closest matching stage or document the overflow for the customer to resolve in Nutshell's pipeline editor post-migration.

Siebel Activities represent Engagements and Tasks linked to parent Contact or Account records. We map activity type, date, owner, duration, and description to Nutshell's activity model (calls as Call type, emails as Email type, meetings as Meeting type, general tasks as Task type). The Nutshell activity timeline renders against the resolved Person or Company record. Custom Activity extension fields in Siebel that have no Nutshell equivalent migrate as notes on the activity record.

Siebel Quotes map to S_DOC_QUOTE with line items in S_QUOTE_ITEM. Nutshell supports Quote objects on paid plans. We migrate Quote header fields (quote number, date, expiration, status) and line items with product, quantity, unit price, and discount. Quote-to-Order linkage from Siebel is preserved in a custom field for reference since Nutshell does not have a native Order-to-Quote workflow.

Siebel Orders use S_ORDER with Order Items in S_ORDER_ITEM and Order Documents in S_ORDER_DOC. Nutshell Orders capture header, line items, and status. We map Order number, date, status, and line items preserving product, quantity, price, and discount. Since Nutshell Orders are tied to the standard CRM workflow rather than Siebel's quote-to-cash engine, complex pricing matrices and billing rules are documented separately for the customer to configure in Nutshell post-migration.

Siebel Service Cases map to Case/Service Request tables with status, assigned Position/Employee, and Activity logs. Nutshell does not have a native Case management object. We migrate Case records as Nutshell Leads tagged with a 'Migrated Case' label and a custom field case_origin_id__c holding the original Siebel SR number, so the customer can reference historical cases in search. If Nutshell's paid plan with custom fields is used, the case status maps to a picklist field.

Siebel Literature records (S_LIT) store metadata and a path reference to the actual document file in the Siebel File System. The database export does not include binary files. We extract the file path list from S_LIT, package the corresponding files from the Siebel File System, and deliver them as a zip archive alongside the migration data. The customer uploads the documents to Nutshell's attachments or links them to the relevant Person or Company record. No Literature metadata migrates directly into Nutshell objects.

Siebel Positions represent organizational job roles and control record visibility through Position-based access control. Nutshell uses Team-based sharing with admin, manager, and member roles. We extract Position records and parent-child hierarchy as structural data in the migration report. The customer maps Siebel Positions to Nutshell Teams and User roles during scoping. Position-based territory restrictions do not have a direct Nutshell equivalent and are documented for the customer's admin to implement through Nutshell's sharing rules post-migration.

Custom data built atop Siebel's extension table pattern (tables with TYPE like 'EXTENSION') are migrated on a per-table basis. We export each extension table, map its foreign keys to the parent S_PARTY or S_CONTACT row, and create corresponding Nutshell custom fields on the Person or Company object. Field type conversion is applied: Siebel DTYPE_* types map to Nutshell field types (DTYPE_NUMBER to Number, DTYPE_DATE to Date, DTYPE_EVTCLOCK to DateTime). Custom extension tables with no parent S_PARTY relationship are documented separately for the customer to design as Nutshell Forms or custom integrations.