> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/reference/migrate-from-flow-classic/portal-migrate-from-flow-classic.md).

# Portal - migrate from Flow Classic

The migration process for Portal 2 customers is as follows:

1. **Migration Source**: Migration will work from the latest version of Portal 2.
2. **Data Sources and Workflows**: Data sources and workflows are migrated to Connect using the “normal” workflow migration process. \
   \
   During the portal page import step, the system will attempt to map workflows to components with the same name, so it can be helpful to maintain the same naming structure as in Flow Classic.\
   \
   **Note**: The database as a data source has been removed in Portal Connect. For portlets using this type of data source, components must be created. This is currently a manual process.
3. **Export Pages from Portal 2**: 

   \
   Open the **Configuration panel** and go to the **Navigation tab**. Click the **Export** button and select the pages to export and click **Export**.\
   \
   **Note**: In Portal Connect, access is set at the application package level. All portal pages will be imported into a package. It is important to consider the application package structure before exporting so that the export aligns with the import in manageable chunks.
4. **Import Process**:
   * Go to **Add New** and select **Import** to start the Import Wizard.
   * Select the package into which the pages are to be imported.
   * Add the file that is to be imported.
   * Map components and apps as required.
   * Click **Import**.

<figure><img src="/files/qgnWZr2fULGEjd5kNOlE" alt=""><figcaption></figcaption></figure>


---

# 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.novacura.com/flow-connect/reference/migrate-from-flow-classic/portal-migrate-from-flow-classic.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.