Before a nonprofit builds daily work inside an AI tool, it should test whether that work can leave. Export representative prompts, files and outputs, open them outside the platform, and ask a second person to reproduce a task. If the team cannot do that, the subscription creates an operational dependency that its monthly price does not reveal.
What happens to our work if the vendor disappears?
The AI market is moving fast. New tools appear every week; some raise investment and grow quickly, some are acquired or change business models, and some simply disappear. This creates a risk that is often underestimated: operational dependency.
Your nonprofit may believe it is buying a software subscription. In reality, it may slowly be building part of its institutional knowledge inside someone else's platform.
The Subscription May Be Temporary. The Dependency May Not Be.
Consider what happens after twelve months of regular use. Your team may have created hundreds of prompts, standard operating procedures, research workflows, proposal templates, custom assistants, internal knowledge collections, reusable output formats, approved, non-sensitive service records and reporting structures.
At the start, the tool was convenient. A year later, it may have become infrastructure - and this can happen without anyone formally deciding it should. No meeting was held where management said, "We want this startup to become an important part of our operational knowledge system." It simply happened through daily use.
The Export Test
One of the simplest procurement questions for an AI vendor is: how can we export our work? Do not stop at "yes, export is supported" - ask in what format.
The format matters. Markdown, JSON, CSV, DOCX and structured records can support reuse, depending on what they contain. A PDF can preserve a readable record without preserving an editable workflow. Open the files and try rebuilding one ordinary task in a different tool. A download button alone does not prove portability.
Portability Should Be Part of Procurement
Procurement teams often evaluate whether a product works today. They should also evaluate whether the organisation can leave tomorrow. A useful AI tool should not require permanent loyalty - the organisation should have a realistic path to move its information elsewhere.
| What you export | What to ask | A sign that it passes |
|---|---|---|
| Prompt library | Can we download reusable prompts, not only chat transcripts? | Instructions are readable, editable and linked to their intended task. |
| Workflows and assistants | Can settings, steps and dependencies be documented outside the platform? | A colleague can recreate one workflow elsewhere using the export and instructions. |
| Uploaded knowledge | Can we retrieve source documents and identify the versions used? | Approved files and a source inventory remain available in storage we control. |
| Outputs | Can we download reports and records in usable standard formats? | Another system can open them with their context, dates and structure intact. |
| API access | Is bulk extraction supported on our plan, with documented limits and cost? | A tested route retrieves the records we need without manual copying. |
These are not technical details for the IT department alone - they are business continuity questions.
Vendor Lock-In Is Not Always Intentional
It is worth distinguishing between deliberate lock-in and accidental dependency. Many small AI companies are not trying to trap customers; they are simply focused on growth, and their priorities tend to run in this order: launch features, attract users, improve the product, raise funding, grow revenue. Data portability is often far down that list.
From the customer's perspective, though, the result can be the same. If your organisation builds critical processes inside the tool and cannot easily move them elsewhere, you have created a dependency - and whether that dependency was intentional matters very little once the service shuts down.
Cheap AI Can Still Be Expensive
One reason organisations move quickly with AI is price. Many tools cost €20, €30 or €50 per user per month - trivial compared with traditional enterprise software. That creates a psychological problem: low subscription prices make tools look low-risk, but the subscription fee may be the least important part of the cost.
Imagine a €30-per-month AI tool becomes central to a fundraising team. After two years, it contains donor research, hundreds of proposal prompts, internal templates, funding opportunity assessments, partner notes and reporting structures. Then the company closes. The financial loss is not €30 - it is the time required to reconstruct the operating system the team built inside the platform.
Cheap tools can create expensive dependencies.
What would this look like for a small fundraising team?
The €30 example above is hypothetical, not a reported vendor failure. Picture two fundraisers who use a new assistant to track public donor research and draft proposals. They keep source documents elsewhere at first, but gradually leave prompt instructions, useful comparisons and reporting templates only inside the tool.
The problem: the team has no complete record of how its proposal workflow operates. The tool is now part of the fundraising process, although nobody approved it as critical infrastructure.
The wrong approach: assume a low price makes the risk small and accept “you can export your data” without testing it. When access ends, a pile of transcripts may remain, but the reusable instructions and workflow still need reconstructing.
The better approach: keep approved source files, versioned prompt templates and the workflow record in nonprofit-controlled storage. During the trial, export a sample and have the other fundraiser recreate one proposal brief. Record what is missing and how long recovery takes.
The consequence: if the test works, changing suppliers becomes a planned task. If it fails, the team can limit the tool to disposable drafting until it has a workable exit route. Neither choice requires predicting whether the vendor will survive.
What do vendor export documents actually tell you?
Read the documentation for the exact account and plan you intend to buy. As checked on 10 October 2026, OpenAI’s ChatGPT export guidance describes eligible account exports, with a ZIP containing chat history and other account data. It says self-service export is unavailable in Business, Enterprise and Healthcare workspaces; organisation-managed access needs a different route. Do not apply a personal-account feature to a managed workspace without checking.
OpenAI’s account-deletion guidance separately describes deletion within 30 days, with limited longer retention where law requires or permits it. Export, cancellation and deletion answer different questions. None of these documents establishes that a custom workflow will run on another vendor’s platform. That is what your practical test must establish.
Which other buying checks still matter?
Portability does not settle data handling, internal ownership or output review. Use Gate 3 to decide which data may enter the tool and Gate 4 to name the person who controls the work. Apply the Signature Test before an AI-assisted proposal or report leaves in your nonprofit’s name. These checks belong alongside the Export Test, without turning this article into another full procurement framework.
My view
I would treat exit effort as part of the purchase price. A cheap assistant can be useful, but the team should know what it would take to stop using it. The procurement question is concrete: can another person continue the essential work using records the nonprofit controls?
I would not reject every tool with imperfect portability. I would restrict the tasks entrusted to it until the dependency is understood and accepted. A temporary drafting aid and a central knowledge system need different levels of assurance.
What to do next
Choose one representative workflow before the trial ends. Export it, inspect the files, rebuild it outside the platform and record the missing steps. Give the vendor specific questions about those gaps, including plan restrictions, access after cancellation and extraction costs.
Set a repeat-test date and a named owner. Repeat when the tool gains a critical new use or the vendor changes terms. Keep the resulting exit record with the handover documentation, where a colleague can find it.
FAQ
What is the Export Test for an AI tool?
It is a practical trial of whether your nonprofit can retrieve important work and continue a representative task outside the vendor’s platform. Downloading files is only the first step; opening, understanding and reusing them completes the test.
Does a PDF export mean the tool is portable?
It may preserve a readable record, but it may not preserve editable data, instructions or workflow settings. Choose the format according to the task, then test reuse in another system.
Does having an API guarantee we can leave?
No. Check your plan’s access, extraction coverage, limits and costs. Test the records you actually need. An API that excludes important workflow settings does not solve that part of the exit problem.
Should a small nonprofit avoid every new AI vendor?
No. Use tools in proportion to the dependency you can manage. Keep source materials and workflow instructions under your control, and avoid making a tool essential before you have tested an exit route.
Sources
About the author
Milan Bogojevic works on practical AI adoption in nonprofits, with a focus on workflows, human accountability and organisational capability.
Last updated: 10 October 2026.