- EXPORT
- IMPORT
- SYNC
- HUMAN
Short answer
How can I move my Huginn agents to a new instance?
Your AI uses the export and import tools to transfer JSON configurations between Huginn instances. This handles the heavy lifting of moving agent logic and settings from one place to another. You'll get a clean handoff of your automation logic.
Migration outcomes.
Where your data lands.
Moving your automation logic results in these specific states.
EXPORT
Local JSON files
The AI pulls the full configuration for a specific agent. You get a structured JSON file ready for transfer.
IMPORT
New instance setup
The AI pushes the JSON data into a different Huginn instance. The agent is recreated with its original settings.
SYNC
Configuration parity
The AI ensures the new agent matches the old one. This keeps your automation logic consistent across environments.
HUMAN
Manual verification
You check the new instance to ensure everything runs as expected. The AI handles the data, but you confirm the logic works.
The workflow
What your AI does when the migration starts.
The AI acts as the bridge between your different Huginn environments.
Extract configuration
The AI reaches into your source Huginn instance to grab the specific agent settings.
export_scenarioPrepare data
The AI processes the exported JSON to ensure it is formatted correctly for the target instance.
export_scenarioDeploy to new instance
The AI sends the configuration to the destination Huginn instance to recreate the agent.
import_scenarioFinalize setup
The AI confirms the import was successful and the agent is active in the new location.
import_scenario
Try it
Copy these to start.
Use these prompts to trigger the migration process.
Starting points
Replace the specific agent names or instance details with your actual Huginn data.
Huginn Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_8UV07EE94E40B2vM3BaaCGQMXBHXynlm3Lbj3L9h/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Huginn capabilities are ready to use.
{
"mcpServers": {
"huginn-ifttt-alternative-mcp": {
"url": "https://edge.vinkius.com/vk_preview_8UV07EE94E40B2vM3BaaCGQMXBHXynlm3Lbj3L9h/mcp"
}
}
}Export the configuration for my 'RSS Monitor' agent from my primary Huginn instance.
Take the JSON from my 'Web Scraper' agent and import it into my staging Huginn instance.
Can you move my 'Price Tracker' agent to the new instance using the export and import tools?
List my current agents so I can pick one to migrate to my backup instance.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Huginn once, then ask.
Just link your instance to Vinkius. Your credentials stay encrypted, and you can start managing your agents through your AI client immediately.
Connect Huginn to your AIFAQ
Common questions about migration
- 01
Will the AI delete my original agent after exporting it?
No. The export tool only reads the configuration; it does not delete anything from your source instance.
- 02
Can the AI change my agent's logic during the move?
No. The AI moves the JSON exactly as it exists. It does not modify the underlying automation logic.
- 03
Does this work for all Huginn agents?
Yes, any agent that can be represented as a JSON configuration can be moved using these tools.
- 04
Do I need to manually create the agent in the new instance first?
No. The import tool creates the agent for you using the exported data.
- 05
Can the AI fix errors in my agent configuration while importing?
No. If the JSON is invalid or incompatible with the target instance, the import will fail. The AI does not rewrite your code.
More questions about Huginn? The Connector page answers them. See everything the Huginn Connector can do
Connect Huginn to Claude, Cursor, ChatGPT & more
