frappe-ops-upgrades

Guide Frappe/ERPNext v14-to-v16 upgrades with migration checks and rollback.

163|53|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-upgrades-impertio-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frappe-ops-upgrades
Source: https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-upgrades
Command: npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-upgrades-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents broken Frappe/ERPNext upgrades caused by skipped migrations, missing pre-upgrade checks, incompatible dependencies, or unsafe rollback decisions.

Core Features & Use Cases

  • Major upgrade planning (v14 → v15 → v16): choose the correct upgrade order and sequencing to avoid patch/schema mismatches.
  • Migration readiness + troubleshooting: run readiness checks, diagnose stuck/failed patches, and re-run patches safely using the patches.txt date-suffix mechanism.
  • Safe rollback procedures: recover from failed upgrades using pre-upgrade database + file backups without corrupting schema state.

Quick Start

Upgrade your site by backing up (with files), switching to the target version branch, running bench update, and then verifying migrations and runtime health.

Frequently Asked Questions about frappe-ops-upgrades

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely upgrade Frappe from v14 to v16?

Safely upgrading Frappe requires sequencing major upgrades through v15, completing pre-upgrade readiness checks, switching branches, running bench update, and verifying runtime health.

Why does bench migrate fail during a Frappe version upgrade?

A bench migrate failure during a Frappe upgrade is often caused by skipped migrations or incompatible dependencies, requiring you to diagnose stuck patches and re-run them safely using the patches.txt date-suffix mechanism.

What is the correct rollback procedure for a failed ERPNext upgrade?

Rolling back a failed ERPNext upgrade requires restoring pre-upgrade database and file backups without re-running bench migrate to avoid corrupting the schema state.

Can I test Frappe major version upgrades on a staging site first?

Yes, you can test Frappe major version upgrades on a staging site first, applying the same bench update and migrate workflows to validate migration readiness and protect customizations before production.

How do I re-run a stuck patch in Frappe after a failed upgrade?

To re-run a stuck patch in Frappe after a failed upgrade, you diagnose the failed patch and apply the patches.txt date-suffix rules to safely bypass or re-execute the migration without breaking schema state.