Klaviyo List Migration: Suppression Handling Done Right

Direct answer: Klaviyo suppression handling during a list migration has one rule that overrides everything else: never import active subscribers with the "update subscription status to subscribed" option selected unless you have verified that every contact in that file has explicit, current consent. That setting rewrites the subscription status of every profile it touches — including profiles already suppressed in Klaviyo for hard bounces, opt-outs, or spam complaints. Sticky Digital, a Klaviyo Platinum Partner, treats suppression import as the first step of every migration and the most critical one to get right — because fixing a suppression mistake after your first campaign is significantly harder than preventing it.

How Klaviyo Handles Suppression — and Why It's Different From Most ESPs

Klaviyo separates suppression into five categories, each with different behavior and different rules about whether the suppression can be reversed. Understanding the distinction matters because not all suppressed contacts should be treated the same way during a migration.

Hard bounce suppressions are permanent and cannot be removed even if a contact tries to resubscribe. Klaviyo automatically suppresses a profile after a hard bounce — a permanent delivery failure caused by an invalid address or blocked domain — and that suppression persists. This is intentional. Sending to known hard bounces damages sender reputation on any platform, and Klaviyo's enforcement of this is stricter than most ESPs.

Soft bounce suppressions trigger automatically after seven or more consecutive soft bounces. Unlike hard bounces, these can resolve over time if the underlying delivery problem is fixed.

Spam complaint suppressions activate when a subscriber marks your mail as spam. These are the highest-priority deliverability suppressions in Klaviyo's hierarchy. They cannot be reversed by a contact resubscribing — only a manual unsuppression by an account administrator can change them, and doing so without investigating why the complaint happened is a mistake.

Manual suppressions are added by account administrators. They can be reversed, and a contact must actively resubscribe to receive mail again after being manually suppressed.

Global suppression is Klaviyo's default behavior — when a contact unsubscribes from any list in your account, they become blocked from all marketing emails across every list. This is different from list-level suppression, which Klaviyo only allows on paid plans and only when global unsubscribe is specifically disabled. For virtually all DTC brands migrating to Klaviyo, global suppression is what's in effect, and a contact who opts out of one email is opted out of everything.

The practical implication: your suppression list in Klaviyo is not list-specific. It's account-wide. Every contact you suppress is suppressed everywhere, permanently, until a specific action reverses it. That scope makes suppression hygiene during migration more consequential than it is on platforms where suppressions are list-contained.

The Import Setting That Overwrites Your Suppression Records

Klaviyo's list import flow includes a consent setting: "Yes, update subscription status for all imported contacts to subscribed." This option exists for situations where you've collected a fresh list of verified opt-ins and want to confirm their subscription status on import. What it also does is rewrite the subscription status of any existing profile it encounters in the import — including profiles that were already suppressed.

In practice: if a contact is globally suppressed in Klaviyo because they previously hard-bounced or opted out, and you import a CSV that includes their email address with this setting selected, Klaviyo will set their subscription status to subscribed. The prior suppression reason doesn't prevent this. The import treats the explicit instruction to mark contacts as subscribed as an override.

A jewelry brand we worked with had run a Klaviyo pilot with 8,000 contacts three months before their full migration. During the pilot, some contacts naturally opted out and a handful hard-bounced, building up a small suppression file. When the team did the full migration import — 90,000 contacts total — they selected "update subscription status to subscribed" to make the import process faster. Every opt-out from the pilot period was re-enabled. Their first post-migration campaign reached contacts who had explicitly unsubscribed. Complaint rates came in above 0.3 percent within 24 hours of the send.

The correct import setting for a migration is: do not select "update subscription status to subscribed" unless every contact in the file has fresh, documented consent and you've confirmed they are not already suppressed in Klaviyo. For most migrations, leave the consent setting as-is and use a separate suppression import to handle opt-outs and bounces before the active subscriber import begins.

What Goes to the Suppression List Before Anything Else

Four categories of contacts need to be in Klaviyo's suppression list before you import a single active subscriber. The sequence is non-negotiable:

Unsubscribes from your old platform. Export every contact who opted out on your previous ESP — global unsubscribes, list-level unsubscribes, preference center opt-outs — and import them to Klaviyo's suppression list first. Navigate to Audience, then Profiles, then View Suppressed Profiles, then Upload File. The CSV should have a single column of email addresses with "Email" as the header. No other data is required for suppression import.

Hard bounces from your old platform. Every email address that hard-bounced on the previous ESP needs to go into suppression before migration. These addresses permanently failed delivery — they're invalid, blocked, or non-existent — and sending to them on Klaviyo generates the same bounce that generates the same damage to sender reputation. Import them the same way as unsubscribes: a single-column CSV to the suppression upload tool.

Spam complaints from your old platform. If your previous ESP tracked complaint events — contacts who marked your mail as spam — those contacts go to suppression as well. On fresh infrastructure during warm-up, a complaint from a contact who already flagged you elsewhere is disproportionately damaging. Complaint rates during warm-up are scrutinized more heavily by inbox providers than complaint rates on established infrastructure.

GDPR and CCPA deletion requests. If your business serves EU, UK, or California residents, and you've received data deletion requests under GDPR or CCPA, those contacts cannot be imported to Klaviyo as active profiles. They need to be suppressed — or if they've requested erasure, not imported at all. This isn't a deliverability issue; it's a legal one. Migration is the moment when undocumented deletion requests get exposed, because the act of importing a contact who requested erasure creates the violation.

Proactive Suppression: The Warm-Up Tool Most Brands Miss

Suppression isn't just about protecting compliance. It's also one of the most effective tools for improving warm-up performance — and most brands treat it as purely reactive.

Your active subscriber list almost certainly contains contacts who are technically subscribed but haven't engaged in 12 or more months. They're not suppressed. They're not unsubscribed. They're just dormant. When you include them in your warm-up segments, they dilute open rates, inflate the denominator in your complaint rate calculations, and give inbox providers a less favorable signal than your genuinely active subscribers would generate on their own.

Before migration, we recommend running a proactive suppression pass on contacts who meet all three of these conditions: no opens in the last 12 months, no purchases in the last 12 months, and no click activity in the last 12 months. These contacts should go into Klaviyo as manually suppressed profiles rather than active subscribers. They're not gone — the profiles exist, the data is preserved, the history is intact — but they don't participate in warm-up sends until you've built enough reputation to absorb their lower engagement safely.

This is a different decision from the compliance-driven suppression above, and it's one teams should make deliberately rather than automatically. Some brands with high repeat purchase rates will want to preserve access to 12-month dormant contacts who might still be customers. Others with one-time purchase categories will find those contacts have no realistic path to re-engagement. The decision belongs to the strategist, not the import tool.

Verifying the Suppression Import Before You Send Anything

After importing suppression data, verify the count before touching active subscribers. Navigate to Audience, then Profiles, then View Suppressed Profiles. The number of suppressed profiles in Klaviyo should roughly match the number of records in your suppression import CSV. If there's a significant discrepancy — say, you imported 12,000 addresses but only 6,000 show as suppressed — the import may have encountered formatting errors, or the contacts may have already existed in Klaviyo with active subscription status that wasn't overridden by the suppression import.

Also verify suppression type. Klaviyo's suppression list view shows the reason for each suppression: hard bounce, manual, spam complaint, and so on. Contacts imported via the bulk suppression upload tool appear as manually suppressed. If you're expecting to see hard-bounce suppressions from your old platform, those will show as manual suppressions after a CSV import — Klaviyo doesn't carry over the original bounce event from another platform. That's fine for compliance purposes, but it's useful to know so the audit doesn't flag them as unexpected entries.

How Sticky Digital Handles Suppression Migration

Every Klaviyo migration we run starts with suppression before anything else in the platform is touched. We export four files from the old platform — unsubscribes, hard bounces, complaints, and any documented deletion requests — and import them as separate suppression uploads so we can audit each category independently. The active subscriber import doesn't begin until we've verified the suppression count matches expectations.

We also audit the import settings before every list upload. The "update subscription status to subscribed" option is only selected when the file has been reviewed and confirmed to contain no previously suppressed contacts. For most migrations, we leave that option unselected and rely on the suppression import to handle opt-out status rather than using the active subscriber import to manage both simultaneously.

The proactive suppression decision — whether to suppress dormant contacts before warm-up — is made during the program audit based on the client's business model and repeat purchase dynamics. For subscription brands, we're more conservative about suppressing dormant contacts because the lapse pattern is different. For single-purchase categories, we suppress more aggressively because re-engagement is statistically less likely and the warm-up benefit is immediate.

Our email and retention services include full suppression auditing and migration management. More on how we approach list health, warm-up sequencing, and suppression strategy is at the Sticky blog. If you're preparing a Klaviyo migration, start a conversation with us here.

FAQ

What happens if I import a suppressed contact as active in Klaviyo?

It depends on which import setting you use and the type of suppression. If you import with "update subscription status to subscribed" selected, the import will override existing manual and unsubscribe-based suppressions, re-enabling those contacts to receive mail. Hard bounce suppressions — the deliverability-category suppressions — generally persist through this, but opt-out suppressions do not. This is the most common suppression mistake in migrations, and it's difficult to audit retroactively because Klaviyo doesn't create a change log showing which profiles were re-enabled by an import override.

Do I need to re-import suppression data if I'm migrating from Mailchimp?

If you use Klaviyo's built-in Mailchimp integration, suppression data syncs automatically — contacts suppressed in Mailchimp are suppressed in Klaviyo, and the integration handles the mapping. For Campaign Monitor and Salesforce Marketing Cloud, the native integrations also handle suppression sync. For any platform not on Klaviyo's built-in integration list, the suppression import is fully manual via CSV upload, and you're responsible for exporting each suppression category from the old platform and importing it correctly.

Can I unsuppress contacts in Klaviyo after a migration?

Contacts suppressed for hard bounces or spam complaints cannot be unsuppressed. Those are deliverability-category suppressions and Klaviyo treats them as permanent — if a hard-bounced contact tries to resubscribe, the deliverability suppression remains and they still can't receive mail. Contacts manually suppressed — including those imported via the bulk suppression upload — can be unsuppressed by an administrator, but the contact must actively resubscribe to receive mail again. Reversing a manual suppression without re-consent is not the same as restoring email eligibility.

Should I suppress dormant contacts before migrating to Klaviyo?

For most DTC brands, yes — particularly during the warm-up period. Contacts who haven't opened, clicked, or purchased in 12 or more months will drag open rates below the 30-plus percent target Klaviyo recommends for first sends, which affects how inbox providers evaluate your new sending infrastructure. The decision depends on your business model: subscription brands and high-repeat-purchase categories should evaluate dormant contacts more carefully before suppressing. Single-purchase categories should suppress more aggressively and plan a separate re-engagement push on the old platform before migration.

What does global suppression mean in Klaviyo?

Global suppression means that when a contact unsubscribes from any email in your Klaviyo account — regardless of which list or campaign sent it — they become blocked from all marketing emails across the entire account. There's no list-specific opt-out behavior by default. This is different from many ESPs where unsubscribing from one list doesn't affect membership in others. Klaviyo allows list-level suppression to be configured on paid plans, but Klaviyo strongly recommends leaving global suppression enabled, and Sticky Digital does the same — the compliance and deliverability risk of list-level suppression is rarely worth the added complexity for DTC brands.

The Suppression List Is the Foundation

Every other part of a Klaviyo migration builds on the suppression list. Get it wrong — by importing in the wrong order, using the wrong import setting, or missing a category of contacts who should be suppressed — and the damage is compounded by every send that follows. Get it right, and you're starting warm-up from a clean foundation that gives inbox providers exactly the signal you want them to see.

If you're planning a Klaviyo migration and want a suppression audit before anything moves, we're easy to reach.

Article By: Mariel Kilroy, Co-Founder, Sticky Digital

Mariel Kilroy is the Co-Founder of Sticky Digital, a retention marketing agency specializing in email, SMS, loyalty, and subscription growth for DTC brands.