The 30-Day Rule: Why We Write the Divorce Papers First
If we cannot migrate our data out in 30 days, we do not own it. Here is the mandatory exit clause every municipal contract needs.
The Pre-Nuptial Requirement
The Account Executive leaned forward, his cufflinks catching the light. “We are looking at a five-year partnership,” he said smoothly. “Our platform becomes the operating system for your social services.”
“Five years is a long time in politics,” I replied. “Governments change. Budgets change. Strategies change. What happens if we need to leave in Year Two?”
He waved a hand dismissively. “We can discuss termination for cause, of course…”
“I am not talking about cause,” I interrupted. “I am talking about autonomy. Show me the ‘Export All’ button. Show me the schema. If I cannot move my Citizens’ records to a competitor next month, I am not buying a tool. I am buying a cage.”
The Trap: Convenience is the Bars of the Cell
The most dangerous phase of any software implementation is the beginning. The vendor makes it incredibly easy to ingest data. They offer “concierge migration services” for free. They want your data inside their walls.
Once the data is in, the trap snaps shut. We see this constantly:
- Proprietary Formats: The data is stored in a way that only their software can read.
- The “API Limit”: When you try to export, they throttle the speed so it takes years to download your own history.
- The Consulting Wall: They claim that extracting the data requires “custom engineering work” at €300 per hour.
This is not a technical limitation. It is a blockade. It is a deliberate strategy to degrade our sovereignty by making the cost of independence higher than the cost of submission.
[Image of an hourglass with “Vendor Contract” written on it, where the sand turns into dollar signs at the bottom]
The Exit Strategy: The 30-Day Sovereignty Clause
We have a standard rider attached to every RFP. It is non-negotiable. If the legal department of the vendor redlines it, we disqualify the vendor.
The Clause:
“Upon termination for any reason, the Vendor guarantees the availability of a complete, machine-readable export of all Municipal data (including metadata and file attachments) within 30 calendar days. This export shall be in a documented, open standard format (JSON, SQL, CSV). Failure to provide this export constitutes a material breach and voids all final payments.”
We test this. During the pilot phase, we do not test the features; we test the exit. We load dummy data and measure how long it takes to get it out.
If the vendor says, “We don’t have an automated export feature yet, it’s on the roadmap,” we politely end the meeting. A roadmap is a promise. An export button is a fact. We serve the Public with facts.
FAQs
Is 30 days realistic for a massive database?
Technically, yes. Bureaucratically, it is tight. But we set the deadline to force the vendor to automate the export, rather than relying on manual labor.
What if the vendor charges for the exit?
We define the cost in the initial contract. It must be 'at cost,' not punitive. A penalty for leaving is a sanction, and we do not accept sanctions.
Why not just use PDF exports?
A PDF is a picture of data, not data itself. You cannot run queries on a picture. We demand JSON, CSV, or SQL.