Migrate from Oracle EBS CRM to monday CRM

Oracle EBS CRM Accounts (stored in ARHZTARZ base tables and exposed through the APPS schema) map to a Monday.com CRM Board where each Account becomes an Item inside a dedicated Group named after the Account. Account name maps to the Item name, and key fields (industry, address, revenue tier) map to custom columns on the Item. We extract the HZ_PARTIES and HZ_ACCOUNTS tables during discovery and create a Group-per-Account board structure that allows the sales team to view all account-level data at a glance. If the customer maintains multiple Account types (prospects, customers, partners), we create separate Groups within the same Board rather than separate Boards to preserve reporting continuity.

EBS CRM Contacts (sourced from the base HR or AR schemas depending on employee vs. external-party classification) map to Monday.com Items within the corresponding Account Group, or as Subitems attached to the Account Item if the customer prefers the parent-child structure. Email address, phone, role, and relationship to Account transfer to custom columns. We resolve the Contact-to-Account relationship by querying the HZ_RELATIONSHIPS table and creating the Subitem or linked Item attachment during migration. Contact ownership from FND_RESPONSIBILITY maps to a People column on the Item.

EBS CRM Opportunities (stored in the CZ Collaborative Selling schema or the deprecated ASF tables depending on CRM module version) map to Monday.com Items inside the relevant Account Group, with the EBS deal stage mapped to a Status column that replaces the CRM pipeline stage concept. Amount, close date, probability, and owner transfer to custom columns. EBS Opportunity probability (stored as a numeric value) migrates as a Number column — Monday.com has no native probability field, so the customer reviews and adjusts probability settings in a custom Formula or Percentage column post-migration. The CZ schema version is identified during discovery before extraction begins.

EBS CRM custom objects stored in user-defined tables within base product schemas (often with FK columns pointing to RA_CUSTOMERS or OE_HEADERS) have no direct Monday.com equivalent because Monday.com does not support true independent custom objects with their own schema. We map custom object fields to Monday.com custom columns on the relevant Board — typically the CRM Board for business-object custom records. For complex custom objects with multi-record cardinality, we recommend a separate Board with Items representing each custom record and a Link column back to the parent Account or Contact. We extract DDL and sample data during discovery to determine the appropriate mapping strategy per custom object.

EBS CRM Territory definitions (stored in AS_TERRITORIES base tables with hierarchical org structure) have no native Monday.com equivalent. Monday.com has no Territory management module. We extract the full territory hierarchy during discovery and document it as a structured report: territory name, parent-territory relationship, assignment rules, and assigned user list. During migration, we create a Monday.com Board called 'Territory Map' with Groups representing each Territory — the Group description carries the assignment rule logic. The customer reviews and assigns the appropriate sales rep to each Group post-migration. This is a best-effort representation; territory-based routing requires rebuilding in Monday.com's automation rules or using the territory report as a reference for manual assignment.

EBS CRM activities and tasks (stored across deprecated Teleservice tables or modern Interaction Center tables depending on installed CRM module) migrate to Monday.com as Subitems on the relevant Account or Contact Item, with the Subitem name carrying the activity type and the Subitem status set to 'Complete' or 'Pending'. Call dispositions, durations, and notes transfer as custom Subitem columns. Activity timestamps are preserved by setting the Subitem's Due Date to the original EBS activity date. We identify the correct source schema during discovery because EBS CRM activity storage varies significantly by module version.

EBS CRM notes and audit history (stored in FZ_NOTES or equivalent application-level audit tables) migrate as text entries in a Long Text column on the corresponding Account, Contact, or Opportunity Item in Monday.com. Each note is timestamped and attributed to the original EBS owner via a text column. Long-form notes exceeding Monday.com's column character limits are attached as linked Documents (via URL column) pointing to a exported file location rather than inlined. We extract the note content, create date, and owner during migration.

EBS CRM attachments stored as LOB data (BFILE or CLOB columns) or on the file system are extracted as binary or BASE64-encoded blobs during migration. For Monday.com, we map file attachments to a File Column on the relevant Item, preserving the original filename and extension. Attachments exceeding Monday.com's file size limits are exported to a customer-provided file storage location and referenced via a URL column on the Item. We flag any attachment above 500MB for customer review before migration.

EBS CRM users (employees sourced from PER_ALL_ASSIGNMENTS_F with CRM-specific responsibilities via FND_RESPONSIBILITIES) are extracted from FND_USER and FND_RESPONSIBILITY tables during discovery. We match EBS users to Monday.com workspace members by email address during migration. Any EBS user without a matching Monday.com account is flagged in the reconciliation report for the customer's admin to provision before record import completes. The FND_RESPONSIBILITY matrix is preserved as a text export for the customer's admin to rebuild Monday.com Workspace roles and permissions post-migration.