Add to Chrome — free

How to import Session Buddy to Tabwell

You have a Session Buddy collection built up over a year — dozens of saved windows, each a flat list of tabs, and the tab groups you actually worked in are nowhere in it, because Session Buddy saves whole windows but ignores Chrome tab groups. To import Session Buddy to Tabwell you do not rebuild any of that by hand: Tabwell ships a built-in Session Buddy importer that reads a Session Buddy JSON export and brings the saved windows and their URLs across in two clicks, turning each session into a Tabwell snapshot you can restore. What does not come across is group structure Session Buddy never stored — its export has windows and tabs, not group titles, colors, or collapsed state — so the import gives you back the windows and links, and from there you arrange them into Chrome tab groups and snapshot them with full group fidelity going forward. The importer is a Tabwell Pro feature, available during the 14-day Pro trial every install starts with, and the whole migration runs locally: the imported snapshot is written to IndexedDB on your device, with no account and nothing leaving the machine. This guide walks the migration step by step, covers what carries over and what you rebuild, and explains how the importer is gated.

What a Session Buddy export holds

Session Buddy saves a session as a set of windows, each one a list of the tabs it held — title and URL. That is more structure than a single flat dump, but it stops at the window: Session Buddy ignores Chrome tab groups, so the group a tab belonged to, the group's title, its color, and whether it was collapsed are not in the export. Its telemetry also phones home every 24 hours, which is one reason power users move off it. Before you migrate, set expectations — the export brings windows and URLs across, not a group layout, because Session Buddy never recorded one. The structure is something you rebuild once in Tabwell, after which Tabwell preserves it on every save and restore.

Migrating from Session Buddy to Tabwell in two clicks

The migration uses Tabwell's built-in Session Buddy importer — there is no manual copy-paste and no third-party converter. Work through it in order:

  1. Install Tabwell from the Chrome Web Store and pin it to the toolbar. Every install starts with a 14-day Pro trial, which is what makes the importer available.
  2. In Session Buddy, export your saved sessions to a JSON file using Session Buddy's own export option.
  3. Open Tabwell, open the importer, and choose Session Buddy as the source.
  4. Load the Session Buddy JSON export. The saved windows and their URLs come across in two clicks and land as a Tabwell snapshot you can open from the side panel.
  5. Arrange the imported tabs into Chrome tab groups and save them — from here Tabwell records each group's title, color, and collapsed state through the chrome.tabGroups API, so the layout survives the next save and restore.

What carries over and what you rebuild

The windows, tab titles, and URLs carry over — that is the research worth migrating, the part you spent a year collecting. Group structure does not, because, as above, Session Buddy never stored it. That is not a Tabwell limitation; it is the gap between a windowed URL list and a full session record. Once the import lands as a snapshot, you group the tabs the way you want, and Tabwell's snapshot keeps that grouping with full fidelity going forward. For the grouping mechanics, see the guide on saving Chrome tab groups; for getting a snapshot back on screen, see the restore guide linked below.

How the importer is gated

The built-in Session Buddy importer is a Tabwell Pro feature. Every install starts with a 14-day Pro trial and no credit card, so you can run the migration on day one before you decide anything. After the trial, the Free tier keeps your latest 5 snapshots with manual save and restore and a 60-minute auto-snapshot; Pro lifts the 5-snapshot cap, indexes every saved tab for full-text search, auto-snapshots every 5 minutes, and is what keeps the importer enabled — $3.99/month, $29/year, or $19 one-time for the first 1,000 Founders buyers ($59 after).

FAQ

Is the Session Buddy importer free?

The built-in Session Buddy importer is a Tabwell Pro feature, but every install starts with a 14-day Pro trial and no credit card, so you can run the full migration during the trial at no cost. After the trial, keeping the importer enabled is part of Pro. The Free tier still lets you manually save and restore your latest 5 snapshots.

Do my Session Buddy tab groups come across when I import?

Session Buddy saves whole windows but ignores Chrome tab groups, so there are no groups in the export to bring over. The import carries the saved windows, tab titles, and URLs, and you regroup them in Tabwell. From then on Tabwell preserves each group's title, color, and collapsed state on every save and restore.

How do I import a Session Buddy session into Tabwell?

Export your saved sessions from Session Buddy to a JSON file, then open Tabwell's built-in importer and choose Session Buddy as the source. Load the export and the windows and their URLs come across in two clicks as a Tabwell snapshot. No manual copy-paste or third-party converter is involved.

Does the importer bring my saved windows across, not just a list of links?

Yes. Unlike a flat single-list dump, a Session Buddy export keeps each window's tabs together, and the importer carries that window grouping across as part of the snapshot. What it cannot carry is Chrome tab group title, color, and collapsed state, because Session Buddy never recorded those. You add the tab groups once in Tabwell and they are preserved from then on.

How much does Tabwell cost after the trial?

Every install includes a 14-day Pro trial with no credit card. After that, Free keeps your latest 5 snapshots; Pro is $3.99/month, $29/year, or a one-time $19 Founders license for the first 1,000 buyers ($59 after). Refunds are 30-day, no questions asked.

Which Chrome version do I need to migrate from Session Buddy?

Chrome 114 or newer, because Tabwell uses the chrome.sidePanel API introduced in that release. The import itself works the same on any supported version. Edge and other Chromium browsers may run it but are not the supported target, and Firefox and Safari are not supported.