Data portability is a precondition of exit
Aliases: right to data portability · data export
What it is
Data portability: users can export their content, connections, and history in usable formats and import them elsewhere. It is the material precondition of exit freedom — without it, leaving means abandoning everything accumulated, and exit does not practically exist.
Why it happens
Portability determines the structure of switching costs. When export is unusable — proprietary formats, shattered fields, missing relationship data — accumulated value cannot move, and staying is the only rational choice; this is lock-in realized in the data dimension. Portability also disciplines incumbents: when moving is genuinely feasible, a service must retain users through continuing quality rather than abandonment costs. The boundary of portability must be faced squarely: it covers the user's own data. Collaborative artifacts (co-edited documents) and others' content (other people's posts) cannot move wholesale — social products are therefore only ever partially migratable, a structural ceiling rather than an implementation flaw.
Where it stops holding
The statutory right (the right to data portability under European data-protection law) covers personal data but not algorithmic relations — the recommendation model's portrait of you is not exportable, and that portrait is precisely the incumbent's advantage; legal portability therefore solves half the problem. Technical usability decides whether the right is realized: format openness, field completeness, delivery deadlines — "an export exists" and "the export is usable" are far apart. And because product structure keeps changing, export needs continuous maintenance, which is exactly why it is quietly abandoned first.
Applying it
Offer structured export covering content, relationship lists, and metadata (timestamps, interaction records) in open formats; export tracks the product — new features enter the export scope at launch, or their exclusion needs a stated reason. The import side supports one-click migration from major sources. Include export usability in release acceptance: the exported file must load in at least one third-party tool. Verification: have a new user migrate for real from a competitor, time it, and record the data-loss checklist — the lost items are the switching-cost list, to be worked down item by item.
Related
- Same group: P3.05.1 Mute, unsubscribe, and delete must be equally reachable · P3.05.3 Lock-in erodes freedom of choice
- Adjacent: P3.10.1 Exit costs include the loss of social ties · P3.10.4 Data processing that continues after exit
- Search terms:
data portability·right to data portability·switching cost