How to migrate a custom GPT, step by step

Step 1: Take stock

Write down what your GPT has: instructions, number and type of knowledge files, Actions, who uses it, and how it is shared. The free checker builds this inventory from what you paste in.

Step 2: Back everything up

Copy your instructions into a text file and keep the original knowledge files in one folder. Details: exporting instructions and backing up files. The free Chrome extension can export a GPT's instructions, and its files where ChatGPT allows.

Step 3: Choose a path

Path A: OpenAI's Migrate to plugin

Best if your users stay in ChatGPT. You must be the GPT's creator or a workspace owner or admin, the GPT must be published, and plugins must be enabled for you. Full steps in our plugin migration guide.

Path B: Rebuild on another platform

Create the assistant on a platform you prefer, paste in the instructions and upload the files. For example, see moving to a Claude Project. Compare options in alternatives.

Path C: Host it yourself

If the bot is customer-facing, a standalone page may suit better. See hosting a custom GPT outside ChatGPT.

Step 4: Rebuild Actions

Actions do not transfer automatically. Inventory each endpoint and decide how to reconnect it. See migrating GPT Actions.

Step 5: Test, then switch users

Run the same real questions through the old and new versions and compare. Our testing guide has a scorecard. Then tell your users where the new version lives.