Migrate from Chatbots to Agents (in-app tutorial)
A simple, in-app walkthrough to move from Chatbots to Agents in OpenAssistantGPT.
Why move to Agents?
Agents are the next generation of chat experiences in OpenAssistantGPT. They’re faster, smarter, and come with improved reliability and features like better web search, knowledge attachments, and optional computer-use.
Important: By mid-2026, all chat experiences in OpenAssistantGPT must run as Agents. If you haven’t migrated by then, we will automatically migrate your chatbots to Agents to ensure nothing is turned off.
Why you need to migrate
- OpenAI is deprecating the Assistant API v2.
- The Responses API is the replacement and the long-term supported path on OpenAI’s platform.
- In OpenAssistantGPT, the Responses API is delivered through Agents, so moving from Chatbots to Agents ensures your experiences keep working without interruption.
Before you start
- Identify which chatbot(s) you want to migrate
- Note their current settings: name, welcome message, error message, prompt, model, web search, files/knowledge
Step 1: Review your existing chatbot
- Go to Dashboard ➜
Chatbots
. - Click your chatbot to open its settings.
- Review and copy the important settings you want to keep (welcome message, prompt, attached files, web search, etc.).
Step 2: Create your Agent
- Go to Dashboard ➜
Agents
. - Click
Create new Agent
. - Fill in the details:
- Display Name
- Welcome Message and Error Message
- Prompt (copy from your chatbot if desired)
- Model (choose your preferred model)
- Key usage (use your default key or provide your own)
- Optional features: Web Search, Computer Use, Files/Knowledge
- Click
Save
. You’ll see your new Agent in the Agents list.
Step 3: Attach your knowledge (optional)
If your chatbot used files/knowledge:
- Open your new Agent from Dashboard ➜
Agents
. - Add the same files/knowledge you used in your chatbot.
- Save.
Step 4: Test your Agent
- From Dashboard ➜
Agents
, open your Agent. - Use the built-in chat to test greetings, typical questions, and any tool/knowledge features.
- Tweak the prompt or settings if needed and save again.
Step 5: Replace your old chatbot where needed
- If you were using your chatbot inside the app (e.g., internal support), start using your Agent from the
Agents
section. - If you had your chatbot publicly available (e.g., embedded on a site), open your Agent and use its Embed section to replace the previous experience.
Tip: Keep the old chatbot available until you’ve confirmed the Agent behaves the way you want.
After migration
- Monitor conversations in Dashboard ➜
Agents
. - Adjust prompt, files, or features (web search, computer use) as your needs evolve.
- You can remove or archive your old chatbot once you’re confident with the new Agent.
Timeline and automatic migration
- By mid‑2026, all chat experiences will run as Agents.
- If you don’t migrate in time, we will migrate your chatbots to Agents for you to ensure nothing is turned off.
FAQ
- Do I need technical changes to migrate?
- No. You can complete the migration entirely within the app by creating an Agent and replacing your previous chatbot usage.
- Will my conversations be impacted?
- Your new Agent will handle new conversations. Keep your old chatbot active until you validate the Agent’s behavior.
- Can I use the same knowledge/files?
- Yes. Attach the same files in your Agent settings.