Backups
Your work lives on this device. Some of it is easy to reproduce and some of it is not, and the difference is worth knowing before you need to know it.
Worth keeping a copy of
| Why | How today | |
|---|---|---|
| Parameter tables | The intent behind a family of parts | Export in Parameters — .csv or .json |
| Posted programs | Reproducible from the design, but not free | Keep the source files in cloud storage |
| Designs | Hours of modelling that exist nowhere else | No export yet — see the note below |
| Tool libraries | Your own entries; vendor catalogs re-import easily | No export yet — vendor tools come back through Import Library |

Not worth worrying about
Machine profiles are quick to recreate through the setup wizard, and the machine's own settings live in the controller rather than here.
Job history is a record of what happened, not something you build on.
The habit that costs nothing
Work from cloud storage where you can. Programs imported from Drive or Dropbox already exist somewhere other than this device, which is what a backup is.