SAP ECC and Mailchimp integration

What moves between them

Customer master records from SAP ECC flow into Mailchimp as list members, with contact details, company, industry, and custom fields mapping the ERP attributes you choose. Vendor contacts can sync into separate lists for internal communication or procurement workflows. The flow is unidirectional, from SAP ECC into Mailchimp, because Mailchimp has no GL accounts, purchase orders, or financial transactions that map back to the ERP. On-premises agent constraints mean ml-connector polls SAP Gateway OData on a schedule you define, typically daily or weekly, and queues the changes for Mailchimp API calls.

How ml-connector handles it

ml-connector runs an on-premises agent on your network that initiates HTTP calls to SAP Gateway OData endpoints, authenticated with the SAP username and password you supply. For each customer or vendor record read from SAP ECC, ml-connector maps relevant fields (name, email, phone, city, country, industry classification, credit limit, payment terms) into a Mailchimp list member object. Before each Mailchimp API call, ml-connector obtains a fresh bearer token using your API key, maps the SAP ECC company code and customer type into Mailchimp list name or segment criteria, and posts the contact to the target list. Because Mailchimp has no GL accounts or supply chain entities, only contact attributes are synced; SAP ECC purchase orders, invoices, and GL postings stay in the ERP. If a Mailchimp API call fails with a 429 (rate limit), ml-connector backs off and retries. The on-premises agent must have outbound HTTPS access to Mailchimp and SAP Gateway, and your SAP Basis team must activate the OData service via TCODE SICF.

A real-world example

A B2B wholesale distributor runs SAP ECC for inventory, procurement, and billing across three regions, and uses Mailchimp for customer newsletters and seasonal promotions. Finance and sales each maintain a different spreadsheet of active customers and contacts. Before the integration, the marketing team imported customer lists manually every month, creating duplicates and missing new accounts opened in SAP ECC. With SAP ECC and Mailchimp connected, each new customer or customer contact change created in SAP ECC automatically flows into Mailchimp within hours. Marketing can now segment campaigns by customer type, credit limit, or last purchase date pulled directly from the ERP, and the monthly import step is eliminated.

What you can do

• •Sync customer master records from SAP ECC into Mailchimp lists, including company name, email, phone, city, country, and industry classification.
• •Sync vendor contacts into separate Mailchimp lists for procurement and supplier relationship teams.
• •Map SAP ECC credit limits, payment terms, and account status into Mailchimp contact custom fields so campaigns can be segmented by financial criteria.
• •Poll SAP Gateway OData on a schedule you control, with the on-premises agent handling RFC authentication and network access.
• •Handle HTTP Basic Auth refreshes, Mailchimp bearer token management, API retries on rate limits, and a complete audit trail on every contact sync.

Questions

How does the integration work with SAP ECC being on-premises?

ml-connector includes an on-premises agent that you run on your network with outbound HTTPS access. The agent initiates calls to SAP Gateway OData endpoints using HTTP Basic Auth with your SAP username and password. SAP ECC does not accept inbound calls from the cloud, so the agent must originate all reads. Your SAP Basis team activates the OData service via TCODE SICF, and ml-connector polls the endpoints on a schedule.

Which SAP ECC data flows into Mailchimp, and in which direction?

Customer and vendor master records flow from SAP ECC into Mailchimp lists. Contact details (name, email, phone, address) and custom attributes (credit limit, payment terms, industry) are mapped into Mailchimp contact fields. The flow is unidirectional because Mailchimp is an email marketing platform without GL accounts, invoices, or purchase orders that would map back to the ERP. Mailchimp webhooks for subscribe, unsubscribe, and bounces are not currently synced back into SAP ECC.

What happens if a customer record exists in both SAP ECC and Mailchimp?

ml-connector matches SAP ECC customer numbers to Mailchimp email addresses and uses the SAP ECC record as the source of truth. If a contact email changes in SAP ECC, the Mailchimp record is updated. If the same email exists in multiple SAP ECC customer records, ml-connector processes each separately, so your team should ensure email uniqueness in the ERP. Duplicate detection is based on the SAP customer number, not email.