Tag: Portability

A ZIP file is not a migration plan.

Google Takeout is one of the better-known examples of a large platform giving users a way to export their information. Google says users can create archives containing data from products including Gmail, Drive, Calendar, Photos and YouTube.

That is useful. It is also easy to overstate what it means.

https://support.google.com/accounts/answer/3024190

Possession is the easy part

Takeout can give you files in formats such as JSON, CSV, ICS and other product-specific exports. The result is evidence that your information is not completely trapped inside Google’s interface.

But portability has two halves.

The first is getting the data out.

The second is having somewhere else that understands it.

Google’s own help page says a downloaded archive can be shared with another service through whatever upload or integration mechanism that third party provides. In other words, the receiving service decides what it can actually ingest.

That distinction matters.

An exported mailbox can be perfectly valid while the destination service cannot recreate labels, filters or account-specific behavior. A photo archive may contain the images you care about while related metadata arrives separately. A social or activity history can be readable by a human without being importable as a living account somewhere else.

The files survived. The system around them did not move.

Direct transfer only works where both sides cooperate

Google has also added direct data-transfer mechanisms for some third-party services and regions. Its current documentation is explicit that the receiving third party must choose to support the transfer and that availability varies by country, account and product.

https://support.google.com/accounts/answer/14452558

That is closer to genuine portability because the receiving service participates in the process.

It also exposes the real problem: portability cannot be created by the exporting platform alone.

If the destination does not understand the source format, relationships and metadata become folders full of evidence rather than a functioning replacement.

A backup can be excellent and still be a terrible exit

Data export is still valuable. If a company disappears, a Takeout archive can preserve mail, photographs, documents and years of personal records. That is far better than a locked account with no export at all.

But “Download your data” should not be confused with “Move to a competitor.”

A workable migration preserves enough structure that the user can resume the underlying task elsewhere without rebuilding everything manually. That can require compatible schemas, import tools, stable identifiers, relationship mapping and cooperation between services.

Without those pieces, the exit door technically opens.

It just leads to a loading dock covered in boxes.

You can export a phone number.

You cannot export the fact that twelve specific people are already in the family group chat and actively use it every day.

That is the portability gap between contacts and relationships.

A contact list is a set of identifiers.

A contact graph includes who follows whom, which groups exist, who belongs to them, who has blocked whom, which conversations are active, which memberships are mutual, and which people actually still use the service.

Those things are much harder to move.

Data portability does not automatically recreate a network

The European Union’s Digital Markets Act now requires designated gatekeepers to provide stronger portability tools for user-generated data. The Commission describes Article 6(9) as requiring free tools and continuous access so users can move data to authorized third parties. See the Commission’s end-user data portability guidance.

That is a significant improvement over a platform merely offering a giant archive download.

But even a perfect export cannot force the people in the file to create accounts somewhere else.

A social graph is partly data and partly coordinated human behavior.

Messaging interoperability shows another approach

The DMA treats messaging differently because strong network effects make migration unusually difficult. Instead of requiring every user to move, Article 7 requires certain gatekeeper messaging services to interoperate with other providers.

The European Commission says the first third-party messaging services interoperable with WhatsApp launched in November 2025. The rules are being phased in across one-to-one messaging, group chats, and eventually calls. See the Commission’s messaging interoperability page.

That is conceptually important.

If two services can communicate, a user can leave one interface without necessarily abandoning everyone still using it.

The solution attacks the network lock-in directly.

Exportable is not the same as portable

A platform can truthfully say:

You can download your data.

That may still leave the user with:

a CSV of contacts who are not on the new service,
old messages with no live destination,
groups that must be rebuilt manually,
followers who must choose to follow again,
community roles that do not transfer,
and years of relationships represented only as static records.

The file moved.

The network did not.

That distinction matters whenever a dominant platform points to an export tool as proof that users are free to leave.

Freedom to leave is not measured only by whether a button produces a ZIP archive.

It is measured by how much useful social structure survives the trip.