Switching From Octo Browser to JustBrowser: 7-Step Migration Guide (2026)

12 min read

Switching from Octo Browser to JustBrowser comes down to careful documentation and a few verification steps. Consider a team running thirty-eight Octo Browser profiles across client and storefront accounts. Octo's per-profile pricing grows with the profile count, and for a team that keeps adding profiles for new clients, the invoice climbs with every addition.

Octo Browser is a capable multi-account browser. The reason teams move is usually the pricing model, which charges by profile, while JustBrowser is one flat plan with unlimited profiles and free team seats.

What You'll Have at the End

A repeatable migration workflow. Cookies exported from Octo Browser. Proxies rebound in JustBrowser. Each profile's settings checked for consistency before you touch anything that generates revenue.

Budget 15-20 minutes per high-value profile. It is not instant, but you only do it once, and the flat pricing on the other side makes it worth the afternoon of careful work.

Prerequisites

Before starting your Octo Browser to JustBrowser migration:

  • Octo Browser installed with active profiles you're migrating
  • JustBrowser downloaded. The 7-day trial is full access (card required, no charge if you cancel within the seven days), so you can test the migration before committing. See the full JustBrowser blog for setup guides.
  • Cookie export extension installed in Octo (Cookie-Editor, for example)
  • Proxy credentials documented: host, port, username, password for each profile
  • 60-90 minutes for your first batch of 3-5 profiles
  • Authority over each account. Only migrate accounts you own or manage with the owner's permission.

Moving more than 10 profiles? Start the trial when you have the time to finish the migration, so the trial clock doesn't run out halfway.

Step 1: Document Everything in Octo Browser First

You'll want to jump straight to exporting cookies. Don't.

Open Octo Browser and build a migration spreadsheet. For each profile:

Profile NamePlatformProxy TypeProxy HostTimezoneLast ActivePriority
Client-A-StoreShopify adminNone (office network)—America/Chicago2026-07-08Critical
QA-UK-01Storefront QA, logged outISPuk.proxy.example.com:30555Europe/London2026-07-09High
ADV-DE-01Ad verificationResidentialde.proxy.example.com:10001Europe/Berlin2026-06-28Low

Why the spreadsheet? Because proxies and location settings are where migrations most often go wrong.

If a QA profile has always checked the UK storefront through one ISP proxy, and you configure a different provider or region in JustBrowser, your results change for reasons that have nothing to do with the site. For logged-in accounts, keep signing in from the network you normally use; a sign-in from a new application can still bring a verification prompt, which you complete as the account owner or authorised manager.

The tedious documentation prevents an expensive mistake. A mistyped port number can send a profile through the wrong exit, and that is hard to trace later.

Step 2: Export Cookies from Octo Browser

Octo Browser doesn't have a universal "export all cookies" button. You'll extract per profile.

Method A: Browser extension (recommended for most people)

  1. Open the Octo Browser profile you're migrating
  2. Navigate to the platform: Amazon, TikTok, Facebook, wherever
  3. Confirm you're logged in. Stale sessions export worthless cookies.
  4. In the extension, export that site's cookies as JSON (Cookie-Editor also offers Netscape format)
  5. Save the file: client-a-store-cookies.json

Method B: Octo Browser's local API

Octo Browser has its own local API. If you're comfortable scripting, check its documentation for the call that starts a profile and returns a debugging address, then read the cookies over CDP. The API approach is faster for bulk migrations but needs a script. Most people use the extension.

Critical part: export cookies while actively logged in. If your last session was two weeks ago, open the profile, verify you're authenticated, then export. Server-side sessions expire, and old cookie files are useless.

For each profile you should now have a cookie file, proxy credentials and documented settings.

Step 3: Create Matching Profiles in JustBrowser

Open JustBrowser. Create a new profile. This is where precision matters.

Settings that should match your Octo Browser profile:

  • Operating System: Windows 11 in Octo → Windows 11 in JustBrowser. macOS stays macOS.
  • Timezone: match the proxy location. A Chicago proxy means America/Chicago.
  • Language: match the proxy location. A US proxy means en-US as the primary language.
  • Screen Resolution: match exactly. 1920x1080 → 1920x1080.

Settings that can differ:

  • Graphics rendering output: different engines produce different results. Expected.
  • Graphics card renderer string: regenerates. Fine.
  • Audio output: same.

Spend your care on the proxy and location settings rather than on matching rendering values. A browser's rendering legitimately changes whenever someone updates, reinstalls or switches machines; what you want to carry over is the network and locale each profile was set up for.

Proxy configuration:

Enter your existing proxy credentials exactly. Same host, same port, same auth.

JustBrowser has a built-in proxy tester. Use it. If the returned IP or country differs from what you expect, stop and debug before continuing.

One wrong digit in a port is enough to break a profile. Check every field, then check again.

Step 4: Import Cookies and Verify Login State

In JustBrowser's profile settings, find the cookie import option and paste or upload the file; JSON and Netscape formats are both detected automatically. (Over the local API, it's POST /profiles/{id}/cookies.) Import while the profile is stopped.

After importing, launch the profile, navigate to the platform and check whether you're logged in.

Logged in? Move to the consistency check.

Logged out? Something broke. Common causes:

  • Expired cookies: the session died server-side. You'll need to log back in.
  • Format mismatch: strip to essential fields (name, value, domain, path, expiration). Some Octo exports include extra metadata that breaks import.
  • Domain mismatch: cookies for .amazon.com don't work on amazon.de.

Logging in again isn't catastrophic. A sign-in from a new application is routine for most platforms. Have 2FA recovery codes ready, and complete any verification the platform asks for as the account owner or authorised manager.

Step 5: Check Each Profile's Settings Agree

Do not skip this, even for a "low priority" test profile. A profile with the wrong settings gives wrong results, however unimportant it is.

Before handing any migrated profile to the team:

  1. Launch the profile in JustBrowser
  2. Run the profile's consistency check in the app (or over the local API, where the operation is listed in the API reference), and open a public page such as BrowserLeaks to read the location, language and system values a website can see
  3. Compare the readout to your migration spreadsheet

What you're looking for:

  • Location: IP location, timezone and language all describe the same place
  • System: the OS, screen and hardware values match what you recorded for the profile
  • Stability: run the check twice. Values that change between runs point to a settings problem, not a normal profile

You are not chasing a score. You are confirming that the profile's settings agree with each other and with your documentation. If something disagrees, check timezone against the proxy location first (the most common cause), then language settings, then OS consistency.

Step 6: Set Up Shared Access and First Sessions

Your cookies carry session state, and the profile is now ready to use. Before handing it over:

  1. Open each migrated profile and complete one ordinary working session: sign in, load the dashboard, confirm the account's data looks as expected.
  2. Share the profile with the teammate who manages that account. In JustBrowser, team seats are free and unlimited, and a direct share carries view-only or launch permission. A seat can only run the profiles shared with it, so anyone who needs their own profiles takes their own subscription.

If you use Playwright or Puppeteer for automation, the REST API guide covers programmatic profile launch. Only automate what the platform's terms allow.

Step 7: Migrate in Batches, Not All at Once

Don't migrate your most valuable profile first.

Pick 2-3 profiles that matter but aren't critical. Use them in JustBrowser for a full week of normal work. Watch for:

  • Verification prompts you didn't get before
  • Session instability
  • Settings that drift from your spreadsheet

No issues after a week? Migrate the rest. Problems? Debug before touching high-value accounts.

Common Errors and Fixes

Cookies imported but session is gone

Cause: Cookies expired server-side, or you exported while logged out.

Fix: Log back into the account from the JustBrowser profile. A sign-in from a new application is routine; complete any verification as the account owner. Have 2FA recovery codes ready.

Proxy connection fails

Cause: Credentials wrong, or your proxy provider authenticates by allowlisted IP.

Fix: Double-check every field. Some providers let you authenticate by allowlisting your machine's IP instead of a username and password. If you're on a different machine than you used with Octo Browser, add the new machine's IP to your provider's allowlist. The ISP proxy tutorial covers provider-specific setup.

The readout shows mismatched location settings

Cause: Timezone or language doesn't match the proxy location, or there's an OS/language inconsistency.

Fix: Verify timezone = proxy timezone, language = proxy country language, OS = consistent with the profile's history. Disable all browser extensions during testing, since some extensions change browser APIs and muddy the readout.

Profile performance feels sluggish

Cause: Usually proxy latency, not the browser.

Fix: Test proxy speed independently. A slow proxy is the provider's issue, not JustBrowser's. Check hardware acceleration settings if local rendering feels off.

The Pricing Math

Whether the switch saves money depends on how many profiles and seats you run.

Octo Browser's plans are priced by profile count, so cost scales with how many profiles you run. JustBrowser is one plan: $9.99/month (or $99.99/year) for unlimited profiles, and team seats are free.

Here's what shifts the math:

  • A handful of profiles: compare Octo's published price for your count against the flat plan.
  • A growing profile count: the flat price matters more with every profile you add, because nothing scales with the count.
  • A team: seats cost nothing, though a seat only runs profiles shared with it.

JustBrowser offers a 7-day trial with unlimited profiles (card required, nothing withheld), so you can test the migration before committing. Check Octo Browser's published pricing for current figures.

Next Steps

Once your test profiles run cleanly for a week:

  1. Batch migrate the remaining profiles. It gets faster with practice.
  2. Run both tools in parallel for a month. Keep Octo Browser active until you're confident, and don't cancel early.
  3. Re-run the consistency check monthly. Engines and sites change. JustBrowser's engine is patched on every upstream Chromium release, so an occasional check keeps your reference profiles honest.

If you run paid campaigns, ClickzProtect monitors for fraudulent clicks, and its click fraud guide explains what signals to watch. For cookieless analytics on your own sites, there's JustAnalytics. Running outbound sales campaigns? VeloCalls provides call tracking.

Migration is tedious work that needs attention to detail. If the per-profile pricing stopped working for you, and you want local-first profile storage with optional unlimited cloud sync, the switch is worth the afternoon. Take your time, verify each profile, and don't migrate your most valuable profile first.

Frequently Asked Questions

Can I export Octo Browser profiles directly into JustBrowser?

No direct import path exists. Octo Browser profiles use a proprietary format that doesn't translate. You'll export cookies via browser extension, document proxy credentials separately, then recreate profiles in JustBrowser with matching timezone, language, and proxy settings. Plan 15-20 minutes per profile that matters.

Will switching from Octo Browser to JustBrowser log me out of my accounts?

It can, if cookies don't carry over or the session has expired server-side. Keep each profile's network, timezone and language as they were, import cookies while the old session is still active, and keep two-factor recovery codes at hand. Expect that a platform may ask you to verify a sign-in from a new application. Complete that verification as the account owner or authorised manager, and if an account is restricted, use the platform's own appeal or recovery route.

How does JustBrowser pricing compare to Octo Browser's per-profile model?

Octo Browser's plans are priced by profile count. JustBrowser is one plan at $9.99/month, or $99.99/year, with unlimited profiles and free team seats, so the more profiles and teammates you have, the more the flat price matters. Check Octo Browser's current published pricing and run the math for your own count.

What happens to my automation scripts that use Octo Browser's local API?

JustBrowser exposes a local REST API plus CDP endpoints for Playwright, Puppeteer, and Selenium. Your automation logic transfers, but you'll update connection strings and endpoint URLs. The API documentation covers the migration path.


Try JustBrowser

A multi-account browser for teams, built on a custom Chromium engine with native C++ integration, not an extension. Each profile is its own browser with its own cookies, storage, proxy and 40+ browser settings, and profiles can be shared with teammates. Local REST API and CDP for Playwright, Puppeteer, Selenium. Windows x64 and macOS (Apple Silicon). 7-day free trial, card required — then $9.99/month or $99.99/year, unlimited profiles, free team seats.

Get started → · How it differs from Multilogin / GoLogin / AdsPower

Tags
  • octo-browser-migration
  • multi-account-browser
  • profile-export
  • cookie-transfer
  • proxy-configuration
  • buildinpublic
  • saasstudio
  • aiworkforce
  • buildwithclaude

Ready to manage multiple accounts?

Seven days free, then $9.99/month — one plan, everything included.

We'd like to use Google Analytics, a Google service, to understand how our website is used. It sets two cookies in your browser and runs only if you click Accept. You can change your choice at any time with Cookie settings. Cookie Policy

Sign-in cookies and the cookie that remembers this choice are always on; the website needs them to work.

Google Analytics, a Google service, helps us understand how our website is used. It sets two cookies, _ga and _ga_TVZHQ99TZW. It is now onoff in this browser. If your browser sends a Global Privacy Control or Do Not Track signal, it stays off. Cookie Policy