klaviyo-migration-deep-dive

Featured

Execute major Klaviyo migration strategies: from legacy v1/v2 APIs, from competitors, or full re-platforming to Klaviyo with the strangler fig pattern. Trigger with phrases like "migrate to klaviyo", "klaviyo migration", "switch to klaviyo", "klaviyo replatform", "mailchimp to klaviyo", "legacy to klaviyo", "v1 to v2 klaviyo".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Klaviyo Migration Deep Dive ## Overview Comprehensive guide for migrating to Klaviyo from legacy APIs (v1/v2), competing ESPs (Mailchimp, SendGrid, etc.), or re-platforming with the strangler fig pattern. Covers data migration, API mapping, and validation. ## Prerequisites - Target Klaviyo account configured - `klaviyo-api` SDK installed - Source system access for data export - Feature flag infrastructure (for gradual rollout) ## Migration Types | Migration | Complexity | Duration | Risk | |-----------|-----------|----------|------| | Klaviyo v1/v2 to current API | Low-Medium | 1-2 weeks | Low | | Mailchimp/SendGrid to Klaviyo | Medium | 2-4 weeks | Medium | | Custom ESP to Klaviyo | High | 4-8 weeks | High | | Full re-platform | High | 2-3 months | High | ## Instructions ### Step 1: Legacy v1/v2 to Current API The most common migration. Klaviyo deprecated v1/v2 endpoints in favor of the JSON:API REST API. ```typescript // ============================================================ // BEFORE: Legacy v1/v2 endpoints (DEPRECATED, will stop working) // ============================================================ // v1 Track (event tracking) // POST https://a.klaviyo.com/api/track // Body: { token: "PUBLIC_KEY", event: "Placed Order", ... } // v2 List Subscribe // POST https://a.klaviyo.com/api/v2/list/LIST_ID/subscribe // Headers: { api-key: "pk_***" } // v1 Identify (profile creation) // POST https://a.klaviyo.com/api/identify // Body: { token: "PUBLIC_KEY", pro...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

klaviyo-upgrade-migration

Upgrade Klaviyo SDK versions and migrate between API revisions. Use when upgrading the klaviyo-api package, migrating from v1/v2 legacy APIs to the current REST API, or handling breaking changes between revisions. Trigger with phrases like "upgrade klaviyo", "klaviyo migration", "klaviyo breaking changes", "update klaviyo SDK", "klaviyo API revision".

2,266 Updated today
jeremylongshore
AI & Automation Featured

instantly-migration-deep-dive

Execute complex Instantly.ai migration strategies for platform changes. Use when migrating between cold email platforms, consolidating workspaces, or re-architecting outreach infrastructure around Instantly. Trigger with phrases like "migrate to instantly", "instantly migration", "switch to instantly", "instantly platform migration", "outreach migration".

2,266 Updated today
jeremylongshore
AI & Automation Featured

shopify-migration-deep-dive

Migrate e-commerce data to Shopify using bulk operations, product imports, and the strangler fig pattern for gradual platform migration. Trigger with phrases like "migrate to shopify", "shopify data migration", "import products shopify", "shopify replatform", "move to shopify".

2,266 Updated today
jeremylongshore
AI & Automation Featured

apollo-migration-deep-dive

Comprehensive Apollo.io migration strategies. Use when migrating from other CRMs to Apollo, consolidating data sources, or executing large-scale data migrations. Trigger with phrases like "apollo migration", "migrate to apollo", "apollo data import", "crm to apollo", "apollo migration strategy".

2,266 Updated today
jeremylongshore
AI & Automation Solid

vercel-migration-deep-dive

Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".

2,266 Updated today
jeremylongshore