Connect · Data warehouse
Mailchimp to Databricks
Directory data as of October 23, 2026
8 of the 44 CDPs in the CdpHub directory list both a connector that reads from Mailchimp and one that sends data to Databricks, so they can sit between the two, and 13 go the other way, from Databricks to Mailchimp.
CDPs that can carry Mailchimp data into Databricks
8 CDPsEach of these CDPs lists a connector that reads from Mailchimp and one that sends data to Databricks. A route is a possible path, not a tested one: what travels depends on each connector, so check the documentation links.
Reads from Mailchimp
BlueConic ⇄ MailchimpImports Mailchimp audience members and mail activity into BlueConic and exports segment profiles to selected Mailchimp audiences in scheduled or manual batch runs.
Sends to Databricks
BlueConic ⇄ DatabricksImports and exports BlueConic profiles, groups and timeline events with a Databricks workspace through Delta Sharing up to six times a day, offered as a paid upgrade.
Reads from Mailchimp
Mailchimp → KlaviyoMigrates Mailchimp contacts to Klaviyo in a one-time sync, along with when each contact received, opened and clicked emails, so campaign metrics carry over.
Sends to Databricks
Klaviyo ⇄ DatabricksData warehouse import and export. Links Klaviyo and Databricks through a token for a Klaviyo-only account, importing profile and event data and exporting Klaviyo data back, with an Advanced KDP subscription.
Reads from Mailchimp
Lytics ⇄ MailchimpImports Mailchimp subscribers and campaign activity into Lytics every 12 hours and exports Lytics audiences to Mailchimp, with campaigns importable as Lytics Experiences.
Sends to Databricks
Lytics ⇄ DatabricksImports Databricks tables into Lytics, loads audiences, events, audience changes, system events and metrics into Delta tables, and can back Lytics Cloud Connect audiences.
Reads from Mailchimp
Mailchimp → SalesforceBrings Mailchimp campaigns, audiences, automations and e-commerce orders into Data 360 in batches or through Zero Copy query federation (beta).
Sends to Databricks
Salesforce ⇄ DatabricksBrings Databricks data into Data 360 in batches or with Zero Copy query and file federation, and shares Data 360 data with Databricks through Lakehouse Federation.
Reads from Mailchimp
Mailchimp → TealiumWebhook data source. Sends Mailchimp list activity, including subscribes, unsubscribes, profile and email changes, cleaned addresses and campaign events, to Tealium AudienceStream through a list webhook.
Sends to Databricks
Tealium → DatabricksWrites event, visitor and log data to Databricks, staged through your own cloud storage on AWS, Azure or Google Cloud, singly or batched, from AudienceStream or EventStream.
Reads from Mailchimp
Mailchimp → Treasure AIImport. Imports Mailchimp lists with their members and member activity, plus campaigns, into Treasure Data with an API key or OAuth, using batch operations to ease rate limits.
Sends to Databricks
Treasure AI → DatabricksExport. Writes Treasure Data job results to a Databricks table in append, overwrite or replace mode, signing in with OAuth M2M or a deprecated personal access token.
Treasure AI → DatabricksOpen Catalog Access. Federates Treasure Data's Glue catalog of Iceberg tables into Databricks Unity Catalog so Databricks can query them without copies, an Open Catalog Access option enabled on request.
The other way: Databricks to Mailchimp
13 CDPsEach of these CDPs lists a connector that reads from Databricks and one that sends data to Mailchimp.
Reads from Databricks
Databricks → ActionIQLayers ActionIQ's CDP on top of Databricks through native reverse ETL, mapping to customer data where it lives so business users can work with it without copying it into the CDP.
Sends to Mailchimp
ActionIQ → MailchimpMailchimp
Reads from Databricks
Databricks → AdobeBrings Databricks data into Experience Platform for Real-Time CDP Ultimate customers.
Sends to Mailchimp
Adobe → MailchimpEvent forwarding. Sends events server-side to the Mailchimp Marketing API through event forwarding, where they can trigger emails from campaigns, customer journeys or transactional sends.
Adobe → MailchimpInterest Categories. Sends Real-Time CDP audiences to Mailchimp as interest categories named after each audience, adding or updating contacts and moving them in or out of groups.
Adobe → MailchimpTags. Sends Real-Time CDP audiences to Mailchimp as tags named after each audience, adding new contacts or tagging existing ones within a chosen Mailchimp audience.
Reads from Databricks
Amperity ⇄ DatabricksShares tables both ways between Amperity and Databricks through Amperity Bridge, using the OpenSharing protocol, an evolution of Delta Sharing, instead of file copies or ETL jobs.
Sends to Mailchimp
Amperity → MailchimpManages Mailchimp audiences from Amperity through the Mailchimp Marketing API, keyed by email address.
Reads from Databricks
BlueConic ⇄ DatabricksImports and exports BlueConic profiles, groups and timeline events with a Databricks workspace through Delta Sharing up to six times a day, offered as a paid upgrade.
Sends to Mailchimp
BlueConic ⇄ MailchimpImports Mailchimp audience members and mail activity into BlueConic and exports segment profiles to selected Mailchimp audiences in scheduled or manual batch runs.
Reads from Databricks
Databricks → DinMoConnects a Databricks SQL warehouse or all-purpose cluster on AWS, Azure or GCP to DinMo with a personal access token, so DinMo can read your tables and write its own technical schemas.
Sends to Mailchimp
DinMo → MailchimpCreates Mailchimp segments inside a chosen contact list from DinMo segments and keeps them current by email for existing contacts, rebuilding a segment from scratch on historical refresh.
Reads from Databricks
Databricks → Fivetran ActivationsSource. Uses Databricks, Unity Catalog included, as a Fivetran Activations source through a service principal or personal access token, on the Basic or Advanced Sync Engine.
Sends to Mailchimp
Fivetran Activations → MailchimpAdds and updates Mailchimp audience members by email from Fivetran Activations after you sign in to Mailchimp, with a required status such as subscribed or unsubscribed.
Reads from Databricks
Databricks → HightouchSource. Connects Databricks to Hightouch as a source, so SQL, dbt or table-based models built there can sync to any destination.
Sends to Mailchimp
Hightouch → MailchimpKeeps Mailchimp audiences in sync with warehouse segments for personalized and automated email.
Reads from Databricks
Lytics ⇄ DatabricksImports Databricks tables into Lytics, loads audiences, events, audience changes, system events and metrics into Delta tables, and can back Lytics Cloud Connect audiences.
Sends to Mailchimp
Lytics ⇄ MailchimpImports Mailchimp subscribers and campaign activity into Lytics every 12 hours and exports Lytics audiences to Mailchimp, with campaigns importable as Lytics Experiences.
Reads from Databricks
Databricks → mParticleWarehouse Sync. Ingests user and event tables, but not views, from Databricks into mParticle through Delta Sharing, as one-time or recurring syncs.
Reads from Databricks
Databricks → RudderStackSource. Reads Databricks tables or SQL models with RudderStack Reverse ETL and activates the results in marketing and sales tools.
Sends to Mailchimp
RudderStack → MailchimpAdds and updates Mailchimp audience members from RudderStack users and records their events.
Reads from Databricks
Databricks → SegmentData Graph. Links Databricks catalogs to Segment's Data Graph through a service principal that reads them and writes checkpoint tables to a catalog of its own, for Linked Audiences and Linked Events.
Databricks → SegmentReverse ETL source. Connects a Databricks SQL warehouse to Segment Reverse ETL through a service principal, with OAuth machine-to-machine sign-in required for any new source.
Sends to Mailchimp
Segment → MailchimpDestination. Sends identify calls from Segment to Mailchimp for email marketing in cloud mode.
Reads from Databricks
Databricks → TealiumCloud data source. Imports a Databricks table into Tealium attributes, connecting to a SQL warehouse on AWS, Azure or GCP with a service principal's OAuth secret rather than a personal access token.
Databricks → TealiumDelta Sharing data source. Shares Databricks tables with Tealium through Databricks-to-Databricks Delta Sharing, in early access, so no credentials leave Databricks and CloudStream can read the data without copying it.
Sends to Mailchimp
Tealium → MailchimpSubscribes or unsubscribes Mailchimp list members and upserts e-commerce orders and abandoned carts from AudienceStream.
Reads from Databricks
Databricks → Treasure AIAI Studio connection. Gives Treasure AI Studio agents query and charting access to a Databricks lakehouse in chat, through a Databricks OAuth app that each user authorizes for their own connection.
Databricks → Treasure AIComposable Audience Studio. Runs Composable Audience Studio parent segments on Databricks Unity Catalog tables with federated queries and service principal OAuth, so audiences are built without copying data.
Databricks → Treasure AIImport. Imports Databricks tables or custom SELECT query results into Treasure Data, with filter conditions and incremental columns, over OAuth M2M or a personal access token.
Databricks → Treasure AILive Connect zero-copy. Reads Databricks tables shared over Delta Sharing into Treasure Data, by default in memory, for ID unification and activations, a Live Connect zero-copy option enabled on request.
Sends to Mailchimp
Treasure AI → MailchimpExport. Adds Treasure Data segments to a Mailchimp list or updates existing members by email, filling merge fields and interest groups, signing in with an API key or OAuth.
Get an email when these routes change
CdpHub Pro will alert you when a CDP adds, renames or retires a connector between Mailchimp and Databricks. Join the waitlist for early access.
Mailchimp and the other warehouses
- Mailchimp to Snowflake9 CDPs
- Mailchimp to BigQuery8 CDPs
- Mailchimp to Amazon Redshift8 CDPs
More into Databricks
- Klaviyo to DatabricksDirect · 6 CDPs
- HubSpot to Databricks12 CDPs
- Salesforce to Databricks12 CDPs
- Shopify to Databricks14 CDPs
About these numbers
CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. A route counts a CDP that lists a connector reading from one end and another sending data to the other: a possible path, not a tested one. What travels, how often and in which format depends on each connector and its plan, so follow the documentation links. Counts are updated as catalogs change; this page reflects the directory as of October 23, 2026. CdpHub is independent and not affiliated with Mailchimp, Databricks or any platform listed.
Getting Mailchimp data into Databricks?
Vendor-neutral help choosing the route that fits your stack, and getting the connection running.