Skip to content
Custom GPTs retire on 11 Dec 2026. Their Actions do not move to plugins on their own. See what transfers
Plugferry
How it works

Seven fixed stages, one screen each.

A first migration takes about fifteen minutes in the app. OpenAI identity verification can take days, so start it on day one.

  1. Stage 1: Import

    4 min

    Paste the GPT’s name, instructions, starters, knowledge files and Action schemas, in the order the GPT editor shows them. Or paste an OpenAPI spec. Each API is called once to check it answers, and its terms and quota are shown beside it.

  2. Stage 2: Review

    30 s

    The transfer matrix shows what moved, what runs on the bridge and what did not. Failing Actions can be parked with a reason instead of shipped as dead tools.

  3. Stage 3: Metadata

    3 min

    Name, subtitle, description, category, starter prompts and the four policy URLs, validated live against submission limits.

    The publisher name becomes permanent when you submit.

  4. Stage 4: Bridge

    2 min + DNS

    Choose the permanent address, the access mode, and add the API credential once. It is never shown again.

    The MCP URL becomes permanent with the first upload to OpenAI.

  5. Stage 5: Package

    30 s

    Build ZIPs for the ChatGPT directory, Codex and Claude, with the review cases and demo URL inside.

  6. Stage 6: Submit

    outside the app

    A checklist in the order the portal really works, and every field to paste with a copy button. Record reviewer feedback and resubmissions as notes.

  7. Stage 7: Live

    ongoing

    Analytics by client, tool and upstream API. Plugferry tells you what to redo after each change.

Start a migration