Migrate from scratch pad to Enterprise

When you switch to Insomnia Enterprise, you can export your scratch pad workspace as a single Insomnia JSON file to capture all requests, collections, environments, variables, and metadata for migration.

1. In the Insomnia app, open your scratch pad workspace.
2. From the Scratch Pad dropdown menu, select “Export”.
3. Click Export.
4. From the Which format would you like to export as? dropdown menu, select “Insomnia v5”.
5. Click Done.

6. In the File name field, enter insomnia-scratch-pad-export.json.

   Make sure the file extension is .json to ensure that Insomnia recognizes it during import.

7. Click Export. This saves the export file locally.

1. Launch Insomnia and sign in to your Enterprise organization.
   • If your org enforces SSO, use the SSO button and complete your IdP flow.
2. On the dashboard, confirm that you see Personal Workspace or your Organization workspaces. Enterprise accounts organize work into projects.

1. In the Insomnia app, sign in to your Enterprise organization. If your org enforces SSO, click Continue with SSO and login.
2. In the Project sidebar, click +.
3. In the Project name field, enter Migrated scratch pad data.
4. In the Project type settings, select one of the following:
   • Cloud Sync: A cloud project to share and sync in your organization, uses E2EE.
   • Git Sync: Ties the project to your repository and requires each collaborator to connect with the repo.
5. Click Create.

1. In the Insomnia app Project sidebar, click Migrated scratch pad data.
2. Click Import.
3. Click Choose files.
4. Click the insomnia-scratch-pad-export.json file.
5. Click Scan.
6. Click Import.

If you used environment variables in your imported scratch pad data, you’ll need to review and fix any environment variables.

1. In the Insomnia app, click your imported scratch pad collection.
2. In the collection sidebar, click Base environment.
3. Click the edit icon.
4. Verify keys such as base_url and API tokens.
5. Use the JSON view to confirm nested values, then enable Table view.
6. If your team uses secret environment variables in the local vault, set or re-enter them as needed in Enterprise.

Secret variables live in the local vault namespace and do not appear in plain text. For example, vault.foo. Keep your vault key safe, resetting it deletes stored secrets.

Validate the migration

Now that your data is migrated to Insomnia Enterprise, verify that everything was migrated correctly by doing the following:

• Open a few imported requests and click Send. Confirm that the URL, headers, and body match what you used in scratch pad.
• Switch environments and verify that requests resolve variables as expected.
• If you chose cloud sync, sign in on another machine and confirm the project appears and stays in sync.