> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/installation-and-upgrade/faq/moving-sqlite-portal-database.md).

# Moving SQLite portal database

If the portal database is located in the wrong directory will an upgrade not be possible.

To fix this:

1. Locate the Portal database, go to the portal web.config and see tag datapath for the location.
2. Open the Flow server tool and find the data storage for the installation to upgrade; click on the meny for the installation and take Open storage.
3. Copy the Portal database to the installation location.
4. Navigate to the portal web.config and change the datapath to the new data path and save the web.config.

*Contact product support if above does not work for you*


---

# 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://help.novacuraflow.com/6.12/installation-and-upgrade/faq/moving-sqlite-portal-database.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.