Execute Clay major re-architecture and migration strategies with strangler fig pattern.
Use when migrating to or from Clay, performing major version upgrades,
or re-platforming existing integrations to Clay.
Trigger with phrases like "migrate clay", "clay migration",
"switch to clay", "clay replatform", "clay upgrade major".
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
# 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:
// 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)
# 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)
// 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
