AI tool migration checklist: what to move before you cancel
Before cancelling an AI subscription, extract five things: your data in a portable format, saved prompts and instructions, custom voices or styles, integration credentials, and billing history. Cloned voices and trained styles are the assets least likely to survive the move.
By the AI Alt Finder team
Cancellation is the point of no return, and most tools delete rather than archive. Work through this list while your account is still active, in this order, because the items at the top are recoverable later and the ones at the bottom are not.
1. Export the data, then open the export
An export you have not opened is not a backup. Download it, unzip it, and confirm the format is something another tool can read. Vendors sometimes export to a proprietary structure that is technically your data and practically unusable.
Check completeness too. Where a product splits into a client and a hosted backend, an export frequently covers only the client side, and the part that made it work stays with the vendor.
2. Save your prompts and project instructions
This is the highest-value item per minute spent and the one most often skipped, because prompts feel disposable. They are not: a refined instruction set is months of accumulated correction, and it usually transfers to a replacement with light editing.
Copy them into a plain text file in your own storage. Not in the tool you are leaving, and not in the tool you are joining.
3. Rebuild expectations for cloned voices, trained styles and fine-tunes
These almost never move. A voice cloned inside a speech platform, a style trained inside an image tool, or a model fine-tuned inside a vendor's console generally cannot be exported into a competitor.
What you can save is the input: the source recordings, the reference images, the training data. Keep those and the asset is rebuildable. Lose those and the switch has a hidden cost nobody quoted you.
4. Inventory integrations before you break them
- List every place the tool holds a credential: repositories, cloud storage, calendars, messaging, payment platforms.
- Revoke access at the source, not just inside the tool being cancelled. A revoked subscription does not always revoke an OAuth grant.
- Note every automation that calls the tool's API. Those fail silently and you will find out from a user rather than from a dashboard.
- Rotate any key that was shared with the outgoing vendor, especially if it was pasted into a hosted configuration.
5. Keep billing records and note the real cancellation date
Download invoices before losing account access; some vendors close the billing portal with the account. If you paid annually, find out whether cancelling ends access immediately or at term, because that changes whether you can run both tools in parallel for free.
Then set the cancellation date after your parallel-running window, not before it. Cancelling first and migrating second is how a bad week becomes a bad month.
The order matters
Export, then prompts, then irreplaceable assets, then integrations, then billing. Reversing that order means discovering an incomplete export on the day access ends, which is the single most common way a planned migration turns into a loss.