How to upgrade self-hosted n8n to v3 safely

  1. Run the Migration Report. n8n says to open Settings → Migration Report before upgrading. It lists the workflows and settings that need attention (n8n docs: v3.0 breaking changes). For 2.0 the report needed n8n 1.119.0 or later (v2.0 migration tool).
  2. Back up first. Export your workflows and back up the database and Docker volume. See our backup guide. One Reddit user lost all their workflows after a Docker upgrade (r/n8n).
  3. Read the breaking changes. v3.0 changes behaviour and retires some legacy features (docs). The 2.0 changes are also worth knowing: Publish/Unpublish replaced the active toggle, and the release channels were renamed to stable/beta (v2.0 breaking changes).
  4. Pin a version tag. Use a specific version, or the stable tag rather than beta (docs).
  5. Test on a copy first (staging), then upgrade production.
  6. Check our version tracker and avoid releases flagged "Wait".

Weekly: "n8n releases — upgrade or wait?"

One email a week. Breaking changes, safe versions, hosting price changes. Free.

Subscribe free →
Opens our Beehiiv signup page.