Migrate from Oracle EBS CRM to Freshsales

Discovery and database connection

We connect directly to the Oracle database with read-only credentials scoped to the CRM-relevant schemas (ARHZTA for Accounts, HR or AR for Contacts, CZ for Opportunities). We run discovery queries to enumerate the target tables, row counts per object, and identify the correct schema variant for Activities and Opportunities. We extract the FND_USER and FND_RESPONSIBILITY tables to get an accurate CRM user count and responsibility matrix. We capture territory definitions from AS_TERRITORIES and inventory every active Oracle Workflow in WF_ tables. Discovery typically takes five to ten business days and produces a written migration scope, record counts per object, and a custom object schema map.

Freshsales environment provisioning

We configure the Freshsales CRM modules and custom fields to receive the EBS CRM data. We map EBS column names to Freshsales field types (Oracle VARCHAR2 to Freshsales text, Oracle DATE to Freshsales date, Oracle NUMBER to Freshsales number or currency). We configure Freshsales deal pipelines to match the EBS opportunity stages and probability percentages. We provision Freshsales users mapped from the EBS FND_USER-to-responsibility matrix. This phase runs three to five business days and is executed in parallel with data extraction so the destination tenant is ready before any data loads.

Test migration and sandbox validation

We run a full migration into the customer's Freshsales sandbox environment before touching production data. We export CRM data from Oracle, transform it through the field mapping, and load it via the Freshsales CRM API. We validate record counts for each object and spot-check twenty to thirty records field-by-field against the Oracle source. Any mapping corrections are captured and applied before the production migration begins. The customer reviews and approves the sandbox migration results before we schedule the production cutover window.

Owner reconciliation and user provisioning

We extract the FND_USER and FND_RESPONSIBILITY tables from Oracle EBS during discovery to identify every CRM user and their responsibility assignments. We match FND_USER email addresses to Freshsales user accounts and resolve the Owner-to-User mapping. Any EBS user without a matching Freshsales account is held in a reconciliation queue; the customer's admin provisions missing users before production migration begins. This step must complete before record import because OwnerId is a required reference on most standard objects.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (no parent dependencies), Contacts with account_id resolved, Leads and Deals split by opportunity status, Tasks, Events, and Notes, then custom objects last. Each phase emits a row-count reconciliation report before the next begins. We use the Freshsales CRM API with rate-limit handling and exponential backoff to manage API throughput constraints. We flag any records that fail import (due to missing required fields or lookup resolution failures) to a retry queue for resolution before final sign-off.

Cutover, delta sync, and automation rebuild handoff

We freeze Oracle EBS CRM writes during cutover, run a final delta migration of any records created or modified during the migration window, and then enable Freshsales as the system of record. We deliver the Oracle Workflow and Territory inventory report to the customer's admin team with rebuild recommendations for Freshsales Automations and Territory settings. We provide a one-week hypercare window to resolve any data reconciliation issues raised by the customer's team. Oracle Workflow rebuilds in Freshsales Automations are outside the standard migration scope and are handled as a separate engagement or internal admin task.

Post-migration validation

We run post-migration validation against the production Freshsales tenant, comparing record counts for every object against the Oracle source totals and flagging any discrepancies above a 1% threshold. We spot-check representative records across all migrated object types for field-level accuracy and validate that parent-to-child lookups (Contact to Company, Deal to Contact) resolve correctly. We deliver a final migration report with record counts, import errors and resolutions, and a list of any remaining data quality flags that the customer should address in Freshsales.