Short answerPackage the work by complexity (simple, medium, complex), start every job with an audit, deliver a documented handover, and never promise identical behavior, because platforms differ.
Offer structure
| Tier | Includes |
|---|---|
| Audit | Inventory, risks, recommended path |
| Standard migration | Instructions and files moved, tested, handed over |
| Advanced rebuild | Actions or integrations rebuilt, extended testing |
Protect yourself and the client
- Define success as a test set both sides agree on.
- State that behavior will differ slightly across platforms.
- Keep client accounts and keys in the client's name.
- Price after the audit, since complexity is hidden until you see Actions and files.
Use the intake questions and handover template. We do not publish rate benchmarks because we have no verified data.
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 auditRelated guides
Sources
Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.