Migrate from Flowise to IgnitionRAG
Flowise froze the code on 29 July 2026 and archived its repository on 13 August 2026. This guide covers a manual migration to a France-hosted managed RAG platform — with no automatic importer for Flowise graphs.
The official FlowiseAI/Flowise repository is archived: no more pull-request review, official presence ended 31 August 2026. The archival announcement planned to deprecate npm packages and Docker images; npm and Docker Hub remain active today. An Apache-2.0 fork remains possible, but you then operate security, RAG and governance. IgnitionRAG is the managed alternative. This is not a graph converter: you recreate sources, collections and agents.
What you take — and what you leave
Take the documents, business connectors, agent instructions and channels (widget, API). Leave the Flowise node graphs: IgnitionRAG does not import visual flows. Managed RAG (chunking, hybrid search, reranking, evaluation) replaces node assembly. Detailed comparison on the IgnitionRAG vs Flowise page.
SaaS or license: the economic model
On SaaS Solo/Team, AI is platform-managed with credits included (no API key needed). BYOK (bring your own keys) is reserved for Agency/ESN/Dedicated licenses, with no markup on tokens. Do not plan to paste an OpenAI key into the Solo or Team offer.
Migrate from Flowise in 5 steps
- 1
Inventory flows, sources and channels
List chatflows, document stores, connectors and widgets or APIs still in production. Capture system prompts and a regression question set. That inventory is the migration spec.
- 2
Recreate collections and connect sources
In IgnitionRAG, create collections and reconnect sources (SharePoint, Drive, web, files). Run ingestion and check chunking. There is no Flowise graph import: documents and connectors migrate, not the canvas.
- 3
Rebuild agents and workflows
Recreate agents and routing in natural language or via the visual builder, using the MCP server if you work from Claude, Cursor or VS Code. Reuse the instructions, not the nodes.
- 4
Check citations and answer quality
Replay your regression questions. Verify source citations, the audit log and per-tenant isolation. Tune retrieval before exposing a channel.
- 5
Cut over widget, API or MCP, then retire Flowise
Point the widget, REST API, TypeScript/Python SDK or MCP server at IgnitionRAG. When the recipe is green, decommission the Flowise instance (or keep a frozen fork off production).
FAQ
Is there an automatic import of Flowise flows?
No. IgnitionRAG has no importer for Flowise graphs. Migration means reconnecting sources, recreating collections and agents, then rewiring channels.
Do I need to provide an LLM key?
Not for SaaS Solo/Team: AI is platform-managed with credits included. BYOK (bring your own keys) is reserved for Agency/ESN/Dedicated licenses.
Has Flowise really stopped?
The official GitHub repository has been archived since 13 August 2026, after a code freeze announced on 29 July 2026. The marketing site may still present the product; there is no official maintenance. The IgnitionRAG vs Flowise comparison details the status.
Go further
Deploy AI agents that work for your company.
Connect authorized knowledge and tools, then put an agent to work where your team needs it.