Cloudflare Workers Migration

This walks you through porting Lambda functions, Express apps, Vercel routes, and Node.js code to Cloudflare Workers. It includes a decision tree for choosing migration strategies, a comparison table showing Workers' near-zero cold starts versus Lambda's 100-500ms, and the top 10 errors you'll hit (fs is not defined, Buffer missing, process.env undefined). The before/after code examples are straight to the point, especially for Lambda handlers and Express middleware. Most helpful is the Node.js compatibility matrix showing what works with nodejs_compat_v2 and what needs alternatives like swapping fs for R2 storage. If you're moving edge-ward and hitting compatibility walls, this is a solid reference to keep nearby.

skills.sh installs: 310
GitHub stars: 248
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add secondsky/claude-skills --skill cloudflare-workers-migration --agent claude-code

Installs into .claude/skills of the current project.

Files

Workers Migration Guide

Migrate existing applications to Cloudflare Workers from various platforms.

Migration Decision Tree

What are you migrating from?
├── AWS Lambda
│   └── Node.js handler? → Lambda adapter pattern
│   └── Python? → Consider Python Workers
│   └── Container/custom runtime? → May need rewrite
├── Vercel/Next.js
│   └── API routes? → Minimal changes with adapter
│   └── Full Next.js app? → Use OpenNext adapter
│   └── Middleware? → Direct Workers equivalent
├── Express/Node.js
│   └── Simple API? → Hono (similar API)
│   └── Complex middleware? → Gradual migration
│   └── Heavy node: usage? → Compatibility layer
└── Other Edge (Deno Deploy, Fastly)
    └── Standard Web APIs? → Minimal changes
    └── Platform-specific? → Targeted rewrites