Does it work with our existing Mailchimp licenses?
Yes — the adapter rides on top of your existing Mailchimp subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
Can the Mailchimp adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Mailchimp tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
Is this a packaged Mailchimp connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
How long does the Mailchimp integration take to ship?
Our standard window is thirty days from signed scope to live Mailchimp adapter in production, plus a one-week monitored stabilization phase. For Aurora, Illinois, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Aurora, Illinois. After go-live, the Mailchimp adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Mailchimp adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.