# Microflow Import / Export **Microflow Designer (MFD)** provides the capability to **export Microflows from one application and import them into another application or environment**.\ This feature enables teams to **reuse integration logic**, maintain **consistency across projects**, and **migrate Microflows across environments** such as Development, SIT, and Production. With Microflow Import / Export, Microflows can be: * Reused across multiple applications * Migrated between environments * Shared without redesigning logic from scratch *** ### Export Microflow Microflows can be exported from an application via the **Project Overview** screen in Microflow Designer.\ The export capability allows one or more Microflows to be packaged together for reuse or migration. #### Export Scope * Users may select **one or multiple Microflows** in a single export operation * Exported packages include Microflow definitions and related configuration, depending on the selected export mode
*** #### Export Options When exporting Microflows, users are presented with **three export modes**, allowing flexibility in how configurations and artifacts are included. **Exporting Configuration (Config Option)** When **Config** is selected, two export variants are available: #### **Only Config** Exports: * Microflow definitions * Business Object definitions Does **not** include: * Java Node JAR files * Web Service artifacts (WSDL / XSD)
This option is suitable for logic replication when external dependencies are already available in the target environment. *** #### **Config + With File** Exports: * Microflow definitions * Business Object definitions * Attached artifacts, such as: * Java Node JAR files * Web Service WSDL / XSD files This option ensures that Microflows with external dependencies can be imported and executed without additional setup.
*** #### Export Package Contents An exported Microflow package may contain: * Microflow logic definitions * Business Object models (JSON format) * Attached artifacts (when included) The package is saved **locally** and can be transported to another application or environment. *** ### Import Microflow Microflows can be imported into a target application using the **Import** option available on the **Project Information** screen. The import capability supports both **new Microflow creation** and **replacement of existing Microflows**, depending on the selected import mode.
*** #### Import Mode Options During import, users can choose one of the following modes: #### **Import as New** * Creates a **new Microflow** * Existing Microflows remain unchanged * Suitable when reusing logic alongside existing flows #### **Overwrite Existing** * Replaces an existing Microflow * User selects which Microflow should be overwritten * Suitable for environment promotion or version replacement
*** #### Import Result After import completion: * Imported Microflows appear under the **Flow Name** section * Microflows become available in the **Microflow navigation panel** * Attached artifacts (if provided) are registered with the project
*** ### Best Practices for Microflow Import / Export To ensure reliable reuse and migration: * Use **Config + With File** when Microflows depend on Java Nodes or Web Services * Use **Only Config** for logic replication within the same environment * Avoid accidental overwrites—verify selected import mode carefully * Maintain versioned export files for traceability * Validate imported Microflows before deploying to production Following these practices helps prevent dependency issues and unintended behavior changes. *** ### Summary The **Microflow Import / Export** feature enables efficient portability and reuse of integration logic in ONEWEB. With this capability, teams can: * Replicate Microflows across applications * Promote Microflows across environments * Share reusable integration logic * Reduce duplication and development effort This feature is essential for maintaining **consistent, scalable, and enterprise‑grade integrations** when using **Microflow Designer** as the system logic layer within the ONEWEB platform. --- # 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/oneweb-platform-th/designer-reference/microflow-designer/microflow-import-export.md?ask= ``` 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.