Insomnia Environment Variable Conflicts During Workspace Import

Workspace Data Restoration

Insomnia allows users to back up and restore request collections and environment settings using a JSON-based export format. When restoring this data via the Import Data function, the application recreates the workspace state, including environment variables and plugins.

Import Collision Behavior

A specific uncertainty arises when importing a JSON backup into a profile that already contains an existing workspace with the same name. The current behavior regarding how the application handles overlapping environment variable keys is not explicitly defined in the documentation.

If the imported dataset contains variables that already exist in the target environment, it is unclear whether the system merges the values, overwrites the existing keys, or creates duplicate entries.

• Does Insomnia prioritize the imported JSON values over existing local environment variables during a name-collision import?
• Is there a configuration to trigger a merge instead of a full overwrite?