Skip to main content
Updated in 2026.20 Packages are a useful tool for exporting and importing Project resources, such as Flows or Lexicons, to share with other teams. With Packages, you can transfer resources from one Project to another. When you create a Package, it automatically includes its direct dependencies for supported resources. Once a Package has been downloaded, you can share it as a ZIP file. Compared to Snapshots, Packages give you more control over which resources you import and export. Packages support the following Project resources:

​
Limitations

  • The maximum Package size depends on how you create or upload it:
    • Cognigy UI: You can create and upload Packages of up to 8 GB. For on-premises installations, you can increase this limit by setting the RESUMABLE_UPLOAD_MAX_FILE_SIZE environment variable in values.yaml. The same limit also applies to Snapshots.
    • Cognigy API: You can create and upload Packages of up to 2 GB. Packages that exceed this limit can’t be created or uploaded. For on-premises installations, you can increase this limit by setting the PACKAGE_MAX_FILE_SIZE environment variable in values.yaml.
  • Endpoints in Packages must have a name with up to 180 characters. Endpoints with longer names cause the Package export to fail.

​
Restrictions

  • Importing Packages from a newer version of Cognigy into an older version may cause unexpected errors.
  • Cognigy skips unsupported resources while importing a Package. For example, deprecated Endpoints or LLMs with outdated configuration schemas.
  • If you export a Package from a Project with Extensions, you must install the respective Extensions in the target Project as well before importing the Package.

​
Working with Packages

You can export and import Packages in Manage > Packaging. You can also export a resource as a Package from the respective resource page by selecting menu > Export as Package.
  • During the import, you may need to resolve conflicts if the Package contains a duplicate of a Project resource.
  • Don’t import Packages for deploying Knowledge.AI resources in a production Project. AI Agents’ knowledge may be temporarily unavailable during the import.
  • Node IDs remain unchanged during the import to ensure that hardcoded links between Flows and Nodes don’t break. If you need to import a Flow multiple times into a Project, delete and re-create the Nodes before importing the Package to prevent Node ID conflicts.

​
Map Locales Before Importing Flows and Endpoints

Locales aren’t imported automatically. However, Packages that include a Flow or Endpoint with an assigned Locale also include the Project’s Locales. During import, you can map these Package Locales to Locales in the target Project.
Before importing the Package, create the required Locales in the target Project. During the import, map each Package Locale to the corresponding target Locale.You can map any Package Locale to the target Project’s primary Locale. If a non-primary Package Locale has incomplete localized content, Cognigy copies the missing content from the Package’s primary Locale.When replacing a Flow, its localized content from the Package overwrites the corresponding content in the target Project.If you don’t create the required Locale, Cognigy uses the target Project’s primary Locale instead.

​
Resolve Import Conflicts

If the Package contains a resource that already exists in your Project, you can resolve the conflict in the Conflict Management section that appears during the import. To manage conflicts, you have the following options:
  • Import as a copy — imports the resource as a new one and adds a counter to the name of the copy. For example, if the resource is a duplicate of a Flow named Main, the new Flow is named Main (2). Imported resources that reference the Package resource keep that reference. This option is selected by default.
  • Replace existing resource. The imported resource overwrites the existing resource in your Project.
Cognigy doesn’t import Knowledge Stores as a copy. Imported Knowledge Stores always replace the current version.
Q1: What should I do if I encounter errors during Knowledge Store Import?A1: Try to upload the Package again. During the reupload, select only the Knowledge Stores that were not fully imported.Q2: How can I avoid browser request timeouts during Knowledge Store Package upload?A2: To avoid browser request timeouts, keep the Package size low. Separate your resources into smaller Packages.

​
More Information

1 When you import a Knowledge Store Package, the source and target Projects must use the same embedding model. If they use different embedding models, recreate the Knowledge Sources to generate new embeddings with the target Project’s model.
Last modified on October 28, 2026