> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-2.1/upgrades-from-earlier-versions-maitred-2003-or-maitred-2005.md). # Upgrades from earlier versions (Maitre’D 2003 or Maitre’D 2005) If you are upgrading from an earlier version, you need to make sure that archives are migrated to the new version. The process of migrating archives is explained in the Maitre’D 7.08 migration documentation and will not be re-explained here. Please consult the appropriate documentation for more information. After all your Maitre’D archives have been migrated, many years’ worth of archives may need to be purged of credit card PANs and expiration dates. Maitre’D takes care of this process for you. It is entirely automated and requires absolutely no intervention on your part whatsoever. Depending on the number of archives to be stripped out of PANs and expiration dates, the entire process may take a few days to complete. The way this is done is that Maitre’D purges up to 30 archives during the end-of-day process, and resumes the purging process during the next end-of-day until all archives have been processed. The purging process was designed that way to create as little downtime as possible for end-users, and be totally transparent. Once the automated purge process is completed for all archives, the Maitre’D database will no longer contain any PAN or expiration date older than the current fiscal day. --- # 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.maitredpos.com/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-2.1/upgrades-from-earlier-versions-maitred-2003-or-maitred-2005.md?ask=&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.