Agent skill

Clay Migration Deep Dive

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay.

MITAuto-check passedBackend & APIs

Install Clay Migration Deep Dive

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-migration-deep-dive -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-migration-deep-dive --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/clay-migration-deep-dive .claude/skills/clay-migration-deep-dive && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clay-migration-deep-dive
GitHub stars
2.8k
Token cost
~2.2k tokens
SKILL.md length
379 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay.

  • Works in 6 steps: Audit Current Enrichment Stack (Week 1) → Map Fields to Clay Columns (Week 1) → Parallel Run (Week 2-3) → …
  • Migrating from ZoomInfo
  • SKILL.md covers Overview, Prerequisites, Migration Types and Instructions, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clay Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay. Use when migrating from ZoomInfo, Apollo, Clearbit, or custom enrichment scripts to Clay, or consolidating fragmented enrichment workflows. Trigger with phrases like "migrate to clay", "clay migration", "switch to clay", "replace zoominfo with clay", "consolidate enrichment tools".

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Backend & APIs, covering GraphQL. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Migrating from ZoomInfo
  • Custom enrichment scripts to Clay
  • Consolidating fragmented enrichment workflows
  • With phrases like migrate to clay

Example prompts

  • “migrate to clay”
  • “clay migration”
  • “switch to clay”
  • “/clay-migration-deep-dive”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*), Bash(npm:*), Bash(node:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Audit Current Enrichment Stack (Week 1)
  2. Map Fields to Clay Columns (Week 1)
  3. Parallel Run (Week 2-3)
  4. Configure Clay Table to Replace Current Stack (Week 3)
  5. Gradual Traffic Migration (Week 4)
  6. Cancel Legacy Subscriptions

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)
    • Bash(npm:*)
    • Bash(node:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • university.clay.com
    • clay.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Clay Migration Deep Dive loads about 2.2k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 379 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 379 words, ~2,170 tokens.

Download SKILL.mdSave it as .claude/skills/clay-migration-deep-dive/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
clay-migration-deep-dive
description
Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay. Use when migrating from ZoomInfo, Apollo, Clearbit, or custom enrichment scripts to Clay, or consolidating fragmented enrichment workflows. Trigger with phrases like "migrate to clay", "clay migration", "switch to clay", "replace zoominfo with clay", "consolidate enrichment tools".
allowed-tools
Read, Write, Edit, Bash(curl:*), Bash(npm:*), Bash(node:*)
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, clay, migration

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

MigrationComplexityDurationRisk
Single provider -> ClayLow1-2 weeksLow
Multiple providers -> ClayMedium2-4 weeksMedium
Custom scripts -> ClayMedium2-4 weeksMedium
Full GTM stack migrationHigh1-2 monthsHigh

Instructions

Step 1: Audit Current Enrichment Stack (Week 1)
typescript
// migration/audit.ts — document your current enrichment setup
interface EnrichmentAudit {
  provider: string;
  monthlyVolume: number;
  monthlyCoost: number;
  dataFields: string[];
  hitRate: number;           // % of lookups that return data
  integrationMethod: string; // API, CSV, Zapier, native CRM
  canExportHistory: boolean;
}

const currentStack: EnrichmentAudit[] = [
  {
    provider: 'ZoomInfo',
    monthlyVolume: 5000,
    monthlyCoost: 15000,  // ZoomInfo is expensive
    dataFields: ['email', 'phone', 'title', 'company', 'revenue'],
    hitRate: 75,
    integrationMethod: 'API + Salesforce native',
    canExportHistory: true,
  },
  {
    provider: 'Apollo.io',
    monthlyVolume: 3000,
    monthlyCoost: 400,
    dataFields: ['email', 'title', 'company', 'linkedin'],
    hitRate: 65,
    integrationMethod: 'API',
    canExportHistory: true,
  },
  {
    provider: 'Custom Python scripts',
    monthlyVolume: 1000,
    monthlyCoost: 0,  // Just developer time
    dataFields: ['email', 'company_data'],
    hitRate: 40,
    integrationMethod: 'Cron job + DB',
    canExportHistory: true,
  },
];

function generateMigrationReport(stack: EnrichmentAudit[]): void {
  const totalCost = stack.reduce((s, p) => s + p.monthlyCoost, 0);
  const totalVolume = stack.reduce((s, p) => s + p.monthlyVolume, 0);
  console.log(`Current stack: ${stack.length} providers`);
  console.log(`Total monthly cost: $${totalCost}`);
  console.log(`Total monthly volume: ${totalVolume} lookups`);
  console.log(`Average hit rate: ${(stack.reduce((s, p) => s + p.hitRate, 0) / stack.length).toFixed(0)}%`);
  console.log(`\nClay equivalent (Growth plan): $495/mo + provider API keys`);
}
Step 2: Map Fields to Clay Columns (Week 1)
yaml
# migration/field-mapping.yaml
field_mapping:
  # Your current field -> Clay enrichment column
  email: "Work Email (Waterfall: Apollo > Hunter)"
  phone: "Phone Number (Apollo)"
  job_title: "Job Title (Apollo/PDL)"
  company_name: "Company Name (Clearbit)"
  company_revenue: "Revenue (Clearbit)"
  employee_count: "Employee Count (Clearbit)"
  industry: "Industry (Clearbit)"
  tech_stack: "Technologies (BuiltWith via Claygent)"
  linkedin: "LinkedIn URL (Apollo)"

  # Fields that don't have direct Clay equivalents:
  intent_signals: "Use Clay's Web Intent feature (Growth plan)"
  custom_research: "Claygent AI research column"
Step 3: Parallel Run (Week 2-3)

Run Clay alongside your existing tools to validate data quality:

typescript
// migration/parallel-run.ts
interface ComparisonResult {
  field: string;
  oldValue: string | null;
  clayValue: string | null;
  match: boolean;
}

async function compareEnrichment(
  email: string,
  oldData: Record<string, unknown>,
  clayData: Record<string, unknown>,
): Promise<ComparisonResult[]> {
  const fieldsToCompare = ['company_name', 'job_title', 'employee_count', 'industry'];

  return fieldsToCompare.map(field => ({
    field,
    oldValue: (oldData[field] as string) || null,
    clayValue: (clayData[field] as string) || null,
    match: String(oldData[field]).toLowerCase() === String(clayData[field]).toLowerCase(),
  }));
}

// Run on a sample of 500 contacts from your CRM
// Compare Clay's enrichment with your current provider's data
// Target: Clay should match or exceed current hit rates
Step 4: Configure Clay Table to Replace Current Stack (Week 3)
yaml
# Clay table configuration to replace multi-provider stack
replacement_table:
  name: "Outbound Leads (Migrated)"
  sources:
    - webhook (replaces API calls to ZoomInfo/Apollo)
    - CRM import (replaces native CRM enrichment)
    - CSV upload (replaces manual processes)

  enrichment_columns:
    1_company_lookup:
      provider: clearbit
      replaces: "ZoomInfo company data"
      own_api_key: true  # 0 Clay credits

    2_email_waterfall:
      providers: [apollo, hunter]
      replaces: "ZoomInfo email + Apollo email"
      own_api_keys: true

    3_person_enrichment:
      provider: apollo
      replaces: "Apollo person data"
      own_api_key: true

    4_ai_research:
      type: claygent
      replaces: "Custom Python research scripts"
      prompt: "Research {{Company Name}} for recent news and tech stack"

    5_icp_scoring:
      type: formula
      replaces: "Custom scoring in Python/SQL"
Step 5: Gradual Traffic Migration (Week 4)
typescript
// migration/traffic-shift.ts
interface MigrationConfig {
  clayPercentage: number;   // 0-100, gradually increase
  legacyEnabled: boolean;
}

class MigrationRouter {
  constructor(private config: MigrationConfig) {}

  shouldUseClay(): boolean {
    return Math.random() * 100 < this.config.clayPercentage;
  }

  async enrichLead(lead: Record<string, unknown>): Promise<Record<string, unknown>> {
    if (this.shouldUseClay()) {
      return this.enrichViaClay(lead);
    }
    return this.enrichViaLegacy(lead);
  }
}

// Migration schedule:
// Week 4, Day 1: 10% to Clay, 90% legacy
// Week 4, Day 3: 25% to Clay, 75% legacy
// Week 4, Day 5: 50% to Clay, 50% legacy
// Week 5, Day 1: 100% to Clay, legacy disabled
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
Show full SKILL.md (172 more words)Show less

Error Handling

IssueCauseSolution
Lower hit rate on ClayDifferent provider coverageAdjust waterfall order, add providers
Missing fieldsClay uses different field namesUpdate field mapping
Data format mismatchDifferent date/number formatsAdd transformation in webhook handler
CRM duplicates during parallelBoth systems writingDeduplicate on email in CRM

Output

Create a migration receipt with source/target systems, data and consent mapping, field transformations, traffic percentage, comparison metrics, deduplication strategy, owners, approval points, rollback status, and legacy-retirement decision. Do not cancel the old path or delete its evidence until the defined monitoring window proves that the new path satisfies the approved contract.

Examples

Shift a staging-compatible source from 10 to 25 percent only after comparing coverage, quality, credit use, and CRM idempotency for the prior cohort. If a field mapping or duplicate error appears, return traffic to the last stable percentage, reconcile the affected records, and correct the transform before advancing the rollout.

Resources

Next Steps

For advanced troubleshooting, see clay-advanced-troubleshooting.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/clay-migration-deep-dive of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Clay Migration Deep Dive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clay Migration Deep Dive compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clay Migration Deep Dive this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.2kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT
GraphQL Operations with CodegenChrisWiles/claude-code-showcase6.1k3 repos~1.5kAutomated safety check: PassNone
Supabasecurvenote/curvenote1705 repos~2.2kAutomated safety check: PassCustom licence
API Design Principlesjh941213/my-cc-harness12518 repos~3.4kAutomated safety check: PassNone

Similar skills

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed
  • GraphQL Operations with Codegen

    ChrisWiles/claude-code-showcase

    Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.

    6.1k GitHub starsUsed in 3 repos~1.5k tokens
    Backend & APIsAuto-check passed
  • Supabase

    curvenote/curvenote

    A skill your agent uses when doing ANY task involving Supabase.

    170 GitHub starsUsed in 5 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • API Design Principles

    jh941213/my-cc-harness

    REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.

    125 GitHub starsUsed in 18 repos~3.4k tokens
    Backend & APIsAuto-check passed
  • API And Interface Design

    dzhalaevd/Donatello

    Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 8 repos~2.6k tokens
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Clay Migration Deep Dive

What does Clay Migration Deep Dive do?

Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay. Clay Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay.

When should I use Clay Migration Deep Dive?

Clay Migration Deep Dive fits situations like: migrating from ZoomInfo; custom enrichment scripts to Clay; consolidating fragmented enrichment workflows; with phrases like migrate to clay.

How do I install Clay Migration Deep Dive in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-migration-deep-dive -a claude-code`. Or copy the skill folder (skills/.curated/clay-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clay-migration-deep-dive in your project. Claude Code loads it when a task matches its description.

How do I install Clay Migration Deep Dive in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-migration-deep-dive -a codex`. Or copy the skill folder (skills/.curated/clay-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clay-migration-deep-dive in your project. Codex loads it when a task matches its description.

Can I use Clay Migration Deep Dive in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-migration-deep-dive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clay-migration-deep-dive, .gemini/skills/clay-migration-deep-dive, .github/skills/clay-migration-deep-dive and .opencode/skills/clay-migration-deep-dive in your project.

What does Clay Migration Deep Dive need to run?

SKILL.md names no scripts, command-line tools or credentials: Clay Migration Deep Dive is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*), Bash(npm:*), Bash(node:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Clay Migration Deep Dive access the network?

SKILL.md names 2 domains. As links in the text: university.clay.com and clay.com. This is read from the text; nothing was executed.

Is Clay Migration Deep Dive safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clay Migration Deep Dive use?

Clay Migration Deep Dive is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clay Migration Deep Dive use?

About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 845 tokens, read only when the agent opens those files.

What are the alternatives to Clay Migration Deep Dive?

Skills that share tags, products or a category with Clay Migration Deep Dive: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), API Designer (Jeffallan/claude-skills, 12k stars), GraphQL Operations with Codegen (ChrisWiles/claude-code-showcase, 6.1k stars) and Supabase (curvenote/curvenote, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clay Migration Deep Dive?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.