Migrate from Oracle EBS CRM to Zoho CRM

Oracle EBS Accounts are stored in AR_CUSTOMERS and exposed through the APPS schema RA_CUSTOMERS_V view. We map the customer number, account name, primary site address, and status fields directly to Zoho CRM Account fields. Account is the parent record — we extract and insert Accounts first so that the Zoho Account ID is available as a lookup reference when Contacts and Opportunities are inserted.

Contacts reside in HZ_PARTIES (person type) and HZ_CONTACT_POINTS with employee contacts sourced from PER_ALL_ASSIGNMENTS_F. We map the party ID, name fields, email, phone, and the FK reference to the parent AR_CUSTOMER account. The relationship between Contact and Account is resolved by matching the EBS party_id to the Zoho Account lookup.

Opportunities in Oracle EBS are stored in the CZ (Collaborative Selling) schema or deprecated ASF schema depending on the CRM module version deployed. We identify the correct schema at discovery, extract stage, amount, probability, expected close date, and owner. Stage values map to Zoho Deal StageName, and the EBS owner email resolves to a Zoho User record via the FND_USER mapping.

Territory definitions in EBS CRM are stored in AS_TERRITORIES with hierarchical org structure references. There is no direct Zoho CRM Territory equivalent — territories do not migrate as code. We extract the full territory hierarchy, assignment rules, and salesrep-to-territory mappings in a structured report and hand it to the customer's Zoho admin to rebuild using Zoho's custom modules and assignment rules.

Activities and tasks are stored across multiple EBS CRM schemas — the deprecated Teleservice tables or the modern Interaction Center tables — depending on which CRM module is installed. We identify the active schema at discovery, extract task type, subject, status, due date, and owner, and insert them into Zoho Activities in dependency order after the parent Contact or Deal record exists in Zoho.

Notes and audit history in Oracle EBS CRM are stored in generic note tables (FZ_NOTES or equivalent) or in the application-level audit trail. We extract them as text with timestamps and owner reference and insert them into Zoho CRM Notes linked to the parent Account, Contact, or Deal record via ContentDocumentLink.

Custom objects in EBS CRM are stored in user-defined tables within base product schemas. They frequently reference FK columns pointing to core tables like RA_CUSTOMERS or OE_HEADERS. We extract the DDL for each custom table at discovery, pre-create matching custom modules in Zoho CRM (with fields typed to Zoho's supported types), then insert records in parent-resolved order so that lookups are satisfied at insert time. Zoho's 300-field and 5-lookup-field limits per module are validated against the custom table column count before migration begins.

Attachments in Oracle EBS CRM are stored as LOB data in the database (BFILE or CLOB columns) or on the file system depending on the attachment configuration. We extract binary attachments as BASE64-encoded blobs and insert them into Zoho CRM as file attachments linked to the parent record. Zoho's file size limit per attachment and total migration size cap of 25 GB are validated against the EBS attachment volume during scoping.

Users in EBS CRM are employees sourced from PER_ALL_ASSIGNMENTS_F with CRM-specific responsibilities assigned via FND_RESPONSIBILITIES. We extract FND_USER (username, email, start_date, end_date) and FND_RESPONSIBILITY (responsibility_name, application_id) to build a user matrix. The customer's Zoho admin provisions matching User accounts before production migration — we resolve by email match during record import.

Oracle Workflows stored in WF_ tables and implemented via PL/SQL packages encode routing, approval, and notification logic specific to EBS. These definitions cannot be exported as structured data and have no equivalent construct in Zoho CRM. We document every active Workflow at discovery — trigger event, routing conditions, approver assignments — in a structured report for the customer's admin to rebuild using Zoho Blueprint and workflow rules.