# Migrating off Page Rules

Page Rules are deprecated. Each Page Rule action maps to a current product:

- URL forwards / redirects -> **Single Redirects** (or Bulk Redirects for large lists)
- Header or URL rewrites -> **Transform Rules**
- Cache settings -> **Cache Rules**
- Origin overrides -> **Origin Rules**
- Other settings (SSL, etc.) -> **Configuration Rules**

## Migration order

1. Inventory every Page Rule: pattern plus action. Page Rules are limited in count, so most zones have a manageable list.
2. Recreate each in its target product with an equivalent expression. Single Redirects support 10 rules on Free, 25 on Pro, 50 on Business, 300 on Enterprise: plan accordingly.
3. Test with Cloudflare Trace before touching the Page Rule: confirm the new rule fires for the same URLs.
4. Disable (do not delete) the Page Rule, verify in production, then delete.

## Why order matters

The new products execute before Page Rules and override them on match. If you create the replacement while the Page Rule is still active and the expressions differ slightly, the new product wins and the behavior change is immediate, not staged. Trace first.

## Checklist

- One Page Rule at a time; verify each before moving on.
- Watch regex support: only Business and Enterprise Single Redirects support regex. Rewrite patterns accordingly on lower plans.
- Keep the old Page Rule disabled (not deleted) for a week as a rollback path.