---
title: Swimlane Solution Packages
slug: swimlane-solution-packages
docTags: 
createdAt: 2025-08-11T11:13:48.000Z
---

Use Swimlane Solution Packages (SSPs, file extension `.ssp`) to transfer collections of applications, applets, playbooks, builder components, builder solutions, and their associated entities between Turbine instances.

## At a Glance

| Task                 | Description                                                                    | Link                                                              |
| -------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------- |
| **Export an SSP**    | Package one or more entities and download as an `.ssp` file.                   | [Export Swimlane Solution Packages](docId\:lke_ku_rDUi2WkwCEFj3W) |
| **Import an SSP**    | Upload an `.ssp` or `.json` file and selectively import entities into Turbine. | [Import Swimlane Solution Packages](docId\:iNUD2C-loASyYC1RptbrR) |
| **Repackage an SSP** | Re-compress an unzipped and edited SSP so it imports correctly.                | [Repackage an Unzipped SSP File](docId\:yEVfL9bCUyPqFmOZwRZfT)    |

## What an SSP Contains

An SSP packages the selected entity and all of its dependencies into a single file. The following table shows what is included and what is excluded.

| Included                                                                   | Excluded                                                                 |
| -------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Root application, applet, playbook, builder component, or builder solution | Application history and record history                                   |
| Associated applications and applets                                        |                                                                          |
| Workflows for root and associated entities                                 | Secure credentials and key store values (can be added after import)      |
| Reports, workspaces, dashboards, and export templates                      | Secure values in asset configurations (can be reconfigured after import) |
| Playbooks (including parent and nested playbooks)                          | Connectors (maintain separately)                                         |
| Orchestration tasks, ingestion rules, sensors, and correlation rules       |                                                                          |
| Assets, plugins, and Dynamic Orchestration assets                          |                                                                          |
| Builder components, builder solutions, and builder intents                 |                                                                          |
| Mapped inputs to key store values (keys removed; add after import)         |                                                                          |
| Application records (optional)                                             |                                                                          |

:::hint{type="info"}
SSPs can optionally include application records when exporting applications. This allows packaged solutions to include preconfigured content such as knowledge base articles, templates, and rule records.
:::

## Export Entry Points

You can export an SSP from any of these starting points.

| Entry Point               | How to Access                                                                                            |
| ------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Application or Applet** | From the **Applications and Applets** page, or from within Application or Applet Builder.                |
| **Playbook**              | From the **Playbooks** page or from within an open playbook.                                             |
| **Builder Component**     | From the component context menu in the builder.                                                          |
| **Builder Solution**      | From the solution context menu in the builder.                                                           |
| **Global Export**         | From the **Applications and Applets** page, select multiple entities across types for a combined export. |

## Selective Entity Export and Import

SSPs include a **relationship graph** that maps dependencies between entities. During export or import, Turbine displays a tree of all entities in the package. You can select or deselect individual entities. Dependent entities are auto-selected and locked when their parent is selected.

:::hint{type="info"}
SSPs exported from older versions of Turbine (before the relationship graph feature) do not support selective entity export or import. All entities in those packages are included automatically.
:::

## Same Name, Different Identity in the Target Tenant

If the target tenant already contains a playbook, builder component, or other packaged entity **with the same name** as an item in the SSP, but that existing copy came from **another** export (a **different sharing identity**), the import may stop with explicit rename or save errors. That behavior is **by design** so you can resolve the conflict deliberately. For message examples and resolution options (rename in tenant, partial import, clean tenant), see [Import Errors: Same Name, Different Sharing ID](https://docs.swimlane.com/import-swimlane-solution-packages#import-errors-same-name-different-sharing-id) in **Import Swimlane Solution Packages**.

## Permissions

Exporting and importing SSPs requires the **System Administrator** role.

:::hint{type="info"}
A system feature flag (`HideSspImportExport`) can hide the import and export UI. If you do not see the import or export options, contact your administrator to verify the flag is not enabled.
:::