| name | lindy-upgrade-migration |
| description | Manage Lindy agent configuration changes, platform updates, and migrations.
Use when reconfiguring agents, handling platform changes,
or migrating agents between workspaces.
Trigger with phrases like "upgrade lindy", "lindy migration",
"lindy reconfigure", "update lindy agents", "lindy workspace migration".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.15.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","lindy","migration"] |
| compatibility | Designed for Claude Code |
Lindy Upgrade & Migration
Overview
Lindy is a managed platform — agents run on Lindy's infrastructure. "Upgrades"
mean reconfiguring agents for new capabilities, migrating agents between workspaces,
or adapting to platform changes. Key concern: agents with webhooks, Lindymail,
and phone numbers require reconfiguration after migration.
Prerequisites
- Admin access to source and target Lindy workspaces
- Inventory of all agents, triggers, and integrations
- Migration window scheduled for customer-facing agents
Instructions
Step 1: Inventory Current Agents
Document every agent before making changes:
| Agent Name | Trigger Type | Actions | Integrations | Webhook URL | Phone # |
|---|
| Support Bot | Email Received | Gmail Reply, Slack Notify | Gmail, Slack | N/A | N/A |
| Lead Router | Webhook | Sheets Update, Slack DM | Sheets, Slack | https://public.lindy.ai/... | N/A |
| Phone Screener | Call Received | Transfer, Agent Send | Phone | N/A | +1-555-0100 |
Step 2: Export Agent Configurations
For each agent, document:
- Prompt: Copy full text from Settings > Prompt
- Model: Which AI model is selected
- Skills/Actions: List all action steps and their configurations
- Trigger filters: Copy filter conditions
- Knowledge Base: Note all sources (files, URLs, integrations)
- Memories: Export any persistent memories
- Exit conditions: Copy all condition text
Step 3: Plan Migration Order
Phase 1: Internal-only agents (no customer impact)
→ Migrate, test, verify for 24-48 hours
Phase 2: Low-risk customer-facing agents (email triage, notifications)
→ Migrate during low-traffic window
→ Monitor for 24 hours
Phase 3: Critical agents (phone, live chat, lead routing)
→ Migrate with rollback plan ready
→ Keep old agent active in parallel for 48 hours
Step 4: Migrate Agent to New Workspace
Option A — Template sharing:
