Back to catalog / Integrations
Cloudflare One migration: map policies and preserve gaps
Use structured source exports to inventory dependencies and stage identity, connectors, rules, and logging.
Skills
Identify the source platform/version and request structured exports of rules, objects, groups, locations, hit counts, exceptions, and logs. Order dependencies such as identity/SCIM, tunnels/connectors, DNS/routes, lists, Access, Gateway, and DLP/CASB. Map every source object to a Cloudflare target with confidence, prerequisites, partial/unsupported gaps, or a Not Migrated reason and security impact. Use current vendor docs; prefix rules and default them to disabled/audit, pilot small groups/sites, compare logs, then expand. Preserve source config unless separately authorized to retire it.
Permissions
Prerequisites
- Assess migration from Zscaler, Palo Alto, VPN/SWG/SASE to Cloudflare One, mapping policy gaps and rollout.
Permissions
- May read security policy, identity, and logs and write migration configs/rules.
Limitations
Do not flatten rules into lists. Account for every rule or flag it with impact. Default new rules to disabled/audit and pilot narrowly.
Pinned upstream source
- Repository
- cloudflare/skills
- File path
- skills/cloudflare-one-migrations/SKILL.md
- Pinned commit
53395984c3ea1925d00fce03b266112302f050e6- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
Structured source-vendor exports · Cloudflare One docs/API schemas · Pilot-group rollout
Main topic
Make Agent behavior safer and easier to verify