[BUG] Workspace Import Fails in v3.0.0

[maximusbirkefeld]

Workspace Import Fails in v3.0.0 – "Transaction is not started yet" Error

After upgrading from Flowise v2.2.7-patch.1 to v3.0.0, importing previously exported content fails with a transactional error. This applies not only to full workspace imports but also to partial imports (e.g. tools, chatflows, agentflows). No import functionality currently works in v3.0.0.

Environment Details

• Old Version (Export Source): 2.2.7-patch.1
• New Version (Import Target): 3.0.0
• Installation Method: Docker
• Docker Node.js Version: 22.14.0
• License: Enterprise

To Reproduce

1. Export a workspace, all tools, or flows (chatflow/agentflow) from Flowise v2.2.7-patch.1.
2. Deploy Flowise v3.0.0 via Docker.
3. Attempt to import the JSON file in the appropriate section (workspace, tool, chatflow, etc.).
4. Observe failure and error message.

Expected behavior Exports from earlier Flowise versions (including partial exports like only tools or flows) should be importable into v3.0.0 without transactional errors.

Impact This issue currently prevents migration to Flowise v3.0.0, as no import functionality works — including full workspace imports and partial imports such as tools, chatflows, and agentflows. We are using Flowise under an Enterprise license and rely on stable upgrade paths for operational continuity. A timely fix would be highly appreciated to avoid delays in adopting the new version.

[jlistemann-ish]

vote up .

[LarsEbt]

vote up

[chungyau97]

Hi @maximusbirkefeld,

The failure you're encountering is due to an incompatible export JSON format in version 3.0.0. As it error out before starting a transaction that's why you receive "Transaction is not started yet".

I will fix 2 errors (trsanction handling, initialize execution as empty array). However, even after that fix, the import will still not work due to the underlying format incompatibility.

Test Data

ExportData-227_patch_1.json

Step-By-Step

1. Set up a staging environment using Flowise version 2.2.7-patch.1.
2. Import ExportData-227_patch_1.json (replace this with your own export data) into staging environment.
3. Update the staging environment from 2.2.7-patch.1 to 3.0.0 version and verify everything works a as expected.
4. Export data from staging environment.

   • Your export should look like this after update:

   • Export data should look like this if using my test data: ExportData-300.json

5. Import ExportData-300.json (replace this with your own export data) into other environment running Flowise version 3.0.0.

[jlistemann-ish]

chungyau97 | HenryHengZJ

Please let me explain why your proposed solution is not viable.

In your Enterprise version you have separate workspaces and RBAC. This serves the aspects of data separation and access control, e.g. to be able to have different projects/customers and employee levels on one application.

What Flowise supports to a limited extent is to ensure that configurations are managed under version control. We would use Git for this and make the exported configurations traceable there and also save them. In the event of code changes, it is then possible to track them there, etc. This could be solved via your REST API, but we are currently using ImpEx in the UI. However, this is only a transitional solution for us. In the long term, we are aiming for a mixed solution of manual editing and automation.

Now to the point. If formats change in Flowise, then it is of course good if the existing configurations are automatically migrated in the app. But in the case of externally saved configurations, there must be traceable ways to migrate configurations without importing them into the app. E.g. with documentation.

For me, there is no way that we can import all projects so that they are also migrated during an app migration. Please write down what I need to customize as projects to the configuration. This configuration is API.

[chungyau97]

Hi @jlistemann-ish,

I will add backward compatibility for Flowise’s ExportData.json starting from version 2.2.7-patch.1, for both UI and API during import.

Additionally, I’ll provide documentation on how to use the import API so you can manage configurations programmatically.

Note: The ExportData.json file from Flowise version 3.0.0 or later is not compatible with older versions of Flowise.

[HenryHengZJ]

@jlistemann-ish

Can you upgrade to 2.2.8 then export the data, pull the 3.0.0 Docker image, then import it back. This will work 100%.

Or

You can backup your database and import it back, this is more technical (https://docs.flowiseai.com/configuration/databases#backup)