Klaviyo migration. No deliverability loss.

No — risk managed end-to-end via staged migration, IP warming, DMARC + BIMI + DKIM validation, and engagement-segmentation cleanup before any high-volume sends move. Standard protocol: flows migrate first (low volume, transactional + behavioural), then campaign sends (high volume, marketing) over 2–4 weeks. Engagement-segmented warming sends through the warmest 20% of your list first, expanding daily. Inbox Placement Rate monitored daily during cutover via Validity, Postmaster Tools, and Sender Score. Clients see 0–3% short-term IPR variance on average.

Yes — full subscriber list, engagement history, segments, and custom properties migrate. Source ESPs vary in what they expose: Mailchimp transfers cleanly (everything except Klaviyo-style RFM segments which we rebuild), HubSpot Marketing exports rich engagement data, Drip and ActiveCampaign transfer well with custom-field mapping, generic CRM email loses some metadata. Custom properties mapped manually in week 1; we document gaps before migration so you know exactly what is preserved vs reconstructed. Subscriber-consent state preserved per platform.

2–4 weeks for established lists above 10,000 subscribers, with engagement-segmented warming starting at the highly-engaged 20% on day 1 and expanding to the broader list over the warming period. Shorter for smaller lists (1–2 weeks below 10k subs). Brand-new IP needs longer (3–5 weeks). We schedule warming based on your list size, send frequency, and current sender reputation; aggressive warming compromises long-term inbox placement. Daily warming progress reported in shared Notion + weekly Loom updates.

Functionally yes, often better — Klaviyo's eCom-native filters (RFM, predictive CLV, replenishment cycle, browse abandonment with Shopify/BigCommerce/Magento integration depth) are richer than most source ESPs. Some source-ESP-specific filters do not have direct Klaviyo equivalents and need re-engineering (mostly in HubSpot lifecycle stages and Marketo programs). We document filter-by-filter differences before cutover, so nothing is a surprise. Most flows perform 10–30% better in Klaviyo for B2C eCom because of native Shopify event integration.

Yes — SMS migration is in scope: Klaviyo SMS (paired with Klaviyo email for unified attribution and audience), Postscript (DTC eCom favourite, deeper Shopify integration), Attentive (high-volume DTC), Twilio (custom B2B and developer-led setups), or migration to Klaviyo SMS from any of the above. TCPA-compliant in the US, GDPR + PECR-compliant in EU/UK, DPDP-compliant in India — express opt-in architecture, designated sender registration, functional unsubscribe preserved across migration. SMS subscriber consent state migrates separately from email consent.

Klaviyo pricing scales with your active profile count and SMS messages sent — not subscriber count alone. We recommend the right plan based on: total active profiles in the past 12 months, monthly email send volume, SMS send volume (separate add-on), required integrations (Shopify, BigCommerce, Recharge, Loop, Yotpo, etc.), and team-seat needs. Most DTC migration clients land on Klaviyo's standard tier sized to their active-profile range, with SMS as a usage add-on. We share pricing comparison vs source-ESP cost in week 1.