Migration
Plan incremental migrations to Cloudflare from AWS, Azure, GCP, server-based apps, or existing databases using strangler patterns, service boundaries, R2 offload, Workers frontdoors, Hyperdrive, queues, workflows, shadow reads, rollback, and observability.
Install
npx skills add zllovesuki/cloudflare-agent-skills --skill migrationgit clone --depth 1 https://github.com/zllovesuki/cloudflare-agent-skills.git /tmp/cloudflare-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/cloudflare-agent-skills/skills/migration ~/.claude/skills/migrationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Migration Use this skill when moving an existing application or subsystem to Cloudflare. ## Migration stance - Migrate incrementally and reversibly. - Establish baselines before moving traffic. - Do not rewrite everything just to match Cloudflare primitives. - Use Workers as a frontdoor/strangler when it reduces risk. - Keep the old system and new system observable during coexistence. ## Baseline first Capture before migration: - Request volume and routes. - Latency percentiles. - Error rates. - CPU/memory and database load. - Storage/egress costs. - Top user flows. - Operational pain points. ## Migration patterns ### Worker frontdoor ```text Client -> Worker -> route migrated paths to Cloudflare-native code -> proxy unmigrated paths to existing origin ``` Use for gradual route-level migration, auth normalization, caching, and observability. ### R2 offload ```text Existing app metadata remains in old DB Worker handles upload/download R2 stores blobs Existing app receives R2 object keys ``` Good first migration when egress/blob cost is high. ### Hyperdrive coexistence ```text Worker -> Hyperdrive -> existing Postgres/MySQL ``` Use when business data must stay in the existing database while edge routes move first. ### Async extraction ```text Existing synchronous operation -> Worker validates request -> Queue/Workflow performs background steps -> D1/R2 stores job status/result ``` Use for exports, imports, notifications, AI pipelines.
Details
- Skill name
migration- Repository
- zllovesuki/cloudflare-agent-skills
- Path
skills/migration/SKILL.md- Repo updated
- 28 April 2026
FAQ
What does the Migration skill do?
Plan incremental migrations to Cloudflare from AWS, Azure, GCP, server-based apps, or existing databases using strangler patterns, service boundaries, R2 offload, Workers frontdoors, Hyperdrive, queues, workflows, shadow reads, rollback, and observability.
How do I install the Migration skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add zllovesuki/cloudflare-agent-skills --skill migration. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Migration popular?
It lives in zllovesuki/cloudflare-agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Agents
9zllovesuki/cloudflare-agent-skills
Build Cloudflare Agents SDK applications for autonomous multi-step tool use, AIChatAgent chat agents, Durable Object-backed state, tools, scheduling, callable methods, WebSockets, SQL state, and constrained agent behavior. Use when RAG or Workflows are not enough.
Cloudflare Architecture
9zllovesuki/cloudflare-agent-skills
Choose Cloudflare Developer Platform primitives and architecture shapes before writing code. Use for Cloudflare Workers, Durable Objects, D1, R2, Queues, Workflows, Containers, Realtime, Workers AI, Vectorize, AI Search, Agents, cost, limits, and migration decisions.
Containers
9zllovesuki/cloudflare-agent-skills
Decide when to use Cloudflare Containers instead of Workers and design container-backed workloads, native binaries, long-running processes, image processing, larger runtime shapes, and Worker frontends. Use as an escape hatch when Workers constraints do not fit.
Observability
9zllovesuki/cloudflare-agent-skills
Add production observability to Cloudflare Workers apps with structured logs, request IDs, metrics, traces, Durable Object/Queue/Workflow visibility, error handling, and incident debugging. Use before deploying or debugging Cloudflare applications.
Full Stack Apps
9zllovesuki/cloudflare-agent-skills
Build full-stack Cloudflare apps with Workers, static assets, SSR, API routes, SPA/hybrid rendering, cache headers, and binding-backed data. Use when implementing frontend-plus-backend applications on Cloudflare Workers.
Platform Limits
9zllovesuki/cloudflare-agent-skills
Check Cloudflare Developer Platform hard limits and runtime constraints before implementation: Worker memory/CPU/body/protocol constraints, D1 size/query limits, Durable Object hotspots, KV consistency, Queue message size/order, R2 object flows, and product availability. Use to prevent invalid designs.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.