cloudflare-one-migrations

Plan migrations from Zscaler, Palo Alto, and legacy VPN platforms to Cloudflare One.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/narr07/permadi --skill cloudflare-one-migrations-narr07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloudflare-one-migrations
Source: https://github.com/narr07/permadi/tree/main/.agents/skills/cloudflare-one-migrations
Command: npx skills add https://github.com/narr07/permadi --skill cloudflare-one-migrations-narr07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating from existing VPN, SWG, or SASE platforms like Zscaler ZIA/ZPA or Palo Alto NGFW to Cloudflare One involves complex policy mapping, hidden parity gaps, and risky cutovers. This Skill structures the assessment and planning process so no source rule is silently dropped. ## Core Features & Use Cases - Source Stack Inventory: Catalogs identities, apps, tunnels, DNS/URL/firewall/DLP/TLS policies, objects, and hit counts from ZIA, ZPA, Palo Alto, and legacy VPN exports. - Policy Mapping Plan: Maps each source rule to Cloudflare One targets (Gateway traffic policies, Access apps, Cloudflare Tunnel, DLP profiles) with confidence levels, partial mappings, and explicit Not Migrated rows. - Safe Staged Rollout: Creates disabled/audit-mode rules with migration prefixes, pilot groups, log comparison, validation gates, and rollback paths. - Use Case: Given ZPA app segment and connector group exports, produce a tunnel-per-connector-group topology with CIDR/hostname routes, reusable Access policies, and the Gateway Network allow rule needed to avoid blocking private app traffic. ## Quick Start Assess my exported Zscaler ZIA and ZPA configuration files and produce a Cloudflare One migration plan with policy mappings and a pilot rollout.

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, then stage rules disabled with a migration prefix and pilot with small groups before expanding.

How to migrate ZPA app segments to Cloudflare Access?▼

Create one Cloudflare Tunnel per ZPA connector group with one cloudflared replica per connector instance. App segment IPs become CIDR routes and domains become hostname routes, while ZPA access policy rules map to reusable Cloudflare Access policies.

Does Cloudflare Access support enough hostnames for large ZPA app segments?▼

The default Access application limit is 5 hostnames per app. For large ZPA migrations, contact the Cloudflare account team to request an increase up to 50 before implementation, otherwise segments must be split into multiple apps with identical policies.

Why does Gateway block 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 selector at higher precedence than migrated block rules to fix this.

What are the limitations when mapping Palo Alto rules to Cloudflare One?▼

App-ID, URL categories, zones, HIP profiles, schedules, and decryption behavior rarely translate exactly. Mark these as partial mappings rather than forcing equivalence, and use Cloudflare device posture integrations to replace HIP checks.