Clarification on whether upgrading a self‑hosted Community n8n instance to a paid plan unlocks historical workflow versions from before the upgrade or only records history going forward

Questions
1

Hi n8n team,

We’re currently running a self‑hosted Community Edition instance and are considering upgrading to a paid self‑hosted plan (e.g., Business/Enterprise) to get full workflow history and Git-based version control.

One thing I’d like to clarify before upgrading:

If we upgrade our existing self‑hosted instance (keeping the same database), will workflow history and/or Git-based version control:

  1. Only apply to versions created from the moment we upgrade onward, or

  2. Also expose any existing historical revisions already present in our database (beyond the current Community limits)?

In other words, will we gain access to any “older” workflow versions that may already exist in the DB but are currently hidden by plan limits, or is all history effectively “from upgrade date forward” for the enhanced features?

Thanks in advance for clarifying this… important factor in how we plan our migration.

Best,
Aidan

2

hello @aidanm

Highly probable, only upwards. I don’t see any evidence that the DB can store any version before the published one

3

Hi @aidanm I guess with enterprise level self hosted plan you will get complete history i am not very sure for cloud but for self hosted that is the case