An exported flow can be imported into .
Dev instance: If you are using an instance of the platform for developing and testing your flows, you can import a new flow through the Flows page.
NOTE: Unless your instance of the platform has been specifically configured to support deployment management, you are using a Dev instance of the platform.
NOTE: If you are attempting to share a flow with other users on the same instance of the platform, you should use the sharing functions. See Overview of Sharing.
Prod instance: If you are importing a flow into a Production instance of the platform, you import it as a package through the Deployment Manager.
NOTE: Deployment Manager is a feature that enables segmentation of platform usage between Dev instances and Prod instances. This feature must be enabled and configured. For more information, see Overview of Deployment Manager.
You cannot import flows that were exported before Release 6.8. See Changes to the Object Model.
NOTE: You cannot import flows into a version of the product that is earlier than the one from which you exported it. For example, if you develop a flow on free , which is updated frequently, you may not be able to import it into other editions of the product, which are updated less frequently.
Imported flows do not contain the following objects:
NOTE: Depending on the import environment, some objects in the flow definition may be incompatible. For example, the connection type may not be valid, or a datasource may not be reachable. In these cases, the objects may be removed from the flow, or you may have to fix a reference in the object definition. After import, you should review the objects in the flow to verify.
NOTE: Exported flows do not contain connections. If your flow relies on a connection to the source, you must create the connection in the Prod environment and create an import mapping rule to assign the local connection ID to the import package. Flows that do not require connections may not require remapping before import. See Define Import Mapping Rules.
NOTE: If the flow's output object uses connections that are not used for importing datasets in the flow, the output is broken on import. Those outputs and their associated connections must be recreated in the environment into which the flow is imported.
Imported datasets that are ingested into backend storage for may be broken after the flow has been imported into another instance. These datasets must be reconnected to their source. You cannot use import mapping rules to reconnect these data sources. This issue applies to the following data sources:
Before you import a package, you may need to create import mapping rules to apply to your package. For example, if the Development data is stored in a different location than the Production data, you may need to create import rules to remap paths and connections to use to acquire the data from the Production environment.
NOTE: Import rules are applied at the time of import. They cannot be retroactively applied to releases that have already been imported.
For more information, see Define Import Mapping Rules.
NOTE: You cannot import into a Dev instance if your account for the instance contains the Deployment role.
NOTE: If the exported ZIP file contains a single JSON file, you can just import the JSON file. If the export ZIP also contains other artifact files, you must import the whole flow definition as a ZIP file. For best results, import the entire ZIP file.
If there are issues with the import, click the Download link to review the missing or malformed objects.
Tip: When you import the flow, click the Warnings link to review the list of objects that must be remapped.
The flow is imported and available for use in the Flows page. After import:
After creating any import rules in your Prod instance, please do the following.
Tip: After you import, you should open the flow in Flow View and run a job to verify that the import was successful and the rules were applied. See Flow View Page.