--- title: "Import and export configuration (r329 / LTS14 and previous)" slug: "import-export-configuration-r329" updated: 2025-07-31T13:34:50Z published: 2025-07-31T13:34:50Z canonical: "support.tulip.co/import-export-configuration-r329" --- > ## 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 (r329 / LTS14 and previous) :::(Warning) (Limited availability) This feature is only available on r329 and earlier, and LTS14 and earlier. :::
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. ## 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 {{glossary.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 {{glossary.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. ## Requires some configuration ### Connector environments Connector {{glossary.Environment}}s (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. :::(Warning) (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 {{glossary.Permission}}s 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 {{glossary.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 {{glossary.Table}}s and {{glossary.Completion}}s 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.