# Import / Export Microflow

The **Microflow Designer (MFD)** allows Microflows to be **exported from one application** and **imported into another application or environment**.\
This capability enables teams to **reuse integration logic**, promote consistency across projects, and migrate Microflows between environments (such as Development, SIT, and Production).

Microflows can be:

* Shared across applications
* Migrated across environments
* Reused without redesigning logic from scratch

***

### Export Microflow

Microflows can be exported from an application via the **Project Overview** screen.

#### Access Export Option

1. Open **Microflow Designer**
2. Navigate to the **Project Overview** screen
3. Click the **Export** option

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FqUTxwihXpwa54o9yU0XN%2Fimage.png?alt=media&#x26;token=4db073d5-b3e1-460a-9e78-b6cecdc3fc1b" alt=""><figcaption></figcaption></figure>

***

#### Export Options

When exporting Microflows, users are presented with **three export modes**:

| Export Option    | Purpose                                                         |
| ---------------- | --------------------------------------------------------------- |
| **Config**       | Export Microflow configuration for reuse in another application |
| **Embedded**     | Export Microflow as a JAR for runtime usage (Embedded Mode)     |
| **MicroService** | Export Microflow as a service for Standalone Server mode        |

Users can select **one or more Microflows** to export in a single operation.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FND72WAczi5Qbp0mN5HkD%2Fimage.png?alt=media&#x26;token=f1d41f3b-ba69-43a2-8285-1b20f2bef15c" alt=""><figcaption></figcaption></figure>

***

#### Exporting Configuration (Config Option)

When **Config** is selected, two export variants are available:

1. **Export only configuration**
2. **Export configuration with attached artifacts**

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2F0SruaAiXV7a9ZFPSd8tn%2Fimage.png?alt=media&#x26;token=20aef9e1-8f6f-40ec-9126-38219a8d78d8" alt=""><figcaption></figcaption></figure>

**Export Variants Explained**

* **Only Config**
  * Exports:
    * Microflow definition
    * Business Objects
  * Does NOT include:
    * Java JARs
    * WSDL / XSD files
* **With File**
  * Exports Microflow configuration
  * Includes attached artifacts, such as:
    * Java node JAR files
    * Web Service WSDL/XSD files

The exported package is saved locally and contains:

* Microflow logic
* Business Object definitions (JSON format)
* Attached artifacts (if selected)

***

### Import Microflow

Microflows can be imported into another application using the **Import** option in the Project Information screen.

#### Access Import Option

1. Open **Microflow Designer**
2. Navigate to the **Project Information** screen
3. Click **Import**

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FXNhJ9Mlgu7r1vMRy8k8f%2Fimage.png?alt=media&#x26;token=fb45dc5b-62fa-40da-9ff0-efab916f924b" alt=""><figcaption></figcaption></figure>

***

#### Import Process

1. Click **Choose File**
2. Select the exported Microflow configuration file
3. The system displays all Microflows available in the package
4. By default, all Microflows are selected for import

***

#### Import Mode Options

Users can choose how the Microflow should be imported:

* **Import as New**
  * Creates a new Microflow
  * Existing flows remain unchanged
* **Overwrite Existing**
  * Replaces an existing Microflow
  * User must select which flow to overwrite

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FA8vKN7iGC1nbSrUAG5dc%2Fimage.png?alt=media&#x26;token=7b8eaf9f-0a3d-4ffd-8452-529b09bde642" alt=""><figcaption></figcaption></figure>

***

#### Complete Import

1. Click **Import**
2. The Microflow is imported into the application
3. Imported Microflows appear:
   * Under the **Flow Name** section
   * In the Microflow navigation menu

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FgSdb7bJzRpwXcPZguFWJ%2Fimage.png?alt=media&#x26;token=39c6fc03-d00f-49a0-8c0c-6020147b3dfa" alt=""><figcaption></figcaption></figure>

***

### Best Practices for Import / Export

* Use **Config + With File** when sharing flows with Java or Web Service dependencies
* Use **Only Config** for logic replication within the same environment
* Avoid overwriting flows unintentionally—verify before importing
* Keep exported files versioned for traceability
* Validate imported Microflows before deployment

***

### Summary

The **Import / Export Microflow** feature enables efficient reuse and portability of integration logic in ONEWEB.

With this capability, users can:

* Replicate Microflows across applications
* Migrate integrations across environments
* Share reusable integration logic
* Reduce duplication and development effort

This is a key feature for maintaining **consistent, scalable, and enterprise‑grade integrations** using ONEWEB Microflow.


---

# 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.onewebstack.com/building-apps/integrations/develop-integration-with-oneweb-microflow/import-export-microflow.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.