> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/10.2-admin/troubleshooting-overview-cp/pentaho-repository-issues/importing-and-exporting-8.0-and-earlier.md).

# Importing and exporting PDI content with Pentaho 8.0 and earlier

When you export the contents of the repository from Pentaho version 8.0 or earlier and import them into a later version, an error occurs. This error may occur because you are attempting to export/import the entire repository, which may include items from repository locations that have restricted access in later versions of Pentaho.

Here's how you can resolve this error: To import or export PDI content that was created in Pentaho 8.0 or earlier, select specific content and not the entire repository. If you are working with multiple selections, export each one separately.

Also note that you do not need to export your Ops Mart content because it is automatically included and updated for each new version of Pentaho.


---

# 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.pentaho.com/pdia-admin/10.2-admin/troubleshooting-overview-cp/pentaho-repository-issues/importing-and-exporting-8.0-and-earlier.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.