Thousands of apps built on Threads, Runs, and Assistants are about to break. The new Responses API is here — and our migration tool automates the transition in minutes, not weeks.
Recursively scans your entire project for every Assistants API pattern — Python, JavaScript, TypeScript. Catches Threads, Runs, Messages, Tools, response_format, and more.
Maps old API calls to their Responses equivalents automatically. client.beta.assistants.create() → client.responses.create(). Threads → conversation state via previous_response_id.
See every change before it's applied. Unified diff output shows exactly what's being replaced — no surprises, full transparency.
Safe by default. The tool never modifies files without the --apply flag. Verify everything first, commit your code, then migrate with confidence.
Full support for both the OpenAI Python SDK and the JavaScript/TypeScript SDK. Whatever stack you're on, we've got you covered.
Every finding is classified as High, Medium, or Low risk. High-risk items need manual review. Medium and Low are auto-migratable. Know exactly what's safe to automate.
# Creating a thread, adding messages, and running thread = client.beta.threads.create() client.beta.threads.messages.create( thread_id=thread.id, role="user", content="What's the weather?" ) run = client.beta.threads.runs .create_and_poll( thread_id=thread.id, assistant_id=asst.id ) content = run.choices[0] .message.content
# Single call with conversation state response = client.responses.create( model="gpt-4o", input=[{"role": "user", "content": "What's the weather?"}] ) # previous_response_id tracks # conversation state automatically content = response.output_text
Run python3 migrate.py /path/to/your/project — the tool recursively scans all your Python/JS files for Assistants API usage.
Get a line-by-line breakdown of every pattern found, colour-coded by risk level (High/Medium/Low) with the old code and its replacement shown side by side.
Run python3 migrate.py . --diff to see a unified diff of every change the tool will make. No surprises.
When you're ready, run python3 migrate.py . --apply. The tool applies all safe changes. High-risk items are flagged for manual review.
One-off payment. No subscriptions. Own the tool forever.
For individual developers and small projects
We do the migration for you. End-to-end.
🔥 ALSO AVAILABLE
Bundle this migration tool with a Google Shopping Feed Audit. Two Q3 deadlines. One price.
£199 bundle
Saves £495 vs separate purchases
View Bundle →The Assistants API (using beta.assistants, beta.threads, beta.threads.runs) is being replaced by the new Responses API. Threads become conversation state managed via previous_response_id. Runs become single responses.create() calls. Tool definition formats have also changed. OpenAI announced the sunset date of August 26, 2026.
Yes. After August 26, 2026, all client.beta.assistants, client.beta.threads, and related endpoints will stop working. Your app will return errors for any code still using the old API. Migration before this date is essential.
Absolutely. The default mode is dry-run — it only scans and reports, never modifies files. Use the --diff flag to see every change as a unified diff. Only when you explicitly pass --apply will the tool make changes. We recommend committing your code to version control first.
Yes. The tool recursively scans directories, automatically skipping node_modules, __pycache__, .git, and other non-source directories. It handles projects of any size — from a single script to enterprise monorepos.
Solo (£99) gives you the tool — you run it, review the changes, and apply them yourself. Full Service (£499) includes a concierge migration where we scan your codebase, apply all changes, test the results, and submit a GitHub PR for your review. Ideal for teams who want a hands-off migration.
Just Python 3.8+ and pip install openai (for the SDK reference). The migration tool itself is a single Python file with no external dependencies beyond the standard library.