Migrate from Oracle Siebel to Mailchimp

Each Siebel Contact is a row in S_CONTACT linked to an S_PARTY parent row. We extract both in a parent-first pass to avoid foreign-key violations, then merge the relevant fields into a single Mailchimp subscriber record. Email address maps to the subscriber email. First Name, Last Name, and Job Title map to FNAME, LNAME, and the JOBTITLE merge field (Essentials plan and above). The original S_PARTY ROW_ID is preserved in a custom mailchimp_siebel_party_id merge field for audit traceability.

Siebel Organizations (S_ORG_EXT) map to Mailchimp's Company metadata field on subscriber records, or to a pre-created Company record in Mailchimp if the Essentials plan with company management is used. The Account Name becomes the Company Name. For multi-level account hierarchies (parent Account, child Account), we store the hierarchy depth as a segment tag (e.g., Tier-1-Account, Tier-2-Account) rather than a native hierarchy because Mailchimp's company model is flat per subscriber.

Siebel's Organization Type field (e.g., Customer, Prospect, Partner) maps to Mailchimp Tags applied to each subscriber. We extract the unique Account Type values during scoping, create matching tags in Mailchimp, and apply them during the subscriber import so that segments can be rebuilt in Mailchimp based on Siebel's original account classification.

Siebel stores Contact addresses across S_CONTACT_BU (business address) and S_ADDR_PER (personal address). We select the primary business address, extract City, State/Province, Postal Code, and Country, and map these to Mailchimp's ADDRESS merge field structure (ADDR1, CITY, STATE, ZIP, COUNTRY) on the subscriber record. Address is available on all Mailchimp paid plans.

Siebel Contact's phone numbers (WORK_PHONE, HOME_PHONE, CELL_PHONE) are stored as separate S_CONTACT_BU rows. We extract the primary WORK_PHONE as the PHONE merge field in Mailchimp. Mobile and home phone values are appended to a custom mailchimp_alt_phones merge field as a pipe-separated string, or distributed across multiple single-line custom merge fields if the plan supports them.

Siebel custom fields added via Siebel Tools (stored in extension tables with TYPE='EXTENSION') require a pre-migration schema scan. We identify all S_EVT_ACT_X, S_CONTACT_X, S_ORG_EXT_X, and equivalent extension tables, extract their column definitions, and create matching custom merge fields in Mailchimp before import. Picklist-type extension fields in Siebel map to Mailchimp dropdown merge fields; text extensions map to text fields. Note: Siebel Tools SRF compilation is a Siebel-admin post-step outside our scope if the destination Siebel environment is still live during extraction.

Literature records in Siebel store document metadata (name, type, URL/path reference) in S_LIT, but the binary files live in the Siebel File System. Mailchimp has no document library equivalent for marketing collateral. We flag S_LIT metadata as a candidate for the customer's document management system or a shared drive, but do not migrate literature as a Mailchimp object. Binary file extraction from the Siebel File System is a separate file-system task outside data migration scope.

Siebel Opportunities represent pipeline and revenue data with no functional equivalent in Mailchimp. Opportunities, Pipeline Stages, Revenue amounts, and Opportunity-Account links do not map to any Mailchimp object. We deliver a written inventory of open and closed Opportunities (record count, stage distribution, account assignment) as a reference document for the customer's admin to use in Salesforce, HubSpot, or another CRM if Opportunity tracking is required post-migration.