> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting/11.6-drill-string-editor/11.6.4-drill-string-editor-menu-ribbon/11.6.4.8-import-export.md).

# 11.6.4.8 - Import/Export

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5aMFPVuB6VD0Hkyga2dA%2Fimage.png?alt=media&amp;token=f32d2a97-154f-46ab-a2f0-9b1c72d6be76" alt=""><figcaption></figcaption></figure>

**Import BHA:** Allows the user to import BHA’s exported from the Drill String Editor in Well Seeker. Using this function will cause a dialog box to appear asking the user to open the desired **.mdb** export file. Once the file is selected the Import/Export window will open allowing the user to select the desired BHAs to be imported. Once selected, the BHA’s will be added on to the end of the current list of BHAs in the Drill String Editor.

**Export BHA:** Opens the Import/Export window, allowing the user to select which BHAs they want to export. The exported BHAs will be exported as a **.mdb** file.

**Import Eng BHA:** Imports a BHA exported from the Innova Engineering software package. Note that this will overwrite the currently selected BHA.

**Export Eng BHA:** Exports the currently selected BHA in a **.bha** format, allowing the BHA to be imported into the Innova Engineering software package.


---

# 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.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting/11.6-drill-string-editor/11.6.4-drill-string-editor-menu-ribbon/11.6.4.8-import-export.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.
