Migrate from Oracle CRM On Demand to Freshsales

Oracle Accounts map directly to Freshsales Accounts with company name, address fields, phone, industry, and ownership preserved. We resolve the Oracle Account ownership (Assigned To field) against the Freshsales User mapping table during import. Oracle Account type (Customer, Prospect, Partner, Competitor) maps to Freshsales Account type with a custom field oracle_original_type__c preserving the source value for reporting continuity.

Oracle Contacts migrate to Freshsales Contacts with standard fields (name, email, phone, title, address) plus any mapped custom fields. We preserve the contact-to-account linking using Freshsales Account lookup. Email serves as the dedupe key; contacts sharing an email address across Oracle records merge to a single Freshsales contact with all associated opportunities and activities preserved.

Oracle Leads from the Standard CRM On Demand tier migrate to Freshsales Leads with Lead_Status, Lead_Source, and custom lead fields mapped. We preserve Oracle's lead rating and score fields in Freshsales custom fields. Lead conversion in Freshsales creates both a Contact and an Account; we run conversion post-import under the customer's conversion rules rather than pre-splitting during migration.

Oracle Enterprise Lead Referral restricts API access to create-only; edit, convert, and analytics are disabled. We flag this during discovery and scope only the creation-date lead records accessible via the API. Any lead history beyond creation events (status changes, conversion events, score updates) is unavailable under this tier's restrictions and we document it as a data gap in the migration deliverable. The customer's admin sets Freshsales lead conversion mapping manually post-import.

Oracle Opportunities map to Freshsales Deals. The Oracle opportunity stage (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) maps to Freshsales Deal stage values that we configure before import. Revenue amount, probability, close date, and opportunity type migrate directly. We preserve opportunity-to-account and opportunity-to-contact associations using the Freshsales Account and Contact lookups resolved at migration time.

Oracle Tasks migrate to Freshsales Tasks with Subject, Status, Priority, Due Date, and Description preserved. Owner assignment migrates by resolving Oracle Assigned To against the User mapping table. Tasks linked to specific Oracle records (Account, Contact, Opportunity) map to Freshsales Tasks with the corresponding lookup resolved.

Oracle Call activities migrate to Freshsales Call records with disposition, duration, and outcome preserved in custom fields. Call title and notes migrate to the Freshsales Call Subject and Description. We preserve the call-to-record linking (Account, Contact, or Deal) via Freshsales lookup resolution at migration time.

Oracle Appointments migrate to Freshsales Meetings with Title, Start Time, End Time, Location, and Description preserved. Attendee linking migrates as Contact or Account lookup relationships in Freshsales. We set the Activity Date to the original Oracle timestamp to preserve timeline ordering.

Oracle Custom Objects are reverse-engineered from the source API schema before migration. We pre-create equivalent Freshsales custom modules using the Module Builder (or API for programmatic provisioning), including all custom fields with type-mapped Freshsales field types (text, number, date, picklist, lookup). Custom object relationships to Accounts, Contacts, and Deals are rebuilt as Freshsales lookup fields on the custom module. Oracle Custom Object 01 through 05 each map to a separate Freshsales module, preserving the original numbering for audit continuity.

Oracle Named Users referenced on Account, Contact, Opportunity, and Activity records map to Freshsales Users by email address. We build a User mapping table during discovery that pairs Oracle user email with Freshsales User ID. Any Oracle user without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Oracle record attachments migrate to Freshsales Documents linked via the native attachment relationship to the corresponding Account, Contact, or Deal. File names, sizes, and MIME types are preserved. Large attachment sets (over 10,000 files) require separate scoping for download sequencing and Freshsales storage accounting.