Your Data Has an Exit Door, or It Doesn't

I have sat through a lot of software demonstrations in my career. Nobody ever asks about the exit door during the demo. Everyone is looking at the dashboard, the mobile app, the reporting screen. Nobody asks what happens the day the department decides to leave.

That is the wrong order. The exit question belongs in procurement, before a signature, not in a support ticket five years later when a new chief wants a different platform and discovers the roster, the certifications, the incident history and the training records do not come out in any usable form.

Data ownership and portability are not IT details. They are contract terms, and they deserve the same scrutiny departments already give to price and features.

Who Actually Owns the Data

Ask the vendor directly, in writing: who owns the data the department enters into this system. The answer should be simple. The department owns its own data. The vendor owns the software.

Most contracts say this somewhere, usually in language nobody reads closely. The real test is not what the ownership clause says. It is what the export function actually does. A department can own its data on paper and still be unable to get it out in any form a human being can use.

I have seen this cut both ways. A vendor can be completely sincere about respecting data ownership and still built a system where full export was never a design priority, because no customer asked for it during the sales process. Ownership without a working export path is a promise, not a capability.

Ask for the Export Before You Need It

Do not wait until a renewal dispute or a platform migration to test the export function. Ask for a sample export during the evaluation, before the contract is signed. Then have someone who actually understands the data open the file and try to use it.

Look at what comes out and what does not. Does the export include historical records or only current status? Does it preserve relationships between records, like which certifications belong to which member, or does it flatten everything into a list that needs to be manually reassembled? Are attachments included, like scanned certificates or photos, or does the export leave you with a spreadsheet of filenames pointing at files you no longer have access to?

A vendor that welcomes this question and can produce a clean, usable export on request is telling you something. A vendor that treats the request as unusual, or that can only produce a technical data dump meant for a database administrator rather than a department, is also telling you something.

Format Matters as Much as Access

Getting the data is only half the question. Getting it in a format anyone can actually use is the other half.

A proprietary format that only the vendor's own software can open is not portability. It is the same lock-in with an extra step. Ask specifically for open, standard formats: CSV, JSON, PDF for documents, formats that another system, or a plain spreadsheet, can read without translation software the department does not own.

This matters even if the department never intends to leave. Formats change. Companies get acquired. Products get sunset. A department that can only read its own historical records through one vendor's proprietary viewer has traded convenience today for dependency it may not have chosen deliberately.

What Happens at Contract End

Read the termination section of the contract as carefully as the pricing section. It should answer specific questions.

How long after termination does the department retain access to export its data? Thirty days is common and often too short for a department that has not planned ahead. What happens to the data after that window closes: is it deleted, and on what schedule? Does the vendor charge a fee for data export at termination, and if so, is that fee disclosed now or discovered later? Is there a difference in export rights between a department that cancels voluntarily and one whose contract is not renewed by the vendor?

Departments that skip this section during procurement are the same departments that call me later asking whether anything can be done about a vendor that wants a fee to hand back records the department already owns. Sometimes something can be done. Often it cannot, because the contract already answered the question, just not in the department's favor, and nobody read it that way at the time.

Format Lock-In Is a Slower Version of the Same Problem

Contract lock-in is obvious. A multi-year term with automatic renewal and a narrow cancellation window is easy to spot if anyone looks.

Format lock-in is quieter and can outlast the contract itself. A department can technically be free to leave a vendor and still be functionally stuck, because five years of incident history only displays correctly inside that vendor's interface, or because certification records were stored as scanned images with no underlying structured data connecting them to members and dates.

This is why the export test during evaluation matters so much. It is the only way to find out whether the department's own history will still mean something once it is outside the system that created it.

This Is a Procurement Question, Not an Afterthought

Every one of these questions belongs on the same evaluation checklist as security certifications, pricing tiers and feature comparisons. They do not belong in a follow-up email after the contract is signed, and they should never be left to whoever happens to be the department's IT contact at the time.

Assign someone the job of asking these questions during procurement, the same way someone is assigned to negotiate price. Put the answers in writing, and put the specific commitments, export format, retention window after termination, any associated fees, into the contract itself rather than trusting a sales conversation to still be accurate three years from now.

Vendors change ownership. Sales representatives move on. Verbal assurances about being reasonable at renewal time do not survive an acquisition. The contract is what remains.

A Good Vendor Should Welcome This Conversation

None of this is an accusation against vendors as a category. Plenty of companies in public safety technology built genuinely portable systems because they understood that customers who feel trapped are customers looking for a reason to leave, and customers who trust they can leave are the ones who stay.

A vendor confident in the value of its product should have no discomfort walking a prospective customer through the export process, showing exactly what a full data export looks like, and putting reasonable export rights in writing. If a vendor becomes evasive, vague or defensive when asked these specific questions, that reaction is itself useful information, delivered for free, before any money changes hands.

Ask the Question While You Still Have Leverage

The department has the most leverage over these terms on the day before it signs the contract and almost none the day after it wants to leave.

Ask who owns the data. Ask for a real export and have someone competent review it. Ask about format. Read the termination section like it matters, because it does. Get the specific commitments in writing rather than trusting the relationship to stay friendly forever.

Every system your department will ever use has an exit door somewhere. Find out now whether it actually opens.