> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/calculation-modules/loads-forces/project-load-group-builder/migrating-data-to-a-new-instal.md).

# Migrating data to a new installation

How to transfer Project Load Group Builder custom load data to a new ENERCALC SEL installation.

## How do I transfer my custom load data in Project Load Group Builder when I set up ENERCALC SEL on a new computer?

Your custom load items are your **User Defined** library, stored in a file named `LoadDbase.TPS`. The **ENERCALC Supplied** library ships with the program, so it doesn't need to be moved.

To find the file, open the Project Load Group Builder and check the **Usage Steps** panel, which lists the exact path to the User Defined `LoadDbase.TPS` (typically `…\Documents\ENERCALC Data Files\`). Copy that file to the same location on the new installation. You can also select **Settings > File Locations** to see the first path, which is the default location for your project files and several per-module data files.


---

# 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://enercalc.com/docs/sel-faq/using-the-software/calculation-modules/loads-forces/project-load-group-builder/migrating-data-to-a-new-instal.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.
