Agent skill · marketing growth · jeremylongshore
clay-migration-deep-dive
Migrate to Clay from other enrichment tools or consolidate multiple
Why this skill is useful
Provides specific migration workflows and field mappings for consolidating enrichment tools into Clay that the AI wouldn't reliably generate on its own.
What it needs
Requires clay account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay Migration Deep Dive Overview Comprehensive guide for migrating from standalone enrichment tools (ZoomInfo, Apollo, Clearbit, Lusha) to Clay, or consolidating multiple tools into a single Clay-based pipeline. Clay replaces the need for individual provider subscriptions by aggregating 150+ providers into waterfall enrichment workflows. Prerequisites Current enrichment tool subscription(s) with data export capability Clay account on Growth or Enterprise plan Understanding of current enrichment volume and costs CRM with existing enriched data Migration Types Migration Complexity Duration Risk ----------- ----------- ---------- ------ Single provider -> Clay Low 1-2 weeks Low Multiple providers -> Clay Medium 2-4 weeks Medium Custom scripts -> Clay Medium 2-4 weeks Medium Full GTM stack migration High 1-2 months High Instructions Step 1: Audit Current Enrichment Stack (Week 1) Step 2: Map Fields to Clay Columns (Week 1) Step 3: Parallel Run (Week 2-3) Run Clay alongside your existing tools to validate data quality: Step 4: Configure Clay Table to Replace Current Stack (Week 3) Step 5: Gradual Traffic Migration (Week 4) Step 6: Cancel Legacy Subscriptions After full migration and 2-week monitoring: [ ] Verify Clay hit rates match or exceed legacy providers [ ] Confirm CRM sync working correctly [ ] Export final data from legacy tools as backup [ ] Cancel ZoomInfo/Apollo/Clearbit subscriptions [ ] Remove legacy API keys from application code [ ] Document Clay configuration for team Error Handling Issue Cause Solution ------- ------- ---------- Lower hit rate on Clay Different provider coverage Adjust waterfall order, add providers Missing fields Clay uses different field names Update field mapping Data format mismatch Different date/number formats Add transformation in webhook handler CRM duplicates during parallel Both systems writing Deduplicate on email in CRM Output Create a migration receipt with source/target systems, data and consent mapping, field transformati …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-migration-deep-dive--63a886