Workflow: migrating a zone off Page Rules

TL;DR: Trace before touching the old rule Use Cloudflare Trace on the affected URLs: confirm the new rule fires and produces the same behavior. # Workflow: Page Rules migration Page Rules are deprecated. Migrate deliberately, one rule at a time. ## 1.

Workflow: Page Rules migration

Page Rules are deprecated. Migrate deliberately, one rule at a time.

1. Inventory

List every Page Rule: URL pattern plus action. Page Rules are count-limited so the list is manageable. For each, identify its replacement:

• URL forwards -> Single Redirects (Bulk Redirects for large static lists)
• Header/URL rewrites -> Transform Rules
• Cache settings -> Cache Rules
• Origin overrides -> Origin Rules
• SSL and misc settings -> Configuration Rules

2. Recreate in the new product

Write the equivalent rule with a matching expression. Watch the constraints: Single Redirects quotas are 10/25/50/300 by plan; regex needs Business or Enterprise. Consolidate where the quota forces it.

3. Trace before touching the old rule

Use Cloudflare Trace on the affected URLs: confirm the new rule fires and produces the same behavior. The new products execute before Page Rules and override them on match, so a slightly different expression changes behavior immediately, not when you delete the old rule.

4. Disable, verify, delete

Disable the Page Rule (do not delete), verify in production with curl, then delete after a stable week. The disabled rule is your rollback.

5. Audit for stacking

On non-conflicting matches, old and new products can both apply in surprising ways. After each migration, re-trace the URL and confirm exactly one system handles it.

Checklist

• One Page Rule at a time; trace each before disabling.
• Quota planning on lower plans; regex only where the plan allows.
• Disabled-not-deleted for a week as rollback.

When to use

You hit exactly this: Workflow: migrating a zone off Page Rules in Workflow.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Workflow.

Edge cases

• For each, identify its replacement: - URL forwards -> Single Redirects (Bulk Redirects for large static lists) - Header/URL rewrites -> Transform Rules - Cache settings -> Cache Rules - Origin overrides -> Origin Rules - SSL and misc settings -> Configuration Rules ## 2.

Composite workflow grounded in verified docs: Page Rules deprecated, per-product replacements, Single Redirects quotas (10/25/50/300) and regex plan limits, new products override Page Rules, Trace for verification. Refs: https://developers.cloudflare.com/rules/page-rules/ , https://developers.cloudflare.com/rules/url-forwarding/