# Klaviyo vs Mailchimp: choose by your store data, your flows and the bill at your list size

Canonical URL: https://www.martechdevs.com/blog/klaviyo-vs-mailchimp

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder at [Martechdevs](https://www.martechdevs.com) and [Growth and Analytics Partners](https://www.growthandanalytics.com)

[LinkedIn](https://linkedin.com/in/jafrinalo)

Published: 2026-10-17

Last updated: 2026-10-17

Choose Klaviyo first when your store needs closely managed purchase, checkout and retention journeys. Shortlist Mailchimp first for a newsletter-led business, then test its current commerce automations rather than assuming they are basic. The useful comparison is the same customer data, send workload and failure cases in both tools, with introductory discounts removed from the renewal budget.

## When should you choose Klaviyo or Mailchimp?

Klaviyo is my first pilot for a DTC store with a dedicated lifecycle operator; Mailchimp is my first pilot for a service business whose main job is publishing offers and newsletters. These are operating-fit judgments. Neither label proves that the other tool cannot do the work.

Mailchimp now documents Shopify abandoned-cart, abandoned-checkout and browse triggers. Its integration can use product, customer and order data. A recommendation based on “Mailchimp cannot run ecommerce flows” would be outdated. [Mailchimp's Shopify triggers](https://mailchimp.com/help/all-the-starting-points/), [store integration](https://mailchimp.com/help/connect-shopify/).

Klaviyo's Shopify integration also brings customer and order data into the platform, with onsite tracking and signup forms. The useful question is which implementation gives your operator the right trigger, customer context and stop condition with manageable maintenance. [Klaviyo's Shopify integration](https://help.klaviyo.com/hc/en-us/articles/115005080407).

At Martechdevs, our [lifecycle and CRM implementation](https://www.martechdevs.com/crm-lifecycle) work connects those rules to the store and verifies the resulting messages. Start with the acceptance test below before commissioning a large flow rebuild.

For a SaaS product with account relationships and product events, evaluate [Customer.io against Klaviyo](https://www.martechdevs.com/blog/customer-io-vs-klaviyo). The [Braze and Customer.io comparison](https://www.martechdevs.com/blog/braze-vs-customer-io) expands that shortlist for broader lifecycle orchestration.

A sales-led business may need a CRM-owned follow-up process alongside its email platform. If neither candidate fits, use the [Klaviyo alternatives guide](https://www.martechdevs.com/blog/klaviyo-alternatives) to change the shortlist around the unmet job.

## What are the practical pros and cons of each platform?

Klaviyo earns its place when store-event journeys are worth operating in detail; Mailchimp earns its place when its campaign and automation workflow covers the job at a defensible recurring cost. Product limits and prices in this comparison were checked on 17 October 2026.

### Klaviyo

- **Best for:** A store with an owner for acquisition, post-purchase and retention flows.
- **Pros:** Store data can drive lifecycle work; email and mobile messaging can share customer context; the monthly plan can be estimated by active profiles and sends.
- **Cons:** Someone must maintain event quality and exclusions; mobile usage adds a separate bill; Free email support ends after its initial support period.
- **Free tier and startup offer:** The Free plan supports a small test. No standing startup discount is assumed in the budget below.
- **Choose it if:** Your actual store-data tests pass and the recurring work is justified by useful customer journeys.
- **Skip it if:** Most of the proposed flows would remain unowned, or a simpler setup already passes every required test.

### Mailchimp

- **Best for:** A newsletter, service or small-business operator who also needs a defined set of automations.
- **Pros:** The current Shopify integration supports commerce triggers; paid send capacity is explicit; an eligible introductory offer reduces initial subscription cost.
- **Cons:** Unsubscribed and non-subscribed contacts can remain billable; duplicates across audiences increase the count; the promotion ends while the operational work continues.
- **Free tier and startup offer:** Free is suitable for a limited sending test. The paid introductory promotion is an eligibility-based offer, not a permanent startup entitlement.
- **Choose it if:** The operator can build, diagnose and maintain the required campaigns and flows within the chosen plan.
- **Skip it if:** A required flow or integration fails the pilot, even after the correct paid tier is tested.

### Which platform fits each business model?

These are shortlist decisions, not a ranking of every feature:

| Business situation | First pilot | Runner-up | What should decide it |
| --- | --- | --- | --- |
| Shopify store with a lifecycle marketer | Klaviyo | Mailchimp Standard | Required order fields, suppression and operator effort |
| Service business publishing a weekly newsletter | Mailchimp | Klaviyo | Campaign production, contact organisation and ongoing cost |
| Store already using Mailchimp with working flows | Improve the existing setup | Klaviyo migration pilot | A measured gap that repays the rebuild and overlap cost |
| SaaS with several workspaces per customer | Customer.io evaluation | Either tool only after the account test | Correct account context, membership changes and stop rules |

## What do the free plans actually prove?

Both free plans can prove a small email workflow, but their limits cannot establish the economics of a larger store. The allowances below are monthly unless a daily limit is stated, checked on 17 October 2026; dollar credits are USD and have channel-specific purchasing power.

| Free-plan constraint | Klaviyo | Mailchimp | Evaluation consequence |
| --- | --- | --- | --- |
| Audience allowance | 250 active profiles | 250 contacts | Reconcile the vendor's meter before importing |
| Email sends | 500 per month | 500 per month; 250 per day | Keep the test below both audience and send limits |
| Other included usage | USD 5 mobile messaging; USD 5 Composer | SMS requires a paid add-on in supported countries | Compare the same channel and destination |
| Initial email support | First 60 days | First 30 days | Test operator handover before support changes |

Sources: [Klaviyo pricing](https://www.klaviyo.com/pricing) and [Mailchimp pricing](https://mailchimp.com/pricing/marketing/).

Mailchimp explicitly says Free sending pauses when the contact or send limit is exceeded. Its page also retains an older sentence suggesting Free for fewer than 500 contacts; use the current 250-contact plan card and confirm your account's allowance. Klaviyo also blocks additional messages after Free limits are reached; its [pricing FAQ](https://www.klaviyo.com/pricing) directs users to wait for the next cycle or upgrade.

On paid self-service Klaviyo, exceeding the profile allowance can trigger a profile-compliant tier next cycle. That does not remove email-send limits. The billing preference determines whether sending stops, the account upgrades or flexible overages add capacity. [Klaviyo billing](https://help.klaviyo.com/hc/en-us/articles/115000976672).

Treat a free test as evidence about a particular workflow. If it omits your required volume, support, automation depth or SMS destination, price and test those requirements separately.

## Why can the same customer list produce different bills?

Klaviyo active profiles and Mailchimp billable contacts are different counts. Newsletter membership alone is insufficient for either forecast.

Klaviyo's active count can include emailable, unsuppressed profiles created through checkout or other engagement without newsletter opt-in. Billing eligibility does not establish permission for promotional messaging. [Klaviyo's active-profile definition](https://help.klaviyo.com/hc/en-us/articles/24263920096027) explains the distinction. Use the [active-profile billing and cleanup guide](https://www.martechdevs.com/blog/klaviyo-active-profiles) to reconcile source, consent and suppression state. [Klaviyo billing rules](https://help.klaviyo.com/hc/en-us/articles/115000976672).

For Mailchimp's current pricing model, subscribed, unsubscribed and non-subscribed contacts count; cleaned, pending and archived contacts do not. Legacy plans can differ. [Mailchimp contact types](https://mailchimp.com/help/about-your-contacts/). The same address in two audiences counts twice, so a second audience is not a free organisational container. [Audience counting](https://mailchimp.com/help/create-audience/).

Mailchimp's monthly bill also uses the peak contact total during the billing period. Archiving after the peak does not rewrite that month's history. Paid overages use additional contact blocks, whose allowance and price depend on the plan and tier. [Additional charges](https://mailchimp.com/help/about-additional-charges/).

Consider a hypothetical database with 5,000 subscribed addresses, 800 unsubscribed addresses and 200 non-subscribed store contacts, all distinct and unarchived. Mailchimp counts 6,000 under those rules. You cannot quote its 5,000-contact tier for that database simply because only 5,000 people are in the newsletter audience.

Before comparing calculators:

1. Export status and source fields at the same timestamp.
2. Count the records each vendor would bill, including cross-audience duplication.
3. Identify records that should remain stored but should not receive marketing.
4. Review archive or suppression decisions with the customer-journey owner.
5. Recheck the processed billing count and the next effective plan.

Deleting records to force a price comparison destroys useful evidence. Fix the source of unnecessary profile creation and preserve permission history.

## What do 5,000 and 25,000 billable contacts cost?

At 5,000 billable contacts, the checked Klaviyo email plan and Mailchimp Standard both cost USD 100 per month before Mailchimp's introductory offer. At 25,000, they show USD 400 and USD 310 respectively. These are the same numerical audience sizes under each vendor's own meter, not a claim that one imported file produces identical counts. For the hypothetical workload, assume 40,000 emails a month at 5,000 billable records and 200,000 at 25,000, within both listed plans.

The live calculators were checked on 17 October 2026 with USD selected. Prices below are per month on monthly billing, before tax, overages, SMS, other products and implementation. The Mailchimp first-year figures model its 50% offer for an eligible account; the ongoing column is today's list price, which can change before renewal. Mailchimp also documents a separate 15% offer for 10,000-plus contacts. Use the offer confirmed for your account, not a universal first-year discount.

| Plan and billable audience | Email sends/month | First 12 months with Mailchimp 50% offer, USD/month | Current ongoing rate, USD/month |
| --- | ---: | ---: | ---: |
| Klaviyo email; 5,000 active profiles | 50,000 | 100 | 100 |
| Mailchimp Standard; 5,000 contacts | 60,000 | 50 | 100 |
| Klaviyo email; 25,000 active profiles | 250,000 | 400 | 400 |
| Mailchimp Standard; 25,000 contacts | 300,000 | 155 | 310 |

[Current Klaviyo calculator](https://www.klaviyo.com/pricing), [current Mailchimp calculator](https://mailchimp.com/pricing/marketing/).

Mailchimp Essentials showed lower ongoing prices of USD 75 and USD 270 at these sizes, with monthly sends of 50,000 and 250,000. Its smaller flow-step allowance may be enough for a simple sequence. Choose the required automation tier before comparing totals; the cheapest plan is irrelevant if the journey cannot be represented in it.

The two-year calculation below holds audience, workload and current list prices constant. Amounts are annual USD subscription costs before tax, using the monthly rates checked on 17 October 2026; twelve monthly payments make each year.

| Email-only scenario | Year one, USD | Year two, USD | Two years, USD |
| --- | ---: | ---: | ---: |
| Klaviyo, 5,000 profiles | 1,200 | 1,200 | 2,400 |
| Mailchimp Standard, 5,000 contacts, eligible 50% offer | 600 | 1,200 | 1,800 |
| Klaviyo, 25,000 profiles | 4,800 | 4,800 | 9,600 |
| Mailchimp Standard, 25,000 contacts, eligible 50% offer | 1,860 | 3,720 | 5,580 |

The [50% offer terms](https://mailchimp.com/legal/promotional-offer-terms/) limit eligibility to new customers or qualifying Free customers within 90 days of account creation in selected countries. The discount lasts twelve months from enrolment, applies to the monthly base price and qualifying contact add-on blocks, and excludes SMS and transactional email. Pausing does not stop the promotional clock. A new account is not automatically eligible in every country.

### How should SMS enter the model?

Add a destination-specific SMS workload as a separate line. The checked Klaviyo estimator priced 2,900 monthly US toll-free SMS messages at USD 40, with other mobile channels at zero; its note says applicable carrier fees are included in the estimate. That makes the illustrated email-plus-SMS totals USD 140 at 5,000 profiles or USD 440 at 25,000. Twelve unchanged months add USD 480 to the email-only annual budget.

Do not apply that rate to another country, MMS, a long multipart message or a different sender type. Mailchimp SMS requires a paid plan and supported sending country, with credits purchased separately. Obtain the same destination and message-shape estimate before declaring either combined package cheaper. [Mailchimp SMS scope](https://mailchimp.com/pricing/marketing/).

At 25,000 profiles the current ongoing email gap is USD 90 per month, or USD 1,080 annually. Using only that ongoing saving, a hypothetical USD 3,000 migration has a simple payback of about 33.3 months, excluding introductory discounts, overlap and operating changes. This is a planning calculation, not a Martechdevs quote or a revenue forecast.

## Which flow tests should decide the purchase?

Build checkout recovery, post-purchase follow-up and replenishment around the same store records in both pilots. Compare the data available at the decision point, including what changes while a customer waits.

| Journey | Data to inspect | Deliberate edge case | Passing result |
| --- | --- | --- | --- |
| Checkout recovery | Cart or checkout identity, products, price and eligible discount | Purchase completes during the delay | Reminder stops and the customer receives no stale offer |
| Post-purchase | Order state, items and fulfilment context | Order is refunded or cancelled | Follow-up changes or stops under the agreed policy |
| Replenishment | Product-specific expected repeat interval and later orders | Another order arrives before the reminder | Timing reflects the relevant product and current purchase history |

Mailchimp distinguishes Shopify cart, checkout and browse triggers, and requires its latest Shopify integration for those triggers. Verify the actual fields and filters rather than treating the trigger name as the whole contract. Klaviyo's integration also needs its real store-data path tested. Use the vendor integration references above and the [Klaviyo setup mistakes guide](https://www.martechdevs.com/blog/klaviyo-implementation-mistakes) to investigate missing or duplicated events.

For each test, retain the source order, event timestamp, recipient, flow entry, decision state and eventual message or suppression. Ask a second operator to diagnose one missing message without the person who built it. A flow that only its creator can explain is an ongoing staffing requirement.

## Why will attributed revenue differ from Shopify or GA4?

Email-platform revenue assigns credit under attribution rules, while Shopify order revenue and GA4 measurement answer different questions. Reconcile orders first, then compare which interactions each platform credits.

Klaviyo currently documents last-touch attribution with configurable windows and historical recalculation after settings change. Its new-account defaults include five-day email-click and email-open windows. Mailchimp also uses a last-touch model with configurable email and SMS interaction windows; its ecommerce reports exclude shipping and tax from net revenue. [Klaviyo attribution](https://help.klaviyo.com/hc/en-us/articles/1260804504250), [Mailchimp attribution](https://mailchimp.com/help/about-mailchimp-attribution/).

In a hypothetical order worth USD 100 before tax and shipping, a customer clicks an email, later clicks a paid ad and then buys. An email platform and an advertising platform may both claim the order under their respective rules. Adding the two credited amounts would not produce another USD 100 of revenue.

Compare order IDs, currency, refunds, tax, shipping, event dates, reporting timezone, eligible interactions and attribution windows. The [GA4 and Shopify revenue reconciliation guide](https://www.martechdevs.com/blog/ga4-shopify-purchase-mismatch) develops the measurement side. Use an appropriately designed holdout to estimate incremental impact; an attribution total alone cannot establish it.

## What should you verify about AI, integrations and contracts?

Verify the exact product, role and action you intend to use. An AI label or MCP endpoint does not establish access to every account operation.

Klaviyo's remote MCP supports account access for Owner, Admin or Manager roles. Its custom-connector query parameter `read-only=true` disables write tools; listed connectors do not expose those query controls. [Klaviyo connection documentation](https://developers.klaviyo.com/en/docs/connect_to_the_klaviyo_mcp_server). Use the [Klaviyo MCP guide](https://www.martechdevs.com/blog/klaviyo-mcp-server) for an investigation workflow with appropriate access.

Mailchimp's [Marketing documentation MCP](https://mailchimp.com/developer/marketing/build/ai-tools/mcp-server) searches published documentation. Its separate [Transactional MCP](https://mailchimp.com/developer/transactional/guides/how-to-use-mailchimps-transactional-messaging-mcp) can call Transactional API operations. Keep those products distinct when evaluating account access. Test a useful report or draft and inspect its evidence before adding writes.

Mailchimp's pricing page says annual Standard and Premium options are available through sales at 10,000-plus contacts. Do not infer those terms from the monthly promotion. Klaviyo's self-service billing rules also differ from manually billed contracts. Record the actual renewal, overage, cancellation and support terms for the account you will buy.

## What do current reviewers highlight?

The inspected reviews support testing segmentation, campaign production and operator learning effort. They do not prove that either platform will create a particular revenue result.

These G2 snapshots were checked on 17 October 2026. Ratings are out of five; counts refer to the cited pages, whose snapshots can differ as reviews are added.

| Product | G2 rating | Review count | Themes to test in your pilot |
| --- | ---: | ---: | --- |
| Klaviyo | 4.6 | 1,368 | Segmentation and store integration; advanced-flow learning effort and pricing |
| Intuit Mailchimp Email Marketing | 4.3 | 12,993 | Email creation and audience organisation; integration fit and growing list costs |

The [Klaviyo page](https://www.g2.com/products/klaviyo/reviews?page=6&qs=pros-and-cons) includes individual comments about useful segmentation, setup learning and a poor fit for quote-based businesses. The [Mailchimp page](https://www.g2.com/products/intuit-mailchimp-email-marketing/reviews) includes small-business accounts of straightforward campaign creation alongside requests for specific integrations.

These are reported experiences. G2 labels some reviews as incentivised or seller-invited and others organic; inspect those labels and the reviewer's business model. The older 4.4 Mailchimp score in a May comparison is not the current product-page score. Use review complaints to write a disqualifying test rather than treating an aggregate star rating as a procurement result.

## How do you migrate without losing permissions or double-sending?

Move permissions and identity before activating the replacement journeys, and assign one sender to each message type during the overlap. Keep a rollback record that preserves new unsubscribes received during the move.

### Mailchimp to Klaviyo

Klaviyo's migration integration transfers subscriber details, unsubscribes and cleaned contacts, audiences as lists, campaign engagement and ratings. The initial campaign-history sync covers the last 90 days. Its guide warns that retaining the old Shopify connection in the wrong sequence can produce duplicate opt-in emails. Follow the documented connection order for the accounts involved. [Mailchimp-to-Klaviyo migration](https://help.klaviyo.com/hc/en-us/articles/115005254948).

There is a suppression exception: a profile already active in Klaviyo is not automatically suppressed when the corresponding Mailchimp record is cleaned or bounced. Reconcile those records and use the documented CSV suppression import for contacts that must remain suppressed before activating messages.

Rebuild and test flows; transferring contacts is not proof that every journey, template or consent rule moved correctly. Map Mailchimp audiences, tags and groups to the intended Klaviyo organisation, then reconcile a sample of subscribed, unsubscribed and excluded people before any campaign starts.

### Klaviyo to Mailchimp

Export the needed profile fields and permission evidence from Klaviyo, then import into the correct Mailchimp audience with explicit status mapping. Test a small fixture before the full audience. Mailchimp's [contact export guide](https://mailchimp.com/help/view-export-contacts/) explains its own status-separated export structure, which is useful for validating the destination and maintaining an exit record.

Rebuild the required automations using the current Shopify integration. Mailchimp warns that restarting some paused welcome automations can resend a welcome message to existing customers. Keep order notifications owned by one system to avoid duplicates. [Shopify connection and migration cautions](https://mailchimp.com/help/connect-shopify/).

### Shared cutover checks

1. Save permission status, source and timestamps, plus the applicable suppression records.
2. Establish the destination domain authentication and sending configuration.
3. Test representative records and the three journey edge cases above.
4. Assign which platform sends each campaign and flow during overlap.
5. Switch forms and remaining capture sources as a coordinated cutover, then reconcile new signups.
6. Confirm the new operating record before retiring old access or billing.

A sending-domain move requires the new provider's DNS configuration and a considered ramp. Preserve old records needed for other senders and follow the specific migration instructions. [Klaviyo's domain-migration guide](https://help.klaviyo.com/hc/en-us/articles/9042531198747) and the [bulk-sender requirements guide](https://www.martechdevs.com/blog/bulk-sender-requirements) cover that preparation. Keep [customer preferences](https://www.martechdevs.com/blog/customer-preference-centre) understandable after the move.

![The platform decision runs from revenue journeys to billable contacts and renewal pricing, then tests triggers and stop conditions; only passing journeys proceed to permission mapping, cutover and reconciliation.](https://www.martechdevs.com/assets/blog/klaviyo-vs-mailchimp.svg)

## What should be true before you approve the switch?

Approve the switch when the destination passes the journey tests and the subscription saving or operating improvement justifies the rebuild. Monitor signup capture, suppression parity, delivery complaints and reconciled orders after launch; a sent-email count alone is insufficient.

## Checklist

- [ ] Both bills use actual billable counts and forecast sends.
- [ ] Promotion eligibility, expiry and current full-price exposure are recorded.
- [ ] SMS uses the intended country, sender type and message volume.
- [ ] Checkout, post-purchase and replenishment tests include state changes.
- [ ] Permission and suppression samples reconcile before sending.
- [ ] Each message type has one active sender during overlap.
- [ ] Forms, authentication and rollback ownership have a cutover plan.
- [ ] Finance can distinguish attributed orders from total or incremental revenue.
- [ ] An operator can diagnose a missing message after handover.

Use [our two-tool selection method](https://www.martechdevs.com/blog/how-to-choose-martech-tools) to document the decision. Bring an unclear journey or billing mismatch to a [free martech audit](https://www.martechdevs.com/martech-ai-audit), or [request a lifecycle migration quote](https://www.martechdevs.com/crm-lifecycle#get-quote) with the flows, data sources and cutover constraints already identified.

## Frequently asked questions

### Does changing email platforms reset a customer's permissions?

No. Preserve the customer's existing choices and the evidence behind them when importing into the destination. Map email and mobile permissions separately, then test an unsubscribed record before activating a flow. If the destination cannot express a required preference, resolve that gap before using the imported address for marketing.

### Should Shopify keep sending order notifications during the move?

Choose one owner for each order-notification type and keep that ownership explicit during cutover. If Shopify already handles the required transactional notices correctly, a marketing-platform migration does not automatically require moving them. Test cancellation, refund and shipping cases so a second automation does not create duplicate or contradictory messages.

### Is a four-step automation allowance enough for a small business?

It can be if the complete required journey fits those steps and its stop conditions work. Sketch the actual trigger, waits, decisions and messages before choosing a plan. Do not remove a customer-protection rule merely to fit a cheaper tier; compare the price of the correct plan with keeping the existing workflow.

### Can historical engagement prove that a migration worked?

Historical opens and clicks can help preserve context, but they do not prove new messages or events are working. Test a fresh signup, a new order, an unsubscribe and a completed flow after cutover. Keep imported history labelled so it cannot be mistaken for activity generated by the new implementation.

### How should agency fees be compared with subscription savings?

Compare the complete one-time rebuild and overlap cost with the ongoing saving at the expected audience and send volume. Include the internal time needed for review and maintenance. If the project primarily improves journeys or reliability, describe those expected benefits separately instead of claiming that a small licence saving pays for the entire migration.

## Sources

1. [Klaviyo: Pricing and live plan calculator](https://www.klaviyo.com/pricing).

2. [Mailchimp: Pricing and live contact selector](https://mailchimp.com/pricing/marketing/).

3. [Mailchimp: Promotional offer terms](https://mailchimp.com/legal/promotional-offer-terms/).

4. [Klaviyo: How billing works](https://help.klaviyo.com/hc/en-us/articles/115000976672).

5. [Mailchimp: Contact types and billing eligibility](https://mailchimp.com/help/about-your-contacts/).

6. [Mailchimp: Audience creation and duplicate counting](https://mailchimp.com/help/create-audience/).

7. [Mailchimp: Additional charges and peak contact totals](https://mailchimp.com/help/about-additional-charges/).

8. [Mailchimp: Marketing automation flow triggers](https://mailchimp.com/help/all-the-starting-points/).

9. [Mailchimp: Shopify integration](https://mailchimp.com/help/connect-shopify/).

10. [Klaviyo: Shopify integration](https://help.klaviyo.com/hc/en-us/articles/115005080407).

11. [Klaviyo: Message attribution](https://help.klaviyo.com/hc/en-us/articles/1260804504250).

12. [Mailchimp: Attribution](https://mailchimp.com/help/about-mailchimp-attribution/).

13. [Klaviyo: MCP connection and access controls](https://developers.klaviyo.com/en/docs/connect_to_the_klaviyo_mcp_server).

14. [Mailchimp: Marketing documentation MCP](https://mailchimp.com/developer/marketing/build/ai-tools/mcp-server).

15. [Mailchimp: Transactional Messaging MCP](https://mailchimp.com/developer/transactional/guides/how-to-use-mailchimps-transactional-messaging-mcp).

16. [G2: Klaviyo reviews](https://www.g2.com/products/klaviyo/reviews?page=6&qs=pros-and-cons).

17. [G2: Intuit Mailchimp Email Marketing reviews](https://www.g2.com/products/intuit-mailchimp-email-marketing/reviews).

18. [Klaviyo: Migrate from Mailchimp](https://help.klaviyo.com/hc/en-us/articles/115005254948).

19. [Mailchimp: Contact export](https://mailchimp.com/help/view-export-contacts/).

20. [Klaviyo: Branded sending-domain migration](https://help.klaviyo.com/hc/en-us/articles/9042531198747).

21. [Klaviyo: Active profile management](https://help.klaviyo.com/hc/en-us/articles/24263920096027).