Short answerTell users what is moving, when, where to find the new version, what is different and who to contact. Keep it short, send it before the old version stops working, and link the new access directly.
Template
Subject: [Bot name] is moving to a new home on [date] Hi [name], [Bot name] is moving because ChatGPT is retiring Custom GPTs. What changes - New link: [URL or how to install] - It may answer slightly differently. [Any known differences] - [Anything it can no longer do, e.g. live lookups] What stays the same - It still answers from [your content]. What to do 1. Open [link] by [date]. 2. [Install or sign in steps if needed]. 3. Tell us if anything looks wrong: [contact]. Thanks, [Name]
Tips
- Send it twice: when you migrate and a week before the old version stops.
- Update saved links, onboarding documents and social posts.
- Be honest about differences; do not promise identical behavior.
Before sending, finish the checklist and testing. For plugin recipients see sharing and installing.
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