Migrate from Mailchimp to another ESP

[fmvilas]

Mailchimp is very expensive and we're just running the newsletter and the notifications through it. Any ESP (Email Service Provider) will allow us to do that and there are many to choose from. Particularly, I'd recommend going with Kit (previously ConvertKit). I've been using it for about a year now and it's amazing and its API is really good. It's more than we need and it will be free for our amount of subscribers (which is a bit more than 2K).

AFAIK, this would require changing a few things:

• Website: newsletter subscription form (through Netlify functions IIRC)
• Website & GH Actions: TSC notifications subscription (through Netlify functions IIRC)
• Website & GH Actions: events notifications subscription (through Netlify functions IIRC)

[Shurtu-gal]

There is another one "voting tsc notification" that are currently being sent using mailjet ( they are also free ).

[brijesh025]

@fmvilas i want to work on this issue, please let me know if you can assign this issue to me so i can start working on this issue.

[Aditya-twd]

Hi @fmvilas! @Shurtu-gal I'd like to work on this. I've been contributing to AsyncAPI CLI error messages recently. Happy to take this on.

[Aditya-twd]

@fmvilas Is this the Mailchimp issue causing the newsletter subscription problem? I'm trying to join the newsletter but getting a "subscription failed" error. Is this related to the migration work you mentioned?

[sammy200-ui]

Hi @fmvilas ! I took a look through the codebase and planned the Kit migration.

I tracked down the logic in netlify/functions/newsletter_subscription.ts. It currently uses the @mailchimp/mailchimp_marketing SDK and relies on config/mailchimp-config.json to map user interests (Newsletter, Meetings, etc.) to specific IDs.

I have a refactor plan ready to go:

Remove the heavy Mailchimp SDK dependency.
Implement a lightweight axios call to the https://api.convertkit.com/v3/forms/{formId}/subscribe endpoint.
Update Config: We can keep the existing config.json structure but simply rename the keys to map to Kit Form IDs instead of Mailchimp Interest IDs.