Migrate from Oracle CRM On Demand to Salesforce Sales Cloud

Oracle CRM On Demand Accounts map directly to Salesforce Account. Oracle's Account Name, Site, Industry, Revenue, and Employee Count fields map to equivalent Salesforce Account fields. Oracle's multi-address model (billing vs shipping) maps to Account.BillingAddress and Account.ShippingAddress. Oracle Account Type (Customer, Prospect, Competitor, Partner) maps to a custom Account.Type__c picklist since Salesforce's native Type field uses a different value set. We run a dedupe check on Account Name before insert to avoid duplicate accounts from Oracle's potentially denormalized data.

Oracle Contacts map to Salesforce Contact with a parent AccountId lookup resolved at migration time. We use the Contact's primary Account linkage from Oracle to establish AccountId on the Salesforce Contact. Email serves as the dedupe key; we apply Salesforce's duplicate rule handling (Matching Rules configured for Email) before insert. Oracle's custom Contact fields map to custom Contact fields in Salesforce created during schema deployment.

Oracle Leads map to Salesforce Lead with Oracle's Lead_Status and Lead_Source fields mapped to Salesforce Lead Status and LeadSource. For customers on the Enterprise Lead Referral tier, we flag during discovery that the API may only expose creation events; lead history beyond creation may be inaccessible. We preserve any Oracle lead score or rating fields as custom Lead fields. Leads without an email address are flagged in the reconciliation report since Salesforce requires an email pattern for standard Lead validation rules.

Oracle Opportunities map to Salesforce Opportunity with stage, probability, close date, and amount preserved. Oracle's Opportunity-to-Account linkage resolves to the AccountId on the migrated Opportunity. Oracle's Opportunity Revenue (Amount) and Quantity fields map to Opportunity.Amount and a custom Quantity field. Stage probability percentages from Oracle map to Salesforce StageProbability. We configure Salesforce Opportunity Sales Processes before migration so that the stage value set matches Oracle's pipeline.

Oracle's deal pipeline stages map to a Salesforce Sales Process with StageName values and probabilities. Each Oracle pipeline becomes a Salesforce Record Type on Opportunity. We extract the full stage set from Oracle's API before migration, configure the Salesforce Sales Process to match, and validate that stage values align during sandbox testing. Probability percentages round to the nearest integer that Salesforce allows per stage.

Oracle custom objects are fully accessible via the REST API but the schema varies per tenant. We reverse-engineer the custom object definition (field names, data types, required flags, lookup relationships) from Oracle during discovery before designing the destination Salesforce custom object. The destination schema is deployed via the Salesforce API into a Sandbox first, validated, then deployed to production. Custom object relationships (Oracle custom-object-to-custom-object lookups) map to Salesforce lookup fields on the destination custom object.

Oracle Tasks map to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Oracle task assignment maps to Salesforce OwnerId via the User mapping. Tasks without a parent Contact or Opportunity are imported as standalone Tasks and flagged in the reconciliation report for the customer to review.

Oracle Call records map to Salesforce Task with TaskSubtype = Call. Oracle's Call disposition, duration, and outcome fields map to custom Task fields in Salesforce. ActivityDate preserves the original timestamp for timeline ordering.

Oracle Appointments map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Oracle appointment attendees map to EventRelation records pointing at the related Contacts, Leads, and Users. We resolve the WhoId (Contact or Lead) and WhatId (Opportunity or Account) at migration time.

Oracle attachments export as files (URL-based or blob-stored) associated with records. URL-based attachments migrate as ContentDocumentLink records pointing to an external URL stored in a custom field. Blob attachments migrate as ContentVersion records attached via ContentDocumentLink to the parent record (Account, Contact, Opportunity, or custom object). File sizes and attachment volumes are scoped separately because they affect migration workspace storage.

Oracle Hosted Named Users map to Salesforce User records by email match. We extract every distinct Owner referenced on Account, Contact, Opportunity, and Activity records during discovery and match by email against the destination Salesforce org's User table. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Oracle users map to inactive Salesforce Users to preserve historical ownership.

Oracle Workflow Rules are not migratable via API in most release combinations. We do not migrate them as code. Instead, we extract each Oracle Workflow Rule's trigger object, conditions, field updates, and assignment actions via the Oracle API and document them in a written inventory with a recommended Salesforce Flow equivalent (record-triggered Flow, scheduled Flow, or Screen Flow). The customer's Salesforce admin rebuilds them post-migration or engages a Salesforce partner.

Oracle CRM On Demand does not have a native tagging equivalent. Oracle static lists and segmented audiences do not migrate directly. We extract the list definitions from Oracle and deliver a mapping document recommending whether each Oracle list should become a Salesforce Campaign (for campaign membership), a Salesforce List View (for administrative segmentation), or a custom multi-select picklist on the relevant object. The customer rebuilds audience lists in Salesforce during the post-migration admin phase.