Getting ALL your data out of Google Reader
There remain only a few days until Google Reader shuts down. Besides the emotions1 and the practicalities of finding a replacement2, I've also been pondering the data loss aspects. As a bit of a digital pack rat, the idea of not being able …
Context & Ripple Effects
Google Reader had become a destination for users displaced by earlier reader closures, including the 2008 Bloglines-to-Reader migration. Its own shutdown turns that migration pattern into a data-retention problem rather than simply a search for another interface.
The replacement market was already moving quickly: more than 500,000 users moved to Feedly in two days. Coverage also connected Reader's closure to privacy and compliance concerns, making control over exported data part of the service-transition debate.
First-order effects
- Google Reader users who export their data before the shutdown retain a usable copy; those who do not lose access to data held inside the service.
- Google Reader’s closure forces remaining users to pair a replacement reader with a separate archive of their accumulated data.
Second-order effects
- Feedly and other replacement readers face pressure to make importing and preserving Google Reader data simple, as migration friction becomes a competitive differentiator.
- Publishers and RSS services gain another reminder that reader migrations can shift audiences abruptly when a central aggregation service closes.
Third-order effects
- If users treat reader shutdowns as archival risks, RSS tools will compete less on a single hosted destination and more on portable libraries that can move between services.
- The closure reinforces a broader shift from trusting long-lived web services by default toward maintaining exportable personal archives.
The trend: Consumer web services are becoming judged not only by their interfaces, but by whether users can carry their accumulated data across shutdowns and replacements.