Import and export
Agents are portable. You can bring one in from another platform, and you can export any Glytos agent as a self-contained file to back up, version, or move between workspaces.
Migrating in
Open Agents -> Import / Migrate. Pick the platform you are coming from:
| Source | Becomes | Kind |
|---|---|---|
| Vapi | A prompt agent | Voice |
| Retell | A prompt agent, or a workflow if it has multiple states | Voice |
| Bland | A prompt agent, or a workflow for a multi-node pathway | Voice |
| OpenAI Assistants | A chat agent | Chat |
| Glytos backup | Whatever it was exported from | Backup |
Each source offers two ways in:
- Connect - paste the platform's API key, and Glytos lists your agents so you can pick which to import. The key is used only for that request and is never stored.
- Paste JSON - paste an export you already have. Useful for one-offs, or when a platform's API is no longer reachable.
Not every source offers both. OpenAI Assistants is connect-only in the app; a saved assistant definition can still be imported through the API (see below).
Every import lands in your Development environment, so you can review and test it before promoting it up.
A multi-step Retell or Bland flow becomes a Glytos workflow: each state becomes a node, and a prompt-based transition becomes an AI edge - the same LLM-decided routing Glytos uses natively. Review the transitions after importing.
Function tools
Function tools come in as stubs: the model knows the tool's name, description and parameters, but only you know the endpoint behind it. An imported tool has no URL and will not run until you open it and set its endpoint and auth. Nothing an import creates can place a live call on its own.
The mapping report after an import lists exactly what carried over and what needs your attention - a tool to wire up, a voice id to confirm, a webhook to reconnect.
Migrating away from OpenAI Assistants
OpenAI removes its Assistants API on 26 August 2026, so /v1/assistants, /v1/threads
and the endpoints around them stop answering. The models are unaffected; what is being
retired is the orchestration layer around them, which is the part Glytos replaces.
Import from Agents -> Import / Migrate -> OpenAI Assistants. Each assistant becomes a Glytos chat agent.
What maps onto what
| OpenAI Assistants | Glytos |
|---|---|
| Assistant | A chat agent |
| Instructions | The agent's system prompt |
Model, temperature, top_p | The agent's model settings |
response_format | Structured outputs (json_object and json_schema) |
| Function tool | An HTTP tool - schema imported, endpoint set by you |
| Thread | A session, with its transcript, events and cost |
| Run | One turn inside that session |
| File Search | Knowledge base or a vector store - re-upload the files |
| Code Interpreter | Not imported |
A strict json_schema is adjusted automatically to the closed-object form OpenAI
requires (additionalProperties: false, all keys required, optionals made nullable),
so a schema that worked on an Assistant does not start returning 400s here.
After the import
The report names what still needs you. In practice that is two things: give each imported tool its endpoint URL and auth, and re-upload any File Search documents into a knowledge base. Until a tool has an endpoint it cannot run, so an import can never place a live call on its own.
Import before the API closes
One-click Connect reads your account through OpenAI's own API, so it works only while OpenAI is still serving it. Run the import before 26 August 2026 even if you are not ready to finish the configuration - bringing the definitions across and wiring them up are separate jobs, and only the first one has a deadline.
If you already hold a saved assistant definition, the API accepts it directly:
POST /imports/openai-assistant with {"assistant": { ... }}, which every Glytos server
SDK wraps.
For the fuller comparison - what you gain, what it costs, and how the two platforms differ - see the OpenAI Assistants migration guide.
Exporting an agent
From an agent's menu, choose Export as JSON. You get a portable glytos-agent
document containing the agent's configuration (or workflow graph) with every tool it
uses inlined, so it is fully self-contained.
The export is secret-free. Provider keys, credentials, webhook auth headers and phone numbers are stripped out and listed as reconnect notes instead - so the file is safe to commit to version control or hand to a teammate.
To bring an export back, use Import / Migrate -> Glytos backup and paste it. Tools are recreated, references are re-linked, and the new agent lands in Development. This makes the export a natural fit for backups, templates, and moving an agent between workspaces.