Git Sync projects migration for Insomnia 12.6

Beta and uses: Insomnia

What changed

Before Insomnia v12.6.0, Insomnia stored Git internals in a private git/ folder and kept other project files in an other/ subfolder. The new layout matches a standard Git repository:

Project files	Insomnia v12.5 and older	Insomnia v12.6 and newer
Git internals	Stored in a private `git/` folder.	Stored in a standard `.git/` folder.
Non-Git files	Non-YAML files stored in an `other/` subfolder.	Non-YAML files sit at the top of the Insomnia project’s repository. Workspace metadata is in `version-control/git/<id>/insomnia.<project-id>.yaml`.

The migration only changes file paths. It doesn’t change:

API collections
Environments
Settings

How to run the migration

Open Insomnia v12.6.0 for the first time: a migration screen appears automatically.
Read the summary on the What’s new screen.
Click Continue.
On the migration screen, click Update Now.
Insomnia migrates all your Git Sync projects in a few seconds. When it’s done, click Open Insomnia.

The migration runs once. Future launches open Insomnia normally.

Validate

After migrating to Insomnia v12.6, you can:

Run Git commands like git status, git log, and git pull in your Insomnia project repository directly from your terminal.
Open the folder in any Git GUI.
Continue using Insomnia’s built-in Git Sync exactly as in previous versions.

The migration doesn’t affect:

Pending changes: The migration preserves uncommitted edits and in-progress work.
Duplicate migrations: Insomnia ensures each project is only migrated once.

How to roll back to an older version

The Insomnia 12.6 file layout preserves your project data. However, older versions of Insomnia (pre-v12.6.0) don’t understand the new .git/ layout. If you need to roll back to an older version:

Don’t delete the project folder: it still contains the data.
Back up your project: push any uncommitted changes to your remote from the Insomnia UI or the Inso CLI.
Install the older version.
Clone the project again from its remote through Insomnia’s Git Sync settings.

FAQs

Is my project’s data safe during the migration?

Yes. Your data is never deleted. The migration moves and restructures files, it doesn’t remove them.

Why am I getting warnings after upgrading?

Warnings mean that Insomnia migrated most projects, but a few couldn’t update automatically. Those projects are listed on screen. Insomnia has disconnected them from their Git remote and converted them into local projects so you don’t lose any data. To restore Git Sync:

Open the project in Insomnia.
Go to Project Settings → Git Sync.
Reconnect the project to its remote repository.

What should I do if the migration is unsuccessful?

If an unexpected error stops the migration before it finishes, your data remains intact and nothing is deleted. Click Retry Update to try again. If the problem persists, either:

Copy the error logs and visit the Git Sync docs.
Open a support ticket.

I have several Git Sync projects. Will the migration take a long time?

No. Insomnia migrates all Git Sync projects in parallel and the process typically completes in a few seconds, regardless of how many projects you have.

Why does a project show as Disconnected after the migration?

This means its migration hit an error and the project was converted to a local project to preserve your data. Reconnect it via Project Settings → Git Sync. Your remote history is untouched.

Do my teammates also need to run this?

Yes. Each person needs to migrate their local installation independently. The migration only changes local files; it doesn’t push anything to the shared remote.

Can I skip the migration?

No. To use Insomnia v12.6.0 and later versions, you need to run the migration. The migration screen continues to appear until it completes successfully.

Why does the Insomnia app show the migration screen every time I open it?

This means a previous migration attempt didn’t finish (for example, the app was closed mid-run). Click Update Now to complete it. If the problem persists, copy the error logs and visit the Git Sync docs or open a support ticket.