--- title: "Import and export configuration (r330 / LTS15 and later)" slug: "import-and-export-configuration-r330" updated: 2026-03-02T20:12:37Z published: 2026-03-02T20:12:37Z canonical: "support.tulip.co/import-and-export-configuration-r330" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Import and export configuration (r330 / LTS15 and later) Limited availability This feature is only available on r330 and later, and LTS15 and later. Who can use this feature Users on Enterprise plans and above. While export and import brings a vast majority of context within applications, it doesn't bring everything, and there may be some work required following an import to make an application functional. ## Added features ### Machines Machines will be included on import (although their mappings and data sources won't be). ### Table Queries and Aggregations Table Queries and aggregations will not create duplicates upon every import. Similarly to connector functions, the imported query or aggregation becomes the development version. The query or aggregation will only import as a snapshot if the same one already exists, but has a different configuration. ### Tables Archived table fields will not be included with their parent tables when they are exported. Linked record table field types will export to infinite depth, not just one layer of linking. ### Analytics Previously, changes to analytics were not reflected in imported apps. Now, apps will import analyses alongside them as new analyses, so changes are preserved. App analyses (on completion data) will not be be exported if they are referencing an app that is not included in the import. They will be clearly blank in the App Editor. ### App Version Comparison App version comparisons will work after importing a new version to an existing app- in the previous feature, it does not work. It will only work for new versions imported after the launch of this feature- forward-facing only. ## Assets that aren't moved Not all assets that can be referenced within an app or automation are automatically moved when that asset is exported. These are cases that need to be addressed following import. ### Approval types Approval types are not moved during export, and all approvals are removed from new apps on import. ### Users Users are not moved during export. Any users that have been assigned in app permissions, or referenced within app logic will need to be replaced. ### App transitions If one application transitions to another app, that Transition may be removed during export and import. If App A has a transition to App B and they are both in an app group that is exported, then transitions will be maintained. If only App A or App B is exported, that transition will break. ### Station and interface configuration Any references to stations, interfaces, machine data sources and edge devices will be broken upon import/export. ## Requires some configuration ### Connector environments Connector Environments (and authentication) details are not moved when connectors are moved between sites. Authentication will need to be redone after a connector is moved between sites. Custom Authentication Authentication tokens stored in custom headers on the connector or a function will be transfered. ### Approvals Approvals will be removed from an application on Export/Import. These must be reconfigured in the target instance. ### App permissions App Permissions will be removed from an application on Export/Import. These must be reconfigured in the target instance. ## Data that is not moved ### Version history Application version history is not moved on app export. Only a single application Version will be moved between instances. Applications can be imported into an existing application, adding a version to the version history. ### Any completion or table data The data stored within Tables and Completions is not moved when an application is exported and imported. ### Activity feed records The activity feed data associated with an asset, or any of its depencies are not moved on export and import. --- Did you find what you were looking for? You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic! **Approval** A mechanism for ensuring that applications are reviewed and approved before publication. *Approvals types*can be configured under the settings menu. Specific approvals may be applied to an application on the application homescreen. **Transitions** **Transitions** are a type of logic in **triggers**. **Transitions** can move operators between steps/apps or start/stop the app.**** Only 1**Transition******can be added to a single **Trigger.** *ex: Complete then change to X app, Next step, Previous step, Cancel app, etc.* **Environment** An **environment** is a set of parameters that match specific configurations for tests. An environment includes **API endpoints** and authentication profiles for REST, SOAP, and GraphQL services, as well as database connection settings, custom project properties, and parameters of connection to JMS servers. **Permissions** Settings for controlling which users have access to specific applications. Use permissions to ensure that only approved users are able to access published applications in production settings. **PublishedVersion** The **Published****Version**of a Tulip app is a complete version of your Application. When an app is ready to be run in production, its logic can be *frozen*by Publishing that app. One application can have multiple published versions. If a **Station**is assigned to run the Published version of an application, it will only see changes when they are published. **Tulip Tables** **Tulip Tables** are a global location to store your production data. **Tables** are made up of **Records** (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview(1).gif) **App Completion** **App Completions**are a mechanism to store immutable data from a Tulip app. When an app is completed, all **Variable's**current values will be stored in the app completions tab.****This completion data can be analyzed in **Analytics.** By default, after a Completion users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types.