> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2026/new-import-export-feature.md).

# New Import/Export Feature

<figure><img src="https://2129322768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKJnzF2TwHA3APPbiCpF%2Fuploads%2F2XdC3zBfrdLME19sO8zg%2FForms_Better_Building.png?alt=media&amp;token=d1ef709e-1581-411d-b57b-35fc02a57132" alt=""><figcaption></figcaption></figure>

If you've used our Moisture, Daylight, or Carbon forms, you complete your recipe of inputs, run the simulation, get your report.&#x20;

It works, but it's always been a little one-sided. Your inputs lived only in your browser's memory, which is fine until you clear your cache, switch machines, or just want to hand your setup to someone else. Then you're stuck re-entering everything from scratch.

You can now export all the inputs from any of these forms straight to your local machine. That file is yours: reopen it, archive it, put it in version control, whatever makes sense for your workflow.

<figure><img src="https://2129322768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKJnzF2TwHA3APPbiCpF%2Fuploads%2FRgypzlNA1Ap0J4EonvX6%2Fimage.png?alt=media&amp;token=3bf3b24d-e52e-4a2e-91d5-d1794c89b1f0" alt=""><figcaption></figcaption></figure>

Once you have that export, you've got a few options. You can import it back into the same form later to pick up exactly where you left off. Or, if you're running into an issue and need our help, you can attach it directly to a support ticket. That means our team can see the exact recipe you used instead of trying to reconstruct it from a screenshot or a half-remembered description over email.

This is rolling out across the platform now, so expect it to show up in more forms over time, not just the three above. The goal is simple: your inputs shouldn't be trapped in a browser tab. They should be portable, so you always have access to them and we can actually help when something goes sideways.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2026/new-import-export-feature.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
