The restore can retrieve files, however, it is unluckily that the folder structure will be lost. Why Lucid does not try to keep the structure, which seems not too difficult. Losing structure is really awful.

@pneo Thank you for commenting and for your feedback regarding our backup and restore feature. If you would like to see this implemented, would you mind posting your feedback in the Product Feedback section of the Community?

For more information on how to share your ideas with the community, please review our 'Feedback and Feature Request’ community article.

We are continually exploring ways to enhance our products, and your input is the most effective means to achieve that goal. We greatly appreciate your feedback.

cc: ​@pneo 

Hi Everyone!
Thanks to feedback from users, we've made an important improvement to our backup and restore functionality.

What's changed: Starting with new backups created moving forward, your folder structure will now be preserved when you restore your documents. This means you won't lose your organizational system during the restore process.

Important note: This improvement applies to backups created after this update. Existing backups will still restore documents to the root level, but any new backups you create will maintain your folder organization.

We really appreciate everyone who took the time to share their experience with this pain point. Your feedback directly contributed to making this improvement happen!

I think you need to really look at this capability, you are using a proprietary format “LAF” files, ironic as my first response to trying to import a 400MB large backup was you are having a laugh. You struggle to handle files > 100MB yet you don’t chunk the backups and then use a common format like zip to aggregate them together. You simply chunk them when the upload fails, then every time it fails you just try and chunk again even when the chunks are ~ 40-50MB. 
Think of this from a customer perspective, you export the data from an employee, you then want to import that to another user, if there is no direct handover (think the new user doesn’t exist prior to exit). Then you have an asynchronous process of backup and restore, but you use a proprietary format, so you can only rely on the tools provided.
Now when those tools offer nothing in the way of real error messages, but partly import and you attempt multiple times you end up in a very messy folder mechanism where you cannot trust anything that you have done.
I am not sure what you would consider a normal user experience, but after wasting half a day trying to recover a set of files, I am leaning back to using Draw.io. It is open, exportable, I can back it up and restore using standard tools. You will never truly replace Visio, Draw.io until you provide a better user experience and no vendor lock-in.

Hi ​@SPC,

Thank you for your response!

This has been escalated to our Research and Development team, and we are actively exploring a better solution. I will update this thread as soon as I hear more from our team. Thank you for your patience.