cloudflare-one-migrations

Plans migrations from Zscaler, Palo Alto, and legacy VPN stacks to Cloudflare One.

13|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/vedang/dotagents --skill cloudflare-one-migrations-vedang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudflare-one-migrations
Source: https://github.com/vedang/dotagents/tree/main/specific_skills/cloudflare-one-migrations
Command: npx skills add https://github.com/vedang/dotagents --skill cloudflare-one-migrations-vedang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating from Zscaler ZIA/ZPA, Palo Alto NGFW/Prisma, or legacy VPN/SWG stacks to Cloudflare One involves hundreds of interdependent policies, objects, and connectors where missed mappings cause silent security gaps or broken connectivity. This Skill provides a structured workflow to inventory source configurations, map them to Cloudflare One resources, and stage a safe rollout. ## Core Features & Use Cases - Source Stack Inventory: Defines exactly which exports to request from ZIA, ZPA, and Palo Alto/Prisma, including policies, objects, connectors, hit counts, and identity data. - Mapping Heuristics: Maps source constructs to Cloudflare One targets such as Gateway traffic policies, Access applications, Cloudflare Tunnels, Split Tunnels, and DLP profiles, with explicit partial/unsupported flags. - Source-Specific Traps: Documents known pitfalls like ZPA connector-group-to-tunnel topology, Access app hostname limits, ZIA caution/warn behavior, and Gateway Network rules blocking private app traffic. - Use Case: A network engineer receives ZPA exports with 40 app segments and 12 connector groups. The Skill guides creating one Cloudflare Tunnel per connector group, converting app segment IPs to CIDR routes, building reusable Access policies, and adding the Gateway Network allow rule before enabling L4 blocks. ## Quick Start Ask the agent to assess a migration from Zscaler ZPA to Cloudflare One using your exported app segments, connector groups, and access policies.

Frequently Asked Questions about cloudflare-one-migrations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from Zscaler ZIA to Cloudflare Gateway?

Export ZIA URL filtering, firewall, SSL inspection, DLP, custom categories, and location data first. Map these to Cloudflare Gateway traffic policies and lists, create identity/SCIM dependencies first, and stage rules in audit mode before pilot rollout.

How do I migrate ZPA app segments to Cloudflare Access?

Create one Cloudflare Tunnel per ZPA connector group, convert app segment IPs to CIDR routes and domains to hostname routes, then build reusable Access policies before attaching them to apps. Note the default 5-hostname limit per Access app may require an account team increase.

Can Palo Alto firewall rules map directly to Cloudflare One?

One Palo Alto rule often produces multiple Cloudflare resources, and App-ID, zones, HIP, and decryption behavior rarely translate exactly. Preserve rule intent rather than rule count, and mark partial mappings instead of forcing false equivalence.

Why does Gateway block my Access private app traffic after migration?

In default-deny Gateway Network environments, broad L4 block rules evaluate before Access policies. Add a Network allow rule with the "Self-hosted Access App with Private Address is Present" selector at higher precedence than the block rules.

What are the limitations of Zscaler to Cloudflare migration?

ZIA caution/warn behavior, DLP engines with custom regex, and some network application groups have no exact Cloudflare equivalent. These must be flagged as explicit customer decisions or manual recreations rather than silently mapped.