Skip to main content

Access your files before and after converting to Protocol V2

Keep usable file copies before self-service conversion and understand what is available afterward.

Written by Grigor

Before self-service conversion to Protocol V2, save usable copies of the files you want to keep. After conversion, files from the previous version do not carry over and cannot be accessed, including by Hivenet.

Before conversion

  1. Keep the mobile app signed in on a device where you can still access your old files.

  2. Open each file you want to keep and use the available download or sharing options to save a copy outside Hivenet. A file marked available offline only inside the app is not a separate copy.

  3. Wait for each download to finish, then open the saved copies and check their contents.

The current desktop apps and Store web app cannot retrieve those previous-version files for you. If mobile access or a download fails, contact Hivenet Support before converting. Keep the working app installed and signed in while you get help.

Record where the copies are saved. Complete the conversion checklist before signing out or continuing.

After confirmed self-service conversion

Upload the copies you saved if you want to use those files in Store again. Keep the separate copies until you have checked that the uploaded files can be downloaded and opened.

If you completed self-service conversion without saving a file, that previous-version file cannot be accessed afterward, including by Hivenet. Converting again will not bring it back.

If Hivenet is managing your migration

Follow the instructions for your account. If expected files are missing or unreadable, contact Hivenet Support. Do not start a separate self-service conversion to try to restore them.

If you are unsure what happened

Keep any working access and record the message you see, the account email, whether you started conversion yourself and whether any saved copy opens. Contact Hivenet Support before making another account change. See conversion troubleshooting.

Did this answer your question?