> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/system-configuration/tools/import-maitred-2003-archives.md).

# Import Maitre'D 2003 Archives

Use this function to make 2003 archives usable in Maitre'D 2005 after upgrading from Maitre'D 2003. The 2003 archived checks and summaries, needed for some reports, are unreadable because of the modified Item structure.

{% hint style="info" %}
NOTE: Start this function during a quiet period of the day, because depending on the number of files, it could take some time.
{% endhint %}

**Archives**

Disable the Checks if you prefer to do these on separate days.

**Sum**

Disable the Summaries if you prefer to do these on separate days.

**With Trace**

Enable this option to display the conversion time taken for each archive file.

#### Import Maitre'D 2003 Archives with Item files <a href="#importmaitred2003archiveswithitemfiles" id="importmaitred2003archiveswithitemfiles"></a>

This function works like the former Import function above, but it also extracts from the last 31 accounting days archives the content of file 7 and 8, to get information such as the PLU, for example, for reporting purposes.


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/system-configuration/tools/import-maitred-2003-archives.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.