GPT Migrator
APIs, integrations and technical migration

Rebuilding a Custom GPT with the OpenAI API

Last checked October 18, 2026
Short answerIf you rebuild on the OpenAI API, use the Responses API. OpenAI's migration page says the Assistants API was sunset on August 26, 2026 and recommends Responses for new integrations. You will also build the chat page, file retrieval and any tool connections yourself.

Checked October 18, 2026 against OpenAI's Assistants-to-Responses migration page. API docs change often; confirm before building.

Assistants API status

OpenAI's page states that the Assistants API was sunset on August 26, 2026 and recommends the Responses API for new integrations. Older guides that tell you to rebuild a GPT as an Assistant are out of date.

How the concepts map

Assistants APIResponses API equivalent
AssistantsPrompts: a prompt holds the model, tools and instructions (created in the dashboard, versioned)
ThreadsConversations
RunsResponses: you send input items and receive output items
Run stepsItems

OpenAI notes that reusable prompt objects are being deprecated, so check the deprecation timeline before relying on them long term. The page we reviewed does not cover file search or vector stores; read the Responses API documentation for that.

What you still build

This path suits developers or teams with budget for a custom build. Otherwise consider simpler options.

Not sure it is simple enough to do yourself?

Tell us what your GPT does, whether it uses Actions and how many files it has. We will say what will break and what a rebuild involves. The audit is free.

Request a free audit

Related guides

Sources

Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.