Kirby Upgrade and Maintenance

Use Kirby 6 conventions for new work. Check the installed CMS version and the migration guide's verified baseline before upgrading; test on a backed-up copy.

Kirby 5 to 6 acceptance

• Read kirby://kb/scenarios/83-migrate-kirby-5-to-6 before planning. Audit Symfony YAML content as well as blueprints, removed presets, case-insensitive field collisions, option-source changes and invalid values.
• Distinguish legacy sections from pickers: lists store no value. Port custom sections and array-based fields to PHP classes and rebuild all Panel assets for Vue 3.
• Remove query.runner, test dashed field access and unknown methods; migrate blueprint object APIs, guards, template reserved names and auth/session integrations.
• Preserve role permission configuration; it is not the deprecated model permissions API. Test allowed/denied roles, pending 2FA, fresh cookies and editor workflows.
• Back up content/accounts/config as well as the lockfile. A dependency rollback alone cannot undo content writes or account changes.

Quick start

• Follow the workflow below for safe, incremental upgrades.

KB entry points