How to import Session Buddy JSON into Tabwell

Tabwell's current Session Buddy importer expects a JSON object containing a sessions array, with windows and tabs nested inside each session. It validates the JSON root, skips empty windows, and converts every non-empty source window into one imported Tabwell snapshot. Where supplied, the importer carries URL, title, tab order, and pinned state. It places those tabs in one grey group named Imported instead of inventing native Chrome group metadata that is not part of the accepted shape. This is a description of Tabwell's parser, not a permanent claim about every Session Buddy release, so make the export using the exact version you run and retain the original file. Start with a representative sample that includes single-window, multi-window, and pinned-tab cases. Compare source and destination counts, inspect sample URLs, then restore a disposable imported snapshot before moving the full archive or changing the source data.

Create a migration worksheet

Before importing, record each sampled session name, its number of non-empty windows, tab count per window, pinned tabs, and several known URLs. Export from the current Session Buddy UI and keep an untouched copy of the JSON.

Run the Tabwell import

Install Tabwell from the Chrome Web Store and open the importer during the local Pro trial.
Choose Session Buddy as the source and load the JSON sample.
Expect one imported snapshot for every non-empty source window.
Compare names, counts, order, pinned state, and sampled links with the worksheet.
Restore one disposable snapshot before importing the rest.

Rebuild native groups deliberately

The accepted JSON shape supplies sessions, windows, and tab fields, while Tabwell creates a neutral Imported group for each converted window. Arrange the tabs into the native Chrome groups you want, then save a new Tabwell snapshot so title, color, and collapsed state are recorded from that point onward. Do not remove the source archive until the new snapshot restores correctly.

Plans and data handling

The Session Buddy importer is a Pro feature available during the local 14-day trial. Free remains available afterward for manual save, restore, and JSON export within its limits. Current prices, purchase options, and terms are listed on the pricing page.

Snapshots, tab titles, and URLs stay in local IndexedDB. Billing and license requests use Tabwell's billing service and Polar without sending tab data. Optional redacted crash diagnostics can be enabled; they are off by default. See the privacy policy.

FAQ

What JSON shape does Tabwell's Session Buddy importer expect?

It expects an object with sessions, windows, and tabs. Invalid JSON or a non-object root fails clearly; empty windows do not create snapshots.

How are multiple source windows imported?

Every non-empty source window becomes one imported Tabwell snapshot, so a multi-window source session can produce multiple snapshots.

Which tab fields can carry over?

The importer reads URL, title, position, and pinned state when those fields are supplied. It does not invent missing native Chrome group fields.

How should I verify a large archive?

Use a worksheet and a representative sample. Compare snapshot and tab counts, names, order, pinned state, and sample URLs, then run a disposable restore before full migration.

Is the importer available during the trial?

Yes. It is available during the local 14-day Pro trial and remains a Pro feature. Current prices, purchase options, and terms are listed at https://tabwell.org/pricing.html.

Where is imported data stored?