Migrate from Oracle EBS CRM to Mailchimp

Oracle EBS CRM Accounts stored in ARHZTARZ base tables map to Mailchimp Companies (a Commerce object). We extract Account Name, Site, Address fields, Phone, Website, and the Organization_ID from the ARHZTARZ table and write them as Company records via the Mailchimp Commerce API. Multi-org EBS Accounts may reference the same business entity across multiple Operating Units; we deduplicate by Account Name and Address hash during extraction and create a single Company in Mailchimp. The FND_ORGANIZATION_UNITS table provides the org context for each Account.

Oracle EBS CRM Contacts sourced from HR (PER_ALL_ASSIGNMENTS_F for employees) or AR schemas (RA_CONTACTS for external parties) map to Mailchimp Members. We extract email address, first name, last name, phone, title, and the FK reference to the parent Account. Contacts are imported into a Mailchimp Audience (list) with the email address as the subscriber key. Address data and custom fields migrate as Mailchimp merge fields. Contacts without a valid email address are excluded and reported separately.

Oracle EBS CRM Opportunities in the CZ Collaborative Selling schema map to Mailchimp Deals (available on Standard and Premium tiers). We extract Opportunity Name, Amount, Stage, Close Date, and Owner, and write them as Mailchimp Deals linked to the corresponding Member or Company. Mailchimp Deals have no probability, forecast, or product-line rollup; these attributes are stored in a custom Deal custom field mapped from EBS StageName. Opportunity data that exceeds Mailchimp's Deal data model (such as multi-product line Items or territory-based forecasting) is documented as a reporting gap in the handoff report.

Oracle EBS CRM Territory definitions in AS_TERRITORIES base tables map to Mailchimp Tags. We extract the territory hierarchy and the Contact-to-Territory assignment rules during discovery, then apply each relevant Tag to the corresponding Member records in Mailchimp. For example, a Contact assigned to the 'Northeast Enterprise' territory receives the 'Northeast-Enterprise' tag. Tags are created as part of the Audience setup before Contact import. Territory rollup reporting that relied on EBS hierarchical territory structures does not replicate in Mailchimp and is documented for the customer's reporting team.

Oracle EBS CRM Activities and Tasks stored in the Interaction Center or deprecated Teleservice tables map to Mailchimp Member Activity events. We extract call logs, meeting records, and task completions with timestamps and owners, then write them as a custom text field on the Member (or as a Mailchimp Note with an activity prefix). Activity owners are resolved via the Owner-to-User merge field mapping. High-volume activity histories (over 50,000 records) are chunked and written with a delay to respect Mailchimp's batch API limits.

Oracle EBS CRM Notes stored in FZ_NOTES or application audit trail tables map to Mailchimp Notes attached to the corresponding Member. We extract Note body text, creation timestamp, and owner reference. Notes migrate as plain text (rich text formatting is flattened) with the original EBS timestamp preserved. If the Note references an attached file stored as a BFILE or CLOB in the EBS database, we write the file path and name to the Note body as a reference rather than embedding the binary content, and we document the file retrieval path separately.

Oracle EBS CRM Users sourced from FND_USER and FND_RESPONSIBILITY tables are mapped to a custom merge field on Mailchimp Members. We extract the EBS username and email of the CRM user responsible for each Account, Contact, and Opportunity and write it as a text merge field (e.g., EBS_Owner_Email). Mailchimp does not have a native user-assignment model for Members; the merge field preserves ownership traceability for reporting and routing purposes. The customer configures Mailchimp's Customer Journey conditions using this field if owner-based routing is required.

Oracle EBS CRM Attachments stored as BFILE, CLOB, or file-system LOBs have no migration path to Mailchimp's contact-centric data model. Mailchimp Members do not support file attachments. We extract attachment file names, paths, and reference URLs from the EBS attachment tables (FND_ATTACHED_DOCUMENTS, FND_LOBS) and include them in a structured document reference file delivered alongside the migration. The customer's team retrieves original files from the EBS document repository separately.