Gurugram insurtech, 80 staff, AWS, Postgres, Freshdesk, Zapier on a high-tier plan, partner insurers asking about data residency
Week 1Inventory and triageExport all Zaps; rank by volume and data sensitivity; mark keep or migrate25 high-volume or sensitive flows chosen for n8n
Weeks 2–3Platform buildn8n in Docker on AWS Mumbai, EXECUTIONS_MODE=queue with Redis workers, Postgres, N8N_ENCRYPTION_KEY held outside the container, backupsStaging and production instances with monitoring
Weeks 3–6Migrate and testRebuild flows in n8n and parallel-run them against the Zaps for a week, comparing outputs in Zap History and the n8n Executions listEach flow cut over once outputs match
Weeks 6–7Harden and hand overError workflows, workflow JSON in Git, upgrade policy, runbookClient DevOps owns patching and upgrades
Where it starts60 Zaps, about 150,000 tasks/month, Zapier bill rising each quarter, no version control, two failures last month found by customers
Where it endsThe insurtech runs its sensitive flows on its own n8n. Weekly they watch failed executions, queue backlog and platform cost against the old Zapier bill.