A set of free converters published on GitHub aims to move workflows out of three automation and AI-agent tools and into n8n, a workflow automation platform. The project, called MigrateFlows, handles exports from OpenAI Agent Builder, Flowise and Pipedream. It runs entirely in the user's web browser, so exported files never leave the user's computer. According to the project's GitHub repository, the converters are meant for workflows built on tools that are shutting down, which makes a clear migration path a practical concern for anyone who depends on them.
What the converters handle
The tools cover three different sources, and each one maps its own building blocks onto n8n nodes. The repository describes how each conversion works, and the details matter for anyone planning a move.
OpenAI Agent Builder
The converter takes the code export from Agent Builder, generated through the Agents SDK in either Python or TypeScript. Each agent becomes an n8n AI Agent that keeps its model, instructions, output schema and memory. Instructions can be static or supplied per request.
Built-in tools such as web search, file search and code interpreter remain OpenAI tools through n8n's OpenAI model, so vector store IDs continue to work. MCP servers are converted into MCP Client tools. The repository states that tokens found in the code are never copied across. Instead, the conversion report tells the user which credential to create.
Logic also gets translated. Guardrails become n8n's Guardrails node, if, elif and else branches and classifiers become Switch nodes, and while loops become If nodes with a loop back. User approval steps are turned into Wait nodes with a form.
Flowise
Flowise support covers chatflow and agentflow exports, as well as a full export made through the Settings menu. Chains and agents are included, from LLM Chains and Retrieval QA to Tool Agents, ReAct agents and supervisor-and-worker teams. Chat models from a long list of providers, along with memory, text splitters and output parsers, carry over as well.
One practical detail stands out. Vector stores keep pointing to the same index, whether it is hosted on Pinecone, Qdrant, Supabase, Postgres or Chroma. According to the repository, nothing has to be re-embedded. Custom tools run inside n8n's Code Tool, and Document Stores come along when the user chooses Export All.
Pipedream
For Pipedream, the converter accepts either the project export or a GitHub Sync folder. Node.js code steps become Code nodes, including patterns such as referring to earlier step outputs, exporting values, ending a flow early and sending responses. HTTP, webhook and schedule triggers, delays, HTTP responses and data stores are also covered.
Common app actions are turned into HTTP Request nodes that use the matching n8n credential. The repository lists Google Sheets, Gmail, Slack, Airtable, OpenAI, Telegram, Discord, GitHub, Outlook, Teams, Google Calendar, SendGrid, Postgres, Supabase, Twilio and Snowflake.
A deadline for Pipedream data stores
The repository highlights one time-sensitive issue. Pipedream data stores are not included in the official export, and according to the project they are deleted on April 30, 2027. Users who rely on stored data should act before then.
To help, the project provides a read-only Pipedream code step, named pipedream-datastore-exporter, that downloads every record as a .datastore.json file. The user places that file next to the export, and the converted n8n workflows come preloaded with the data. The project has published a step-by-step guide at migrateflows.com.
Every conversion also comes with a checklist of manual tasks, such as reconnecting credentials and creating variables. Data does not move on its own, so this checklist is the part most likely to decide how much work a migration takes.
How the project tested its output
The repository reports results for each source. For Agent Builder, 196 real exports that people had published on GitHub were converted into 196 workflows, containing 437 agents in total. According to the project, all of them pass n8n's own workflow validator and import.
For Flowise, the 51 marketplace templates produced 55 workflows. All of them pass the validator and import, and the main patterns were run live in n8n. For Pipedream, 52 public GitHub Sync workflows import without errors, and 317 of 318 code steps compile. The one that fails is broken in the original source, according to the repository.
These figures come from the project itself rather than from an independent audit. They show that the output is structurally valid and importable in n8n, but they do not confirm that every workflow behaves exactly as it did on the original platform. Readers should test important workflows before switching them off.
Known gaps
The repository is open about what does not yet convert. The gaps differ by source, and users should check them against their own workflows.
- Agent Builder: function tools come out as Code Tool stubs because the export does not include their code. OpenAI connectors such as Gmail and Drive must be replaced with n8n nodes. Moderation and hallucination guardrails have no n8n equivalent.
- Flowise: sequential agents from Agentflow v1 and some integration tools are not supported.
- Pipedream: Python steps are in beta, and less common app actions become items on the manual checklist.
Anyone who runs into a problem can open an issue on GitHub, provided they remove private information from the export first. The project also accepts messages at hello@migrateflows.com.
Running the tools locally
Users can work through the website or the command line, which requires Node.js 18 or later. Each run writes one .n8n.json file per workflow along with a report. The site can also be hosted locally with a single command. An examples folder includes sample inputs written for the project, along with the n8n workflows they produce.
The code is released under the MIT license. MigrateFlows describes itself as independent and not affiliated with OpenAI, FlowiseAI, Pipedream, Workday or n8n.
For teams facing a shutdown, the converters offer a concrete starting point, and the export-and-checklist approach keeps data on the user's own machine. The remaining work, such as reconnecting credentials and testing edge cases, still falls to the people who own the workflows. The April 30, 2027 deadline for Pipedream data stores makes that work worth starting early.
Related: Turn a PDF CV into a Master Google Sheet with n8n and easybits · n8n Workflow Parses Gmail Invoices Into Sheets With Slack Alerts
Comments (0)