Migrate from Oracle CRM On Demand to Nutshell

Discovery and scoping

We audit the Oracle CRM On Demand tenant across objects in use (standard and custom), custom field definitions, pipeline stage values, active user count, and activity volume. We identify the Oracle edition tier (Standard CRM On Demand or Enterprise Lead Referral) and any role-level export restrictions that could limit field access. We also confirm which Nutshell plan is active (Starter, Pro, or Enterprise) since custom field limits and automation features vary by tier. The discovery output is a written migration scope with record counts per object and a list of any Oracle API access gaps to resolve before extraction begins.

Schema design and mapping document

We design the destination schema in Nutshell. This includes provisioning custom fields on Company, Person, and Deal objects to receive Oracle custom field data, configuring pipeline stages that map from Oracle Opportunity stages, and setting up any custom fields required for lead-scoring or classification data. We document the full object-level and field-level mapping in a written mapping deliverable that the customer reviews and approves before extraction begins. Oracle Custom Objects are reverse-engineered during this phase and mapped to Nutshell custom fields on the appropriate parent object.

Data extraction with API rate-limit pacing

We extract Oracle data in queue-friendly batches that honor the 30-req/min limit. We run exports under an administrator account with the 'List - Export all Fields' privilege to ensure complete record extraction, and we document any fields hidden by role-level restrictions. List export files are downloaded immediately upon job completion and stored in our migration workspace before the 168-hour expiry. For large record sets, we use Oracle's bulk export jobs to minimize API round-trips. All data is staged in a structured format before transformation begins.

Data staging, transformation, and validation

We stage Oracle extract files and apply transformations: Oracle Account-to-Nutshell Company mapping, Oracle Contact-to-Nutshell Person mapping with Account link resolution, Oracle Opportunity-to-Nutshell Deal mapping with pipeline stage normalization, and Oracle Activity-to-Nutshell Activity mapping with parent record resolution. We run duplicate detection on email addresses for Person records and flag potential duplicates for the customer's review. Oracle attachment URLs are resolved and file content is staged for import.

Production import and reconciliation

We run the production import into Nutshell in dependency order: Companies first (to satisfy lookup references), then People (with Account link resolved), then Deals (with Person and Company links resolved), then Activities last. Each phase emits a row-count reconciliation report before the next phase begins. We validate that Oracle OwnerId references resolve to Nutshell User IDs via the user mapping table and flag any unresolved owners for the customer's admin to provision before import resumes.

Cutover, validation, and handoff

We freeze Oracle writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the object and field mapping document, the Workflow and Automation inventory (with trigger and condition notes for each Oracle rule requiring rebuild), and the reconciled record counts per object. We do not rebuild Oracle Workflow Rules or automations in Nutshell; that work is a separate engagement or an internal admin task. We provide a one-week hypercare window for reconciliation issues raised during the first week of Nutshell use.