Transfer app configurations between environments.
Overview
Import and export functionality enables you to:
- Backup app configurations.
- Share setups across teams.
- Migrate between environments.
- Version control outside the platform.
Export
What’s Exported
App-level export includes:
| Component | Included |
|---|
| App metadata | Name, description, settings |
| Orchestration | Pattern, configuration |
| Agents | All agent definitions |
| Tools | Workflow, code, MCP tools |
| Knowledge | Search AI connections |
| Events | Event configurations |
| Memory stores | Schema definitions |
| Variables and Namespaces | Environment and content variables |
| MCP servers | Server configurations |
| Processors | Pre processors and Response processor |
Agent-level export includes:
| Component | Included |
|---|
| Agent metadata | Name, description, instructions |
| Tools | Associated tools references. The tool configurations are part of the app-level export. Agent export does not export configuration related to the tools. |
| Delegation rules | Handoff configuration for Adaptive Network Orchestration |
What’s NOT Exported
- API keys and secrets
- Actual data in memory stores
- Usage analytics
- Deployment history
Export Process
- Navigate to Deploy → Export/Import.
- Select Export tab.
- Choose export type:
- App: Full application export
- Agents: Selected agents only
- Select version (if applicable).
- Click Export.
- Download the JSON file.
File Naming
App level export: <app-name>-export-<timestamp>.zip, includes app level config and individual files for workflow tools that are part of the app.
Agent level export: agents-<app-name>-<timestamp>.json
Import
Prerequisites
- Import permissions in your account
- Valid JSON or zip file (max 5 MB)
- Target app must exist.
Import Process
- Navigate to Deploy → Export/Import.
- Select Import tab.
- Upload JSON/Zip file.
- Review component summary:
- App details
- Agents and tools
- Knowledge sources
- Memory stores
- Variables
- Resolve any conflicts (highlighted in red).
- Click Import.
Import Order
Components are imported in dependency order:
1. Tools (standalone)
2. Agents
3. App configuration
4. Events
5. Memory stores
- Any existing app configuration is overwritten during the import process.
- The import file can’t exceed 5MB in size.
- Partial imports aren’t supported. In case of errors, import fails.
Handling Conflicts
Missing Dependencies
If imported configuration references missing items, errors are shown and import fails.
Options:
- Verify the file.
- Retry after appropriate changes in the file.
Model Availability
If AI models don’t exist in target, warnings are shown.
Options:
- Configure the required models
- Select alternative models after import.
Environment Variables
Variables are exported but values may need updating:
{
"env_variables": [
{
"name": "API_KEY",
"value": "***REDACTED***",
"is_secret": true
},
{
"name": "API_URL",
"value": "https://api.example.com",
"is_secret": false
}
]
}
After import:
- Navigate to Settings → Environment.
- Update secret values.
- Verify non-secret values are correct.
Best Practices
Before Export
- Test the app thoroughly.
- Document the configuration.
- Note any external dependencies.
- Verify all tools are deployed.
Before Import
- Backup existing configuration.
- Check model availability.
- Prepare environment variables.
- Review import summary carefully.
Version Control
Store exports in version control:
configs/
├── production/
│ ├── app-customer-service-2024-01-15.json
│ └── app-customer-service-2024-01-01.json
├── staging/
│ └── app-customer-service-latest.json
└── README.md
Migration Checklist
## Pre-Migration
- [ ] Export source configuration
- [ ] Document external dependencies
- [ ] List required API keys
- [ ] Note model requirements
## Import
- [ ] Create target app (if new)
- [ ] Upload configuration
- [ ] Resolve conflicts
- [ ] Update environment variables
## Post-Migration
- [ ] Configure API keys
- [ ] Test all agents
- [ ] Verify tool functionality
- [ ] Run diagnostics
- [ ] Test end-to-end flows
Troubleshooting
Import Fails
“Invalid JSON format”.
- Validate JSON syntax.
- Check file wasn’t corrupted.
“File too large”
- Maximum size is 5 MB.
- Split into separate exports.
“Missing required field”
- Ensure export is from compatible version.
- Check for manual edits that removed fields.
Configuration Issues After Import
Tools not working
- Redeploy workflow tools.
- Check API connections.
- Verify environment variables.
Agents not responding correctly
- Review instruction import.
- Check knowledge connections.
- Verify model configuration.