Migrate from Oracle CRM On Demand to monday CRM

Oracle Accounts map to Monday.com's Company Entity within the People board. We extract AccountName, Location, Industry, AccountType, Owner, and custom fields during discovery, then map each to the equivalent Company Column in Monday.com. Address records (street, city, state, postal code, country) map to structured address Columns or a single long-text Address Column depending on the customer's chosen board layout. Owner assignment requires a User mapping table since Oracle user IDs and Monday.com member emails differ.

Oracle Contacts map to People Entities in Monday.com CRM. We preserve ContactName, EmailAddress, PhoneNumber, JobTitle, and all custom contact fields as Columns on the People Entity. Contact-to-Account linking in Oracle maps to the Company Column on the People Entity, creating the relationship in Monday.com's CRM data model. Duplicate detection uses EmailAddress as the primary dedupe key. Role-level field restrictions from Oracle are documented as part of the mapping deliverable since some Contact fields may be hidden from the export user role.

Oracle Leads map to People Entities in Monday.com CRM with Lead_Status preserved as a status Column value. If the customer is on the Enterprise Lead Referral tier (create-only), we flag this during discovery because historical Lead records beyond creation events may be inaccessible via API under that tier's restrictions. We migrate the full Lead record where accessible: LeadSource, LeadStatus, custom lead fields, and created/modified timestamps as date Columns. Oracle Lead conversion (creating an Account and Contact from a Lead) has no direct Monday.com equivalent; we preserve the conversion context in a text Column noting the original Lead record reference.

Oracle Opportunities map to Deal Items in Monday.com CRM. Each Opportunity becomes an Item in the Deals Board, with OpportunityName as the Item name, Amount as a number Column, CloseDate as a date Column, SalesStage as a status Column, and Probability as a number Column. The Oracle Opportunity-to-Account relationship maps to the Company Column on the Deal Item, and Opportunity-to-Contact relationships map to the People Column. We handle pipeline stage mapping by creating Monday.com status groups that correspond to Oracle's pipeline stage values.

Oracle's Opportunity pipeline stages map to Monday.com Status Column values on the Deals Board. Each Oracle pipeline becomes a distinct Status Column, or a single Status Column with all stage values if the customer uses one sales process. Stage probability percentages migrate as a separate number Column. If Oracle uses multiple pipelines, we create multiple Status Columns or separate Boards per pipeline, depending on the customer's reporting needs in Monday.com.

Oracle Tasks map to Update entries on the linked Account, Contact, or Opportunity Item in Monday.com. Task Subject becomes the Update title, Description maps to Update body text, Status maps to a status indicator in the Update, and DueDate maps to a date reference. We preserve the activity timestamp from Oracle's ActivityDate as a date Column or Update timestamp for audit ordering. Large activity histories (over 12-24 months) are prioritized for recent records with older records flagged for archival handling during scoping.

Oracle Call records map to Updates on the linked Item with Call-specific Columns: CallDuration maps to a number Column (seconds), CallDisposition maps to a text Column, and CallType (inbound/outbound) maps to a status Column. Call notes from Description migrate to the Update body. If the customer requires structured call logging, we configure a dedicated Calls Group or sub-Board within the account or opportunity Board with typed Columns for duration, outcome, and disposition.

Oracle Appointments (meetings) map to Updates on the linked Item with StartTime, EndTime, and Location preserved as date and text Columns. If Monday.com's Calendar integration is active, we document the appointment mapping so the customer's admin can connect Oracle calendar data post-migration. Meeting notes migrate as Update body text with the original Oracle timestamp preserved for activity ordering.

Oracle Custom Objects migrate to Monday.com Boards with Column types matched to Oracle field data types: text fields to text Columns, numbers to number Columns, dates to date Columns, picklists to status Columns, and lookups to People or Group Columns. We reverse-engineer the Oracle custom object definition during discovery (field names, types, required flags, lookup relationships) before creating the Monday.com Board schema. Custom Object relationships to standard Oracle objects (Account, Contact, Opportunity) map to People Columns or Group Columns in Monday.com. We do not migrate Custom Object hierarchies as separate Boards unless the customer specifically requests it during scoping.

Oracle record attachments migrate as file uploads attached to the corresponding Item in Monday.com. We handle both URL-based attachments (stored as a text Column with the original URL) and blob-stored attachments (downloaded and re-uploaded to Monday.com's file storage). Attachment file sizes and volumes are scoped separately from record migration because Monday.com has per-board storage limits. We flag any attachments exceeding Monday.com's file size limits during discovery for customer decision on handling.