I have a cloud instance of version 1.xx . I’m aware that the current version is now 2.xx . We will eventually update, but the last time we updated from 1.A to a newer 1.xxxB, a lot of nodes and code blocks broke for us and we spend a lot of time fixing all workflows.
- Is there a way to spin up another version v2.xx IN THE SAME ACCOUNT (without paying for another account) so that we can develop in parallel, fix all discrepancies and still keep v1.xx going ? We don’t want to break v1 workflows that are running fine. It’s also easier to migrate in the same account that will eventually upgrade.
- Any tips to make the migrations from v1 to v2 less painful ?
Information on your n8n setup
- n8n version: 1.120.4
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system: