n8n is a great way to start automating, but many teams reach a point where they need more: conversational AI agents, LATAM e-invoicing, SLA-backed support, or on-premise deployment with full control over their data. The good news is that migrating doesn't mean rebuilding everything from scratch. The Floogos importer converts your n8n workflows automatically —today with 97% coverage— and hands you a report showing what's ready and the little that's worth reviewing. This guide walks you through the whole process, step by step.
Understand why (and when) to migrate
Before moving anything, be clear on what you gain. Teams usually migrate to Floogos when they need:
- Multichannel conversational AI agents (Web, Telegram, WhatsApp, Instagram) with memory and real data
- Ready-to-use LATAM e-invoicing (Mexico, Colombia, Peru, Argentina and more)
- On-premise or your-cloud deployment, with full control over where your data lives
- Forms, dashboards and execution insights without bolting on separate tools
- SLA-backed support and a platform with a company behind it
💡 Tip: you don't have to migrate everything at once. Start with 2-3 representative workflows, validate the result, and scale with confidence.
Know what converts automatically
The importer is not a simple copy-paste: it interprets the n8n JSON and translates it into the Floogos model. Specifically, it:
- Maps n8n nodes to their Floogos equivalents (HTTP, integrations, logic, data, etc.)
- Translates n8n's {{ $json.field }} expressions into Floogos' variable syntax
- Rebuilds triggers and webhooks so the flow fires just like before
- Preserves the visual layout of nodes so the canvas feels familiar
💡 Tip: nodes without a direct equivalent (some very specific ones, for example) are converted into an HTTP node or a marker, so you never lose the flow's structure.
Export your workflow from n8n
In n8n, open the workflow you want to migrate and export it to JSON:
- Open the workflow in the n8n editor
- Menu (···) → "Download" to save the .json file
- Repeat for each workflow you want to migrate (or select several and export together)
- Save your credentials separately too: for security, n8n does not export them in the JSON
💡 Tip: name the files clearly (e.g. "orders-to-crm.json"). It helps you map them against the conversion report.
Import the JSON into Floogos
From Floogos, import the file and let the platform do the heavy lifting:
- Go to the workflow editor and choose "Import"
- Select the n8n source and upload your .json file
- Floogos converts the flow and opens it directly in the visual editor
- You get a conversion report detailing every node
💡 Tip: got many workflows? Import them in batches and review the consolidated report instead of going one by one.
Review the report and fill in the gaps
This is the key to a stress-free migration: the report tells you exactly what to review, no guessing.
- 1:1 converted nodes: nothing to do, they're ready
- Nodes converted as HTTP/marker: check the service's parameters and credentials
- Re-assign credentials in Floogos (remember they don't travel in the JSON)
- Use Floo AI to complete or rewrite a step by describing it in natural language
💡 Tip: Floo AI is also handy for improving the flow while you migrate: ask it to add error handling or a notification and it generates it right on the canvas.
Test, observe and activate
Before going to production, validate the flow with the built-in observability tools:
- Run the workflow with test data and review the trace step by step
- Check the insights to see timings, errors and bottlenecks
- Adjust what's needed and re-run until it's all green
- Activate the workflow (and its trigger/webhook) to set it live
💡 Tip: keep the original n8n workflow paused for a few days as a backup, until you confirm the Floogos version works the same or better.
n8n migration checklist
Frequently asked questions
Are n8n expressions converted too?
Yes. The importer translates n8n's {{ $json.field }} expressions into Floogos' variable syntax, so data passing between nodes keeps working without you rewriting them by hand.
What happens with a node Floogos doesn't support natively yet?
It isn't lost: it's converted into an equivalent HTTP node or a clearly flagged marker in the report. You keep the flow's structure and only have to complete that specific step, often with help from Floo AI.
Do I have to load my credentials again?
Yes, for security. n8n doesn't include credentials in the exported JSON, so you re-assign them in Floogos once and they become reusable across all your workflows.
Can I keep running on-premise like in n8n?
Yes. Floogos can be deployed on-premise or in your own cloud, keeping full control over where your data lives, with the added benefit of AI agents, e-invoicing and support.
Migrating from n8n to Floogos isn't a leap into the unknown but a guided move: you export, import, review a clear report and activate. You gain AI agents, LATAM e-invoicing, forms, dashboards and support, without giving up on-premise control. Start with a handful of workflows and see for yourself how far 97% automatic conversion takes you.