> 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/install/9.3-install/pentaho-upgrade-cp/before-you-begin-pentaho-upgrade.md).

# Before you begin

Before you can run the Pentaho Upgrade Installer, you must also perform the following tasks:

1. Verify that your system components are current.

   Your system components, such as web browsers or repository databases, must be up-to-date. See the [Components Reference](/install/9.3-install/components-reference.md) to verify the system requirements.

   **Note:** The Pentaho Upgrade Installer requires 22 GB of free space to perform the upgrade process.
2. If you are upgrading an environment that includes the Pentaho Server, stop the server prior to performing backups and installation.

   For instructions, see [Start and stop the Pentaho Server for configuration](/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/start-and-stop-the-pentaho-server-for-configuration.md).
3. Review your customizations.

   During the upgrade process, you can help the upgrade installer specify which items contain your customizations. See [Specify customized items to address after upgrading](https://github.com/pentaho/documentation/blob/main/PDIA/9.3/Install/Pentaho%20upgrade/Pentaho%20upgrade%20\(cp\)/Using%20the%20Pentaho%20Upgrade%20Installer%20\(Pentaho%20upgrade\)/Specify%20items%20to%20include%20or%20exclude%20\(Pentaho%20upgrade\)=GUID-F2CC89CE-AD4A-416E-B7FF-3D9F0B74828C=4=en=.md) for details. Then, after upgrading your Pentaho products to 9.3, you can merge your previous customizations into post-upgrade versions of the Pentaho files. See the [Apply customizations](/install/9.3-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp/apply-customizations-post-upgrade-tasks.md) post-upgrade task for instructions.
4. If you are using Hadoop clusters with your Pentaho products, review and back up your `site.xml` files.

   The upgrade process does not retain the drivers for your Hadoop clusters. You will need to re-install your drivers after completing the upgrade process. See the [Install drivers for your Hadoop clusters](/install/9.3-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp/install-drivers-for-your-hadoop-clusters-post-upgrade-tasks.md) post-upgrade task for details.
5. If you are using plugins with your Pentaho products, review and back up your plugins to a separate directory structure.

   The upgrade process does not retain your plugins. You will need to re-apply your plugins after completing the upgrade process. See the [Apply your plugins](/install/9.3-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp/apply-your-plugins-post-upgrade-tasks.md) post-upgrade task for details.
6. If you are upgrading the Pentaho Server, verify that no users are logged on to the server.

   As a best practice, perform the upgrade process of the Pentaho Server during off-business hours to minimize the impact to your day-to-day operations.

You should review previous release notes, along with the [Components Reference](/install/9.3-install/components-reference.md), to understand how our products have changed since those previous releases.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/9.3-install/pentaho-upgrade-cp/before-you-begin-pentaho-upgrade.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.