Klaviyo to SMTP2GO Migration
Sending-platform escape for a restricted vertical, with the revenue flows rebuilt
Context
An e-commerce brand in a restricted product vertical was forced off Klaviyo, the platform's acceptable-use enforcement, not anything the brand did wrong technically. That is a existential email problem: the welcome and cart-recovery flows that drive repeat revenue go dark on someone else's timeline, and the obvious replacements enforce similar policies, so picking the next platform casually risks a second shutdown in ninety days.
The engagement rebuilt the sending operation on defensible ground: acceptable-use pre-clearance before any platform commitment, a clean authentication build on the SMTP2GO relay, and the two highest-revenue automations re-engineered from scratch, a nine-email welcome sequence fed by a coupon popup, and a four-email cart-abandonment sequence on a decay schedule, with every template hand-coded from Figma into email-client-safe responsive HTML.
The Challenge
- The vertical triggers automated and manual AUP enforcement on most consumer ESPs, platform selection had to be verified in writing, not assumed from a pricing page.
- The flows had to be rebuilt, not exported: automation logic does not transfer between Klaviyo and a relay-based stack.
- Design fidelity mattered, the brand had polished Figma designs that had to survive Outlook's rendering engine, not just Gmail's.
- Cart recovery needed purchase-aware cancellation: a buyer who completes checkout mid-sequence must exit instantly.
- A fresh sending setup meant reputation had to be built and measured from zero, with placement instrumented rather than presumed.
Scope and Approach
-
01
Vertical-aware platform selection
Ran acceptable-use verification against candidate ESPs before committing, the product category was submitted for written policy clearance rather than discovered-by-suspension later. SMTP2GO accepted the vertical explicitly; the rebuild happened once, on ground that will hold.
-
02
Sending architecture and authentication
Provisioned the relay end to end: dedicated sending domain, SPF include, DKIM signing keys, DMARC policy, verified aligned with real test sends before the first production message. The transactional and marketing streams were kept architecturally separable so future volume growth cannot drag order emails down with promotional reputation.
-
03
Welcome flow: nine emails plus capture
Built the lead-capture popup (AJAX submit, coupon issuance, thank-you state handled in-popup) feeding a nine-email welcome sequence, brand story, product education, social proof, discount escalation, each email triggered off list entry with timing tuned to the buying cycle.
-
04
Cart recovery on a decay schedule
Rebuilt cart abandonment as a four-email sequence at T+0h, 22h, 46h and 70h, immediate reminder, value restatement, objection handling, final urgency, with automatic cancellation the moment the order completes, driven by WooCommerce order state rather than link clicks.
-
05
Figma to email-safe HTML
Hand-coded every template into table-based responsive HTML: MSO conditional comments for Outlook, bulletproof buttons, explicit image dimensions, alt text throughout, and mobile breakpoints verified at real device widths. Pixel-accurate against the Figma source across Gmail, Outlook and Apple Mail, not just the preview pane.
-
06
Placement validation and instrumentation
Seed-tested the new setup across providers before launch, then instrumented the first production sends, the migration was measured by inbox placement and flow KPIs from day one, not declared done because messages left the server.
Architecture flow
Technical Deep Dive
Policy clearance as an engineering step
For restricted verticals, the ESP's acceptable-use policy is a hard dependency exactly like an API contract. The selection process treated it that way: product copy and category submitted to the platform, written confirmation received, limits understood (daily relay caps, review gates) before a single template was built. The alternative, build first, get suspended later, had already happened once on Klaviyo.
Why the templates are hand-coded tables
Outlook still renders email with Word's engine; flexbox and modern CSS silently collapse. The Figma designs survived because every layout is nested tables with MSO conditionals, fonts fall back gracefully, and spacing is explicit rather than inherited. Drag-and-drop builders approximate this; hand-coding guarantees it, and makes the diff reviewable when a template changes.
The decay schedule
The 0/22/46/70-hour offsets are deliberate: the first touch catches the still-browsing buyer, the sub-24h second touch lands inside the decision window while avoiding same-hour annoyance, and the later touches space out as intent decays. Purchase-aware cancellation makes the sequence safe to run aggressively, nobody who bought keeps getting recovery emails.
Early KPIs, honestly measured
First weeks live: the coupon popup captured 58 leads into the welcome flow, and the first 621 production sends registered zero spam complaints on the new infrastructure. Small numbers reported as small numbers, what matters at this stage is that the complaint rate is clean while reputation compounds.
Engineering Decisions
Relay + WooCommerce-native automation over another consumer ESP
Moving Klaviyo-to-Klaviyo-clone would have re-created the same policy exposure. Anchoring flows to WooCommerce events with SMTP2GO as the authenticated transport keeps the automation logic in infrastructure the brand controls and the policy surface minimal.
Nine welcome touches, front-loaded value
A long welcome arc converts better in considered-purchase niches, but only if the early emails give before they ask, the sequence leads with education and proof, holds the hard discount for later, and every email can be dropped or reordered without breaking the flow.
Measure placement from send one
Fresh domain, fresh relay, restricted vertical, the setup earns trust sequentially. Instrumenting bounces, complaints and placement from the first send means any reputation problem surfaces at send 600, not send 60,000.
Results
- A clean exit from Klaviyo onto a relay pre-cleared in writing for the vertical, no second ban cycle.
- Nine-email welcome and four-email cart-recovery flows live on purchase-aware triggers.
- The coupon popup captured 58 leads in its first weeks live.
- Zero spam complaints across the first 621 sends on the new authentication build.
- Figma-accurate, MSO-safe responsive templates rendering correctly across Gmail, Outlook and Apple Mail.
- A documented handover covering the sending architecture, flow logic and what to watch as volume grows.
Have a system that needs
this kind of work?
Tell me what is breaking or what you need built. I will reply with how I would approach it and what I would check first.