# Migrate from Flow Classic

## Import workflows from Flow Classic in Hub

You can import workflow archive files (.wap) or individual Flow files (.flow) from Flow Classic into an application package in Flow Connect.

### Import workflows

Start the import wizard available in the Application Library in Hub.

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

Select a file to import, and then select a destination application package.

<div align="left"><figure><img src="/files/8Fea0vkHu4ZBkyKypzWA" alt="" width="375"><figcaption></figcaption></figure></div>

Map connectors from the imported workflows to the connectors available in your organization. IFS OData connectors in Classic can be mapped to REST connectors in Connect.

<div align="left"><figure><img src="/files/oG7v0URyqbus5LOUWo3Y" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
Not all connectors in Classic can be mapped to a connector in Connect. Leave these unmapped and manage them manually after import.
{% endhint %}

For workflows using the IFS OData connector, a Map Projections step will be displayed. The import wizard will analyze all projections used in the workflows included in the file. Select the corresponding IFS OData module. Available modules with the same name as the projection will be automatically selected. Modules from the Application Library and the destination application package will be available.

<div align="left"><figure><img src="/files/WgW96BaXaPZkMVzQ4dvG" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="success" %}
If you want to generate missing modules before completing the wizard, copy the list of required projections by clicking the copy icon next to the IFS Projections header, and use them in the Batch Create IFS OData Modules application. When the modules are generated, refresh the available modules by clicking the refresh icon next to the FlowScript Modules header.
{% endhint %}

Confirm your import in the Import Overview step.

<div align="left"><figure><img src="/files/2iY1mLIX5MavJy1Yrqxt" alt="" width="375"><figcaption></figcaption></figure></div>

When the import wizard is complete, you can open the application package by clicking the link.

<div align="left"><figure><img src="/files/yKcopy3LgMH5mYmIhLu1" alt="" width="375"><figcaption></figcaption></figure></div>

Continue by [reviewing](#review-the-imported-applications-and-components) the imported applications and components.

## Import workflows from Flow Classic in Windows Designer

You can import workflow archive files (wap-files) from Flow Classic into an Application Package in Flow Connect.

### Export workflows

Begin by exporting your workflows, along with all dependencies, from Flow Classic.&#x20;

To do this, navigate to Flow Classic Studio. From the server content view, choose the folder containing the workflows you wish to export. Then, save the wap-file to your disk.

### Import workflows

The workflows contained within the archive will be imported into an existing package. You have the option to use an existing package or create a new one if needed.

Open the Flow Connect Designer and select **Import Archive** from the File menu.

<div align="left"><figure><img src="/files/YHe4Rwu3JCUPJns7ieT5" alt="" width="386"><figcaption></figcaption></figure></div>

&#x20;The import wizard is started:

1. Select file to import.
2. Choose Organization.
3. Choose destination Application Package.
4. Map the connectors used in the workflows to then ones you have in the organization.
5. Confirm the content preview.
6. Done.

### Review the imported applications and components

Open the package you selected during import. You should now see your imported applications and components. These items will initially be in an error state, requiring you to open and review them in the Designer.

#### Component references

If your application contains components, you need to make your first committed version of each component before they can be used by applications.

Locate your component and right click and select **Edit Component** to open.

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

Check the Problems tab to check for errors.

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

Typical errors might be that we are referencing a global Flow property that is not yet created in Connect or errors that wasn't possible to fix automatically in the new version of FlowScript.

When there are no errors left in the component, commit your first version.

#### Application

When components are committed, refresh the components in your application. Components will be refreshed and display the current version of the component.

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

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

Review and handle errors in the application. Dubbel click on the the error and the step will be highlighted.

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

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

Run your app in diagnostic mode to verify that it works .

&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.novacura.com/flow-connect/reference/migrate-from-flow-classic.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.