SAP Business One and Mailchimp integration

What moves between them

The main flow is from SAP Business One into Mailchimp. SAP Business One BusinessPartners map to Mailchimp List Members, synced on a poll schedule tied to your SAP update cadence. SAP Business One Invoices map to Mailchimp E-commerce Orders so order history, amounts, and payment status flow into Mailchimp's e-commerce tracking; this allows revenue attribution and cohort analysis in Mailchimp campaigns. Contact details (email, phone, address) and customer attributes from SAP Business One are upserted to Mailchimp lists so your marketing audience always reflects your actual customer base.

How ml-connector handles it

ml-connector maintains a session token to SAP Business One and reuses it across calls to avoid the 5-second cold-start penalty of a new login. It polls the SAP Business One OData endpoint with an UpdateDate filter to fetch only changed records since the last run, then upserts those BusinessPartners and Invoices into Mailchimp. Invoices become E-commerce Orders in Mailchimp, mapped by a unique SAP invoice number or customer-defined key. Contact fields from SAP Business One (name, email, phone, address, custom dimensions like ProfitCenter) are mapped to Mailchimp List Member fields, and if Mailchimp does not have a direct field, the value is stored in a merge field or a custom dimension. Because SAP Business One session tokens expire after 30 minutes of inactivity, ml-connector refreshes the session on a schedule even if no records have changed, ensuring the next poll does not hit the -5002 timeout error. Mailchimp does not verify webhook signatures on the Marketing API, so ml-connector uses HTTPS and a secret URL path as additional safeguards. If SAP Business One is on a self-signed TLS certificate (common for on-premise), that certificate is stored encrypted and presented on each request. E-mail address is the primary match key for List Members; if a SAP Business One customer email changes, ml-connector upserts the member record so Mailchimp has the current email and the old engagement history is preserved under the new address.

A real-world example

A mid-market B2B services company runs SAP Business One on-premise to manage customers, invoices, and payments. They use Mailchimp to build email campaigns targeting high-value segments and track engagement. Before the integration, the marketing team manually exported customer lists from SAP Business One and imported them into Mailchimp each month, then later looked up order history one-by-one to see which customers had received invoices. With SAP Business One and Mailchimp connected, the customer list updates automatically every night, pulling in new customers and recent invoice data, so every campaign sent to Mailchimp already has transaction history attached. The team can now segment by purchase history and frequency without manual export.

What you can do

• •Sync SAP Business One BusinessPartners to Mailchimp List Members, keeping contact records, emails, phone numbers, and customer attributes current in your marketing audience.
• •Map SAP Business One Invoices to Mailchimp E-commerce Orders so order history and amounts flow into Mailchimp's e-commerce tracking and revenue attribution.
• •Maintain SAP Business One session tokens and refresh them on schedule to avoid timeout errors that halt polling.
• •Handle self-signed TLS certificates on on-premise SAP Business One instances and present them on each OData request.
• •Poll SAP Business One on a schedule with UpdateDate filters so only changed records are fetched, reducing load and keeping Mailchimp audience in sync with your ERP.

Questions

Which direction does data move between SAP Business One and Mailchimp?

The main flow is from SAP Business One into Mailchimp. Customer records (BusinessPartners) sync to Mailchimp List Members, and invoices map to e-commerce orders so order history is available in Mailchimp for segmentation and engagement tracking. Mailchimp is a marketing platform with no general ledger or purchasing capability, so financial data does not flow back to SAP Business One.

How does ml-connector handle SAP Business One's on-premise architecture and session token expiry?

SAP Business One runs on-premise or partner-hosted with a customer-specific Service Layer URL that the customer provides. ml-connector reuses the session token returned by /Login across multiple requests to avoid the 5-second cold-start penalty, and it refreshes the session on schedule even if no records have changed, so the 30-minute inactivity timeout does not interrupt polling. If the session expires, ml-connector logs the -5002 timeout error and re-authenticates on the next scheduled run.

What happens to customer records if their email address changes in SAP Business One?

ml-connector upserts the member record to Mailchimp using email as the primary match key, so if a customer email changes in SAP Business One, the updated record goes to Mailchimp under the new address. Mailchimp preserves the engagement history (opens, clicks, campaign sends) under the new email, so the customer's marketing journey stays intact even if their contact details change.