Agent skill · product strategy · jeremylongshore
lindy-migration-deep-dive
Advanced migration strategies for moving to Lindy AI from other platforms.
Why this skill is useful
Provides detailed migration strategies and patterns for transitioning to Lindy AI from various automation platforms that the AI wouldn't generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Migration Deep Dive Overview Migrate existing automation workflows from Zapier, Make (Integromat), n8n, LangChain, or custom code to Lindy AI. Key insight: Lindy replaces rigid rule-based automations with AI agents that can reason, adapt, and handle ambiguity — so migration is a redesign opportunity, not a 1:1 translation. Prerequisites Inventory of existing automations (source platform) Lindy workspace ready with required integrations authorized Migration timeline approved Rollback plan defined for customer-facing workflows Migration Source Comparison Source Platform Lindy Equivalent Key Difference ---------------- ----------------- ---------------- Zapier Zap Lindy Agent AI reasoning replaces rigid if/then Make Scenario Lindy Agent No-code builder instead of module chains n8n Workflow Lindy Agent Managed infra, no self-hosting LangChain Agent Lindy Agent Step No-code, managed, no Python needed Custom code HTTP Request + Run Code Less code, AI fills gaps Instructions Step 1: Inventory Source Automations For each existing automation, document: Field Example ------- --------- Name Support Email Triage Trigger New email in support@co.com Steps 1. Parse email 2. Classify 3. Route to channel Integrations Gmail, Slack, Sheets Frequency ~50 runs/day Complexity Medium (3 steps, 1 condition) Step 2: Classify Migration Complexity Complexity Criteria Migration Approach Time ----------- --------- ------------------- ------ Simple 1-3 steps, no conditions Build from scratch in Lindy 30 min Medium 4-8 steps, conditions Natural language description to Agent Builder 1-2 hours Complex 9+ steps, multi-branch, loops Redesign as multi-agent society 1-2 days Custom code Python/JS logic Run Code action + HTTP Request 2-4 hours Step 3: Migration Strategy by Source From Zapier: From Make (Integromat): From n8n: From LangChain/Custom Code: Step 4: Execute Migration (Phased) Phase 1: Internal-Only Agents (Days 1-3) 1. Migrate non-customer-facing automations first 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-migration-deep-dive