Integrations, exports and APIs
Exports and data portability
What leaves the app.
Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made
C0591 Can I export data from ET?
There is a package export tool on the rail, but we have not documented its output or format, so we cannot promise what you get.
C0592 Can I export my saved desk?
Project locks are stored locally. Whether the file can be copied to another machine has not been tested.
C0593 If I export something, does it keep its labels?
It should. The labels such as Opinion EstimateWhat this label means A maker’s own figure, non-binding and for planning only. It is labelled maker-reported, is not verified by ET, and is not a quote or an offer to sell. A hard figure appears only if the maker opts in. ET invents no prices. Glossary entry for this label and US-noted are part of how figures are presented, and exported figures should be treated with the same label. We have not verified how exports preserve them.
C0594 Do I need to credit sources in an export?
Yes, per each source's terms. See sources and attribution, and do not remove credit from pictures or data.
C0595 Can I take my data with me if I stop using ET?
Yes in the sense that desk state is on your own computer. There is no ET account data to export, since ET holds no account.
C0596 How do I back up my desk?
Copy the relevant local files under your own backup routine. We have not documented the file locations beyond the local application-data folder.
C0597 Is there an import feature?
None is documented. You cannot load your own data into the graph or layers as a stated feature.
C0598 Can I bring my own overlays?
Not as a documented feature. Overlay packs are built by the project from named sources.
C0599 Are exports allowed for commercial use?
Not automatically. Every source has its own licence, several are unreviewed, and some carry share-alike. You must check the source before reuse.