Migrate from Oracle EBS CRM to HighLevel

Oracle EBS CRM Accounts (stored in ARHZTARZ base tables and exposed through the APPS schema) map to GoHighLevel as both a Contact record and a Company record. We use the customer name as the Contact name, the primary address as the Contact address fields, and create a separate Company record for cross-contact association. If the EBS Account has multiple contacts (AR_CONTACT_RELS or PER_CONTACTS), each contact becomes a separate GoHighLevel Contact linked to the same Company. Multi-org EBS structures are mapped to GoHighLevel Locations if the customer uses GoHighLevel's multi-location feature.

Oracle EBS CRM Contacts sourced from the HR schema (PER_ALL_ASSIGNMENTS_F for employees) or the AR base schema for external parties map directly to GoHighLevel Contact. We preserve the full name, email address, phone numbers, job title, and relationship to the Account. If the contact has a duplicate in GoHighLevel by email match, we update rather than create. The mapping resolves the parent Account lookup before insert to maintain referential integrity.

Oracle EBS CRM Opportunities are stored in the CZ (Collaborative Selling) schema or the deprecated ASF schema depending on the CRM module version deployed. We identify the correct schema at discovery time, extract stage, amount, probability, close date, and owner, and map these to GoHighLevel Opportunity. EBS opportunity currency codes map to GoHighLevel's single-currency model — multi-currency EBS Opportunities require a currency conversion step at migration time. We configure GoHighLevel pipeline stages to match the EBS stage names before migration so that deal history reflects the original pipeline.

Activities and tasks in EBS CRM live across multiple schemas depending on which CRM module is installed — the deprecated Teleservice tables or the modern Interaction Center tables. We identify the source schema at discovery, extract the activity type, subject, description, due date, and owner reference, and map these to GoHighLevel Task records. The task owner resolves by email match against the GoHighLevel User table. Activity timestamps are preserved as the task creation date.

Notes 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 blobs with timestamps and owner references, then map them to GoHighLevel Contact Notes or Opportunity Notes depending on the parent object stored in the EBS note record. Large text blobs are truncated at GoHighLevel's note field limits.

Oracle EBS CRM Territory definitions (stored in AS_TERRITORIES base tables with hierarchical org structures) have no direct GoHighLevel equivalent. We extract the territory hierarchy and assignment rules and document them as a GoHighLevel Location and pipeline assignment plan. Multi-territory organizations use GoHighLevel Locations to segregate data by team or branch, with pipeline stage assignments scoped per Location.

Oracle EBS CRM custom objects are stored in user-defined tables within the base product schemas, often with FK columns pointing to RA_CUSTOMERS or OE_HEADERS. We extract the DDL for each custom table during discovery, create equivalent Custom Objects in GoHighLevel via Object Settings, define typed fields matching the source column types, and configure associations to standard objects (Contact, Opportunity, Company). Required fields in GoHighLevel Custom Objects are validated before import — any missing required field values from the source are flagged for customer decision (null-insert or exclude). GoHighLevel Custom Objects support CSV import via the bulk import UI with field mapping.

Oracle EBS CRM users are sourced from the HR schema (PER_ALL_ASSIGNMENTS_F) with CRM-specific responsibilities assigned via FND_RESPONSIBILITIES. We extract the FND_USER table and FND_RESPONSIBILITY mappings during discovery to get an accurate user count and responsibility matrix. Users map to GoHighLevel Users by email match. Any EBS user without a matching GoHighLevel user is held in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references on Opportunities and Tasks require a valid GoHighLevel User.