Skip to main content

Tusky Migration Guide

As of December 19, 2025, the storage service Tusky is shutting down. Data stored on Walrus through Tusky is still safe and accessible. During Tusky's sunsetting period, you can continue reading your data, however you must either migrate to using Walrus directly or through alternative tooling.

During this sunset period, you must:

  1. Take note of the Tusky sunsetting window.

  2. Request your encryption keys from Tusky if you use the password protected keys stored by them.

  3. Begin downloading your datasets. Refer to the Tusky documentation for more information or view the video tutorial.

  4. Decide which migration option fits your use case best.

  5. Complete re-upload where required.

  6. Validate reads and access patterns on Walrus.

  7. Update applications or workflows as needed.

Immediate first steps​

  1. Take note of the sunset window.

    • You have at least 30 days (until January 19, 2025) of guaranteed read access via Tusky from the date of their shut down announcement.
    • Do not wait until the last week of this 30 day window.

  2. Take inventory of your data. Having an inventory of your data will help determine which migration option fits best.

  3. Request your encryption keys from Tusky now if you use the password protected keys they store.

Important note on encryption (applies to all migration options)​

Tusky supports self-hosted keys and keys supplied by the user but stored on Tusky and password protected. They implement server-side encryption and decryption of blobs with those keys, which means that a user or app client does not need to do the actual encryption or decryption on their end.

This means once you download your data from Tusky, it should already be decrypted.

Based on your needs for data management going forward, you can choose to encrypt your data using an alternative mechanism as mentioned in the migration options. If you request the Tusky-stored encryption keys from them before they shut down the service, you may choose to reuse those keys with the relevant alternatives.

Migration option 1: Download from Tusky → decrypt → re-upload to Walrus​

  1. Download your data from Tusky
  1. Set up a Walrus client
  1. Re-upload to Walrus

Migration option 2: Direct Walrus access through blob or quilt patch IDs​

  1. Extract blob or patch IDs and metadata from Tusky (through their app, API, or SDK).

  2. Fetch blobs or quilt patches directly from Walrus using:

  1. Validate integrity and availability of the data.
  • You might have to decrypt your data using encryption keys that you have retrieved from Tusky. Make sure you request these before their service is shut down.
  1. Update your application or workflows to reference Walrus directly going forward.

Migration option 3: Migrate to another Walrus-compatible interface (Managed UX)​

Available options:

tip

More managed UX options coming soon.

  1. Export data from Tusky
  • Use the Tusky app, API, or SDK to download all required data.
  • Evaluate and choose one of the options listed above.
  • Based on your needs, confirm support for:
    • Bulk uploads
    • Large files
    • Encryption
    • Long-term maintenance and support
  1. Re-upload data
  • Upload data through the new interface (relevant UI, API, or SDK).
  • Re-apply encryption and access controls as needed.
  1. Validate access and workflows
  • Confirm reads, permissions, and any application integrations.