New: The Agentic CDP

·Read the analysis

Connect · Data warehouse

Mailchimp to Amazon Redshift

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 Amazon Redshift, so they can sit between the two, and 13 go the other way, from Amazon Redshift to Mailchimp.

8CDPs can carry Mailchimp data into Amazon Redshift
13CDPs can carry Amazon Redshift data to Mailchimp
20of 44 CDPs list Mailchimp
28of 44 CDPs list Amazon Redshift

CDPs that can carry Mailchimp data into Amazon Redshift

8 CDPs

Each of these CDPs lists a connector that reads from Mailchimp and one that sends data to Amazon Redshift. 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 ⇄ Mailchimp

    Imports Mailchimp audience members and mail activity into BlueConic and exports segment profiles to selected Mailchimp audiences in scheduled or manual batch runs.

    Sends to Amazon Redshift

    BlueConic ⇄ Amazon Redshift

    Imports Amazon Redshift tables or SQL query results into BlueConic profiles, orders, events and groups, and exports profiles in sync, replace or append mode staged through Amazon S3.

  • Reads from Mailchimp

    Mailchimp → Klaviyo

    Migrates 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 Amazon Redshift

    Klaviyo → Amazon Redshift

    Exports Klaviyo profiles and events to an Amazon Redshift instance, with the option to leave out events from integrations that already feed Redshift.

  • Reads from Mailchimp

    Lytics ⇄ Mailchimp

    Imports Mailchimp subscribers and campaign activity into Lytics every 12 hours and exports Lytics audiences to Mailchimp, with campaigns importable as Lytics Experiences.

    Sends to Amazon Redshift

    Lytics ⇄ Amazon Redshift

    Imports user tables from Amazon Redshift into Lytics over a PostgreSQL connection and keeps a Redshift table of a Lytics audience updated by loading files staged in S3.

  • Reads from Mailchimp

    Mailchimp → mParticle

    Feed. Brings Mailchimp email events into mParticle as a feed through a Mailchimp webhook.

    Sends to Amazon Redshift

    mParticle → Amazon Redshift

    Loads all incoming mParticle data into an Amazon Redshift cluster, so you can query events and user data with SQL.

  • Reads from Mailchimp

    Mailchimp → Salesforce

    Brings Mailchimp campaigns, audiences, automations and e-commerce orders into Data 360 in batches or through Zero Copy query federation (beta).

    Sends to Amazon Redshift

    Salesforce ⇄ Amazon Redshift

    Connects Data 360 and Amazon Redshift through Zero Copy, querying Redshift tables in place and sharing Data 360 data back to Redshift.

  • Reads from Mailchimp

    Mailchimp → Segment

    Source. Pulls Mailchimp objects into Segment on a schedule for syncing to a warehouse.

    Sends to Amazon Redshift

    Segment → Amazon Redshift

    Loads Segment event data into Amazon Redshift on a schedule as a storage destination, ready for SQL analysis.

  • Reads from Mailchimp

    Mailchimp → Tealium

    Webhook 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 Amazon Redshift

    Tealium → Amazon Redshift

    Loads full or custom event and visitor data into Amazon Redshift tables in micro-batches or batches, from AudienceStream or EventStream.

  • Reads from Mailchimp

    Mailchimp → Treasure AI

    Import. 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 Amazon Redshift

    Treasure AI → Amazon Redshift

    Export. Writes Treasure Data job results to tables in an existing Amazon Redshift cluster over JDBC, with no support for timestamp or date columns, which you must first convert to strings or Unix time.

The other way: Amazon Redshift to Mailchimp

13 CDPs

Each of these CDPs lists a connector that reads from Amazon Redshift and one that sends data to Mailchimp.

  • Reads from Amazon Redshift

    Amazon Redshift → ActionIQ

    Connects ActionIQ to Amazon Redshift with HybridCompute, pushing generated SQL down to the warehouse and returning only the needed results, usually customer IDs, without copying the data.

    Sends to Mailchimp

    ActionIQ → Mailchimp

    Mailchimp

  • Reads from Amazon Redshift

    Amazon Redshift → Adobe

    Brings Amazon Redshift data into Experience Platform for Real-Time CDP Ultimate customers.

    Sends to Mailchimp

    Adobe → Mailchimp

    Event 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 → Mailchimp

    Interest 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 → Mailchimp

    Tags. 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 Amazon Redshift

    BlueConic ⇄ Amazon Redshift

    Imports Amazon Redshift tables or SQL query results into BlueConic profiles, orders, events and groups, and exports profiles in sync, replace or append mode staged through Amazon S3.

    Sends to Mailchimp

    BlueConic ⇄ Mailchimp

    Imports Mailchimp audience members and mail activity into BlueConic and exports segment profiles to selected Mailchimp audiences in scheduled or manual batch runs.

  • Reads from Amazon Redshift

    Amazon Redshift → DinMo

    Connects Amazon Redshift, provisioned or Serverless, to DinMo as the source for models, segments and activations, reached directly or through AWS PrivateLink, an SSH tunnel or SSM.

    Sends to Mailchimp

    DinMo → Mailchimp

    Creates 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 Amazon Redshift

    Amazon Redshift → Fivetran Activations

    Source. Extracts Amazon Redshift tables and views for Fivetran Activations syncs with the UNLOAD command, which in a VPC deployment needs an S3 VPC endpoint.

    Sends to Mailchimp

    Fivetran Activations → Mailchimp

    Adds 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 Amazon Redshift

    Amazon Redshift → Hightouch

    Source. Connects Amazon Redshift to Hightouch as a source, so SQL, dbt or table-based models built there can sync to any destination.

    Sends to Mailchimp

    Hightouch → Mailchimp

    Keeps Mailchimp audiences in sync with warehouse segments for personalized and automated email.

  • Reads from Amazon Redshift

    Lytics ⇄ Amazon Redshift

    Imports user tables from Amazon Redshift into Lytics over a PostgreSQL connection and keeps a Redshift table of a Lytics audience updated by loading files staged in S3.

    Sends to Mailchimp

    Lytics ⇄ Mailchimp

    Imports Mailchimp subscribers and campaign activity into Lytics every 12 hours and exports Lytics audiences to Mailchimp, with campaigns importable as Lytics Experiences.

  • Reads from Amazon Redshift

    Amazon Redshift → mParticle

    Warehouse Sync. Brings user and event data from Amazon Redshift or Redshift Serverless into mParticle, with access through an IAM role that mParticle assumes.

    Sends to Mailchimp

    mParticle → Mailchimp

    Audiences. Keeps Mailchimp lists in step with mParticle audiences through Mailchimp's v3 API.

    mParticle → Mailchimp

    Events. Forwards mParticle events and user data to Mailchimp for email campaign targeting and tracking.

  • Reads from Amazon Redshift

    Amazon Redshift → RudderStack

    Source. Reads tables or SQL models from Amazon Redshift with RudderStack Reverse ETL and syncs the rows to downstream tools on a schedule.

    Sends to Mailchimp

    RudderStack → Mailchimp

    Adds and updates Mailchimp audience members from RudderStack users and records their events.

  • Reads from Amazon Redshift

    Amazon Redshift → Segment

    Data Graph. Connects a Redshift cluster to Segment's Data Graph through its own role and user, so Linked Audiences and Linked Events can use warehouse entity tables next to Profiles Sync data.

    Amazon Redshift → Segment

    Reverse ETL source. Lets Segment Reverse ETL query an Amazon Redshift cluster as a dedicated database user and send the results to destinations, keeping sync state in its own schema.

    Sends to Mailchimp

    Segment → Mailchimp

    Destination. Sends identify calls from Segment to Mailchimp for email marketing in cloud mode.

  • Reads from Amazon Redshift

    Amazon Redshift → Tealium

    Cloud data source. Reads a table or view from an Amazon Redshift cluster into Tealium attributes over JDBC, using the cluster's hostname, port, database, schema and credentials.

    Sends to Mailchimp

    Tealium → Mailchimp

    Subscribes or unsubscribes Mailchimp list members and upserts e-commerce orders and abandoned carts from AudienceStream.

  • Reads from Amazon Redshift

    Amazon Redshift → Treasure AI

    Import. Imports a table from Amazon Redshift into Treasure Data with an optional WHERE condition, and can load only rows added since the last scheduled run.

    Amazon Redshift → Treasure AI

    Live Connect zero-copy. Runs federated Trino queries from Treasure Data against Amazon Redshift tables through a Live Connect zero-copy source, once enabled, keeping results seven days unless saved.

    Sends to Mailchimp

    Treasure AI → Mailchimp

    Export. 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.

  • Reads from Amazon Redshift

    Amazon Redshift → Zeta Global

    Queries Amazon Redshift provisioned clusters from Zeta Data Flows to ingest selected data, connecting with host, port and database plus optional IAM authentication.

    Sends to Mailchimp

    Zeta Global → Mailchimp

    Pushes Zeta customers to Mailchimp through a Channel Manager channel following the Mailchimp Lists API, authenticated as Mailchimp's developer docs describe, from Experiences.

Get an email when these routes change

CdpHub Pro will alert you when a CDP adds, renames or retires a connector between Mailchimp and Amazon Redshift. Join the waitlist for early access.

Join the Pro waitlist →

Mailchimp and the other warehouses

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, Amazon Redshift or any platform listed.

Getting Mailchimp data into Amazon Redshift?

Vendor-neutral help choosing the route that fits your stack, and getting the connection running.

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy