Own Your Data Before Your AI Tool Dies (The Exit-Note Discipline)

The shutdown email arrived on a Tuesday: beloved tool, acquired, being folded into an enterprise product, export available for thirty days. I had watched this happen to other people with the sympathy of a bystander. This time it was mine, and the difference between my colleagues who lost a week of work and me, who lost an afternoon, was not luck. It was a discipline I had adopted a year earlier, and this essay is the discipline written down so I stop having to explain it in DMs.

The core principle: the state of your work lives in formats you own, and every tool is replaceable scaffolding around that state. For each critical tool, I maintain three things, an export of the content in open formats, a document of the configuration that matters, prompts, templates, settings, workflows, and an exit note, one page, naming where I would go and what the migration would involve. None of this is complicated. All of it is boring. That is exactly why it is rare.

The export habit is the foundation, and the specifics matter. Formats: markdown beats vendor formats, CSV beats proprietary databases, standard image and video containers beat project files that only one application opens. Cadence: monthly for active tools, quarterly for the rest, because the value of an export decays with age and a stale backup is a memory of safety, not safety. Verification: open the export once, actually look at it, because I have found corrupted exports twice over the years, and both times the finding cost minutes instead of the disaster the same corruption would have caused during a real shutdown.

The configuration document is the part everyone skips and the part that saves the most time. My tools hold invisible work: the voice settings tuned over months, the integration recipes, the prompt library, the folder structure that makes everything findable. The shutdown email offers to export your content, never your configuration. Rebuilding configuration from memory under deadline pressure is how a tool transition becomes a tool funeral; rebuilding it from a two-page document is an errand.

The exit note sounds paranoid and functions as clarity. For each tool: primary alternative, what would be lost, estimated migration hours. Writing it forces an honest answer to a question worth asking anyway, am I locked in, and how much, and the answers have changed my purchasing twice, steering me away from tools whose convenience came with unacceptable exit costs. My Tuesday shutdown took an afternoon: exports downloaded, configuration handed to the replacement tool, exit note executed exactly as drafted. The colleagues without the discipline lost their prompt libraries, their templates, their momentum. Own the state, export on a schedule, write the note. The tools are rentals. Your work is not.