Writing data export rights into an event platform contract
Data export rights are the contractual terms that decide what you can take out of an event platform, in what format, how often, and for how long after termination. Privacy law covers personal data supplied by the individual and leaves booth history, priority points and derived scores entirely to the contract.
The renewal paperwork for the registration platform arrives with three weeks to signature, and somebody asks whether we can get our data out if we ever leave. The account manager says yes, of course, there is an export button. Everyone relaxes.
Data export rights are what that button turns into when the relationship stops being friendly, and the gap between the two is where a portfolio's history goes missing. The button exports registrations. It does not export the twelve years of booth positions, the priority points that decide who picks first next year, or the identifiers that let you match a 2021 attendee to a 2026 one.
What the law actually gives you
Less than the phrase "data portability" suggests, and it is worth being precise because the misunderstanding is near universal.
Article 20 of the General Data Protection Regulation gives the data subject the right to receive their personal data in a structured, commonly used and machine readable format, and to transmit it to another controller without hindrance (EU, 2016). Two conditions attach. The processing has to rest on consent under Article 6(1)(a) or Article 9(2)(a), or on a contract under Article 6(1)(b), and it has to be carried out by automated means. Where technically feasible, the person can ask for direct transmission from one controller to another.
Read that as an attendee's right against you, because that is what it is. It gives you nothing to hold against your platform vendor, and it reaches personal data only. The commercial record of a show sits outside it.
The EU Data Act, Regulation (EU) 2023/2854, gets closer to the problem. It entered into force in January 2024 and applies from 12 September 2025, and its Chapter VI addresses switching between data processing services. Article 25 sets contractual terms for switching, including a maximum notice period for initiating the process of no more than two months and a mandatory maximum transitional period of 30 calendar days for the switch itself (EU, 2023). Article 13 provides that a contractual term unilaterally imposed on an enterprise that is unfair is not binding on that enterprise.
That is real bargaining power, and it still will not hand you your booth history, because the obligations attach to data processing services and to exportable data as the regulation defines it. Whether your exhibitor portal counts, and whether a decade of floor plans counts as exportable data, is exactly the sort of question that gets answered in a negotiation rather than in a statute.
What you actually need, counted
Stop saying "our data" and count the objects. This is the single change that makes the negotiation tractable.
A mid sized portfolio's registration and exhibitor stack holds something like eleven objects worth naming: person records, registration transactions, registration answers to custom questions, badge scans, session attendance, exhibitor accounts, contracts, booth assignments by edition, priority points, invoices, and the audit log of changes. For each one, write down the row count for a recent edition and the key you would need to join it to the others.
Now check what the vendor's standard export covers. In my experience it will be four of the eleven, typically person, registration, exhibitor account and invoice, because those are the objects finance asked about. The other seven, which include everything that makes next year's floor plan possible, come out only if you ask for them by name. Getting four of eleven is 36 per cent of the objects and considerably less than 36 per cent of the value.
The audit log is the one worth fighting hardest for and the one most often refused. Without it you cannot answer who changed a booth assignment or when a registration was cancelled, and after a migration those questions become unanswerable forever.
How do you specify a format that will still work in three years?
Name the format, the encoding and the delimiter, and require a schema document alongside the files.
CSV in UTF-8 is a reasonable default and it needs three qualifications to be useful: how a field containing the delimiter is quoted, how a line break inside a free text answer is represented, and how nulls are distinguished from empty strings. Those three ambiguities account for most of the pain in reading an export you did not generate. Newline delimited JSON avoids all three and is worth asking for where the vendor supports it.
Require the schema as a separate file rather than as a header row, because a header row tells you a column exists and nothing about its type, its allowed values, or whether it is the same column it was last quarter. A vendor who cannot produce a field list with types has told you something useful about how the export is generated.
Ask for identifiers to be included even where they look internal. The vendor's own record id, the edition id, and any parent references are what let you rebuild relationships on the other side. An export with names and no keys is a report.
What should the post termination window be?
Ninety days is the number I would open with, and the argument for it is operational rather than legal.
When a platform relationship ends, the export happens during the busiest and least organised month your team will have. Somebody is standing up the replacement, somebody else is running a show, and the person who knew which fields mattered has usually already moved to the new project. A window that closes on the termination date guarantees the export gets taken in a hurry and checked by nobody.
Ninety days lets you take the export, load it, discover the three columns that came through empty, and go back once. Ask for that second request explicitly, because a clause granting one export is a clause granting one chance to get it right.
Two related terms are worth the same sentence in the contract. What happens to the data during a payment dispute, since a suspended account with a locked export is the strongest hold a vendor has. And how long the vendor retains your data after termination, which is a deletion question, and pulls in the opposite direction from everything else here.
Frequency, and why self service beats a ticket
An annual export right is close to worthless. It tells you the data can leave in principle and gives you no practice at receiving it.
Ask for a scheduled export you can trigger yourself, at least monthly, delivered to storage you control. The reason is not the data, which you can mostly get through the API anyway. The reason is that a monthly export exercises the path, so the day you actually need it you already know the file layout, the row counts and the failure modes. A right you have never used is a right you will discover is broken at the worst moment.
Specify the latency too. "Within five working days of request" is a normal ask and it converts an open ended obligation into something you can hold someone to. Pair it with the question of how far back the export reaches, which is a different limit entirely and is covered in finding the API history limits. A vendor can honour a perfect export clause and still hand you two years when you asked for five.
Pricing the clause before you argue for it
Procurement will ask what this is worth, and a number helps.
Take the rebuild cost. If leaving without booth history means recreating priority points by hand from twelve years of floor plans, estimate the hours. Say 40 shows worth of exhibitor lineage at half a day each, so 20 days of somebody's time, plus the errors that survive. That is the figure the export clause is buying down, and it is far larger than any discount you would win by trading the clause away.
The other half of the pricing conversation is timing. Export rights are cheap to obtain at first signature, more expensive at renewal, and unobtainable at termination. If your platform contracts are up for renewal in the next year, that is the window, and the rehearsal that proves the clause works belongs with testing for vendor lock in before the renewal rather than after it.
Where this stops
A contract clause is a promise about behaviour, and a promise cannot manufacture data the platform never stored.
If the system overwrites a booth assignment rather than versioning it, no export clause recovers the previous value, because there is no previous value to export. If custom question responses are stored as free text with no code, the export is faithful and still requires the same cleaning work you would have done anyway. Ask what is stored before you argue about what is exported. The vendor's own documented export is usually the fastest way to find out what the underlying model holds.
The second limit is enforcement. A clause you have to litigate is a clause you do not have, especially against a vendor whose commercial relationship with you continues across other shows in the portfolio. Prefer terms that are self executing, like a scheduled export to your own storage, over terms that require the vendor to do something on request.
This week, list the objects you would need to rebuild next year's floor plan and priority order, then open your current contract and see how many of them are named in it. The count of objects that appear nowhere is your negotiating list.
Questions people ask about data export rights
- Does GDPR give an organiser the right to export event data?
- Not in the way organisers assume. Article 20 gives the data subject, meaning the individual, a right to receive their personal data in a structured, commonly used and machine readable format, and only where processing rests on consent or contract and is carried out by automated means. The right belongs to your attendees and gives you nothing to hold against your platform vendor.
- What does the EU Data Act change for event platform contracts?
- Regulation (EU) 2023/2854 applies from 12 September 2025 and addresses switching between data processing services. Article 25 requires contractual terms including a notice period for initiating switching of no more than two months and a mandatory maximum transitional period of 30 calendar days. Article 13 provides that unfair contractual terms unilaterally imposed on an enterprise are not binding.
- What should an export clause actually specify?
- Five things: the scope by named object rather than by the word data, the file format and character encoding, the frequency and whether it is self service, the maximum latency between requesting and receiving, and how long after termination you can still request one. A clause missing the last item leaves you negotiating in the month when you have least bargaining power.
Related reading
- How to plan a Cvent data export you can actually reuse
- Finding the API history limits in your event systems before a five year backfill
- Testing for vendor lock in before you renew an event platform