Migrating From Incogniton to JustBrowser: Exporting Profiles and Re-Binding Proxies

Last Tuesday I watched someone in a Discord server spend four hours trying to figure out why their Incogniton profiles kept hitting verification walls on Amazon. Turned out their cloud sync had been acting up for weeks. Session cookies weren't persisting between launches. Every login looked like a new device.

They'd hit that wall a lot of Incogniton users eventually hit: the free 10-profile tier works fine until it doesn't, and the cloud sync limits start mattering right around the time your operation scales past "hobby project."

I've been through two antidetect browser migrations in the past 18 months. Neither was fun. (I once managed to lock myself out of four accounts in a single afternoon because I got cocky and batch-migrated without documenting proxies. Learned that lesson the expensive way.) But the Incogniton-to-JustBrowser path is actually one of the cleaner ones — Incogniton's cookie export is decent, and if you document your proxy configs before touching anything, the whole process takes maybe 20 minutes per profile.

Here's the exact workflow.

What You'll Have at the End

Working profiles in JustBrowser with cookies intact, proxies bound, and fingerprints validated on CreepJS. Your warmed-up accounts carry over. Your session state carries over. You'll run detection tests before touching anything that matters.

This isn't a 5-minute job. Budget 15-20 minutes per high-value profile. Faster if you batch the easy stuff.

Prerequisites

Incogniton installed with the profiles you're migrating
JustBrowser downloaded — 7-day trial gives you 5 profiles for testing the workflow
Cookie export extension — EditThisCookie or Cookie-Editor works fine
Proxy credentials documented — host, port, username, password for each profile
60-90 minutes for your first batch of 3-5 profiles

If you're moving more than 5 profiles, grab JustBrowser Pro ($9.99/month for unlimited) before starting. Otherwise you'll run out of trial mid-migration and have to pause.

Step 1: Document Your Incogniton Setup First

Skip this and you'll regret it. I skipped it on my first migration. Cost me a Facebook Business Manager that had been running clean for eight months. The proxy config was wrong by one digit in the port number. One digit.

Open Incogniton. For each profile you're moving, note:

Profile	Platform	Proxy Host	Port	Timezone	OS	Last Active
AMZ-Seller-01	Amazon	us.smartproxy.com	10001	America/Chicago	Windows 11	2026-06-24
FB-BM-Main	Facebook	isp.iproyal.com	32000	America/New_York	macOS	2026-06-25
TEST-Profile	General	185.xxx.xxx.xxx	8080	Europe/London	Windows 10	2026-06-20

Why does this matter? IP consistency is the single biggest factor in avoiding account flags during migration. Platforms care less about canvas hash changes (browsers update all the time) and more about whether your IP + timezone + language pattern suddenly shifts. The geoip mismatch guide covers what triggers these flags in detail.

Get the proxy config right. Everything else is recoverable.

Step 2: Export Cookies From Incogniton

Incogniton has a built-in cookie export option — better than some competitors, honestly. But I still prefer the extension method for control.

Method A: Browser extension (my preference)

Launch the Incogniton profile
Navigate to the platform — Amazon, Facebook, TikTok, wherever
Confirm you're logged in. Stale sessions export useless cookies.
Click EditThisCookie → Export → choose JSON or Netscape format
Save as amz-seller-01-cookies.json

Method B: Incogniton's export

Right-click the profile in Incogniton
Export → Cookies
You'll get a JSON file

The extension method lets you export per-site, which is cleaner when one profile handles multiple platforms. Incogniton's bulk export grabs everything, which can include garbage cookies you don't need. Thousands of tracking cookies from random ad networks. You don't want those.

Critical: Export while actively logged in. Server-side sessions expire. A cookie file from last month is worthless — the session token died server-side even if the file still exists locally.

Step 3: Create Matching Profiles in JustBrowser

Open JustBrowser. New profile. Now pay attention.

Settings that MUST match:

Operating System: Windows 11 in Incogniton → Windows 11 in JustBrowser. Don't mix.
Timezone: Must match proxy location exactly. Chicago proxy = America/Chicago. Not "close enough." Exact.
Language: Match proxy country. US proxy = en-US. German proxy = de-DE.
Screen Resolution: Match what Incogniton was using. 1920x1080 → 1920x1080.

Settings that will differ (and that's fine):

Canvas fingerprint — different engines produce different hashes. Normal.
WebGL renderer — regenerates. Platforms expect this when browsers update.
Audio fingerprint — same deal.

I spent way too long worrying about fingerprint values on my first migration before realizing: fingerprint changes look like browser updates. IP changes look like account theft. Focus on the IP. The WebGL fingerprinting guide explains why these values change legitimately all the time.

Proxy configuration:

Enter your existing proxy credentials. Same host, same port, same auth. Use JustBrowser's built-in proxy tester — if the country or IP differs from what you expect, stop. Debug before continuing.

One wrong character in a proxy credential = one burned account. Check every field twice.

Step 4: Import Cookies and Verify Session

In JustBrowser's profile settings, find cookie import. Paste JSON or upload the Netscape file.

Launch the profile. Navigate to the platform. Check: are you logged in?

Logged in? Great. Move to fingerprint validation.

Logged out? Something broke. Common causes:

Session expired server-side

The cookie file was valid when exported but the session died since then. Log back in from the JustBrowser profile. As long as IP + timezone match your pattern, one new-device login is normal.

Cookie format mismatch

Some exports include metadata that breaks import. Strip to essential fields: name, value, domain, path, expiration. The cookie import/export formats guide covers format conversions.

Domain mismatch

Cookies for .amazon.com don't apply to amazon.co.uk. Make sure domains match.

Re-authentication isn't catastrophic. What matters: doing it from the right IP and timezone. One login from a "new device" that matches your historical pattern is fine. One login from a completely different geography is how accounts die.

Step 5: Validate Fingerprints on CreepJS

Do not skip this. I know you want to. Don't. I've skipped it twice. Both times I regretted it within a week.

Before using the migrated profile on any account that generates revenue:

Launch the profile in JustBrowser
Go to CreepJS
Wait 15-20 seconds for the full report
Check the Lies section — should be empty or minimal
Note the Trust Score — 80%+ is solid

What you're looking for:

Lies section: Empty = good. Red entries = detectable inconsistencies.
Trust score: Below 65% means something's misconfigured.
Consistency: Run the test twice. Same hashes both times? Good. Random changes = stability problem.

Also run Pixelscan and BrowserLeaks. The CreepJS and Pixelscan benchmark explains what each metric actually means — not all of them matter equally.

If something fails: check timezone vs proxy location first (60% of issues), then language settings, then OS consistency. These three cause most detection failures. Fingerprint values are almost never the problem.

Cookies carry session state. They don't carry browsing history.

JustBrowser's cookie warm-up engine visits 127 curated sites to build realistic history signals. Run it on migrated profiles. Takes about 10 minutes per profile. This reinforces the account-age pattern that platforms use for trust scoring.

For the first 48-72 hours post-migration:

Keep activity patterns consistent with your previous behavior
Don't suddenly 10x your actions
Avoid heavy automation until you've confirmed stability

The account warm-up duration data has specifics on how long platforms remember behavior patterns.

Step 7: Migrate Production Profiles Gradually

Start with profiles that matter but aren't critical. Test accounts, secondary sellers, profiles you can afford to lose.

Run them in JustBrowser for a full week. Watch for:

Increased CAPTCHA frequency
Verification prompts you didn't get before
Session instability or unexpected logouts

No issues after a week? Migrate the rest. Problems? Debug. Do not — and I cannot stress this enough — touch your $50K/month Amazon seller account until you've sorted it.

I've given this advice to maybe forty people. At least eight of them ignored it and migrated their most valuable profile first. Guess which ones had bad weeks.

Common Errors and Fixes

Proxy connection fails in JustBrowser

Cause: Credentials wrong, or provider requires IP whitelisting.

Fix: Double-check every field. Some providers (Bright Data, IPRoyal, Smartproxy) require you to whitelist your machine's IP. If you're migrating from a different computer than you used with Incogniton, add the new machine's IP to your provider's allowlist.

CreepJS trust score dropped compared to Incogniton

Cause: Fingerprint settings don't match proxy location.

Fix: Verify timezone = proxy timezone. Language = proxy country language. OS consistent with profile history. Disable browser extensions during testing — some modify fingerprint APIs in detectable ways.

Session keeps logging out after migration

Cause: Cookie domain mismatch or server-side session expired.

Fix: Re-authenticate from the JustBrowser profile. Make sure IP and timezone match your historical pattern. Have 2FA recovery codes ready — some platforms require verification on fingerprint changes.

Profile runs slower than in Incogniton

Cause: Usually proxy latency, not the browser.

Fix: Test proxy speed independently with a speed test site. If it's slow, that's your provider. Also check if you're running too many profiles on underpowered hardware — I've seen people try to run 30 profiles on a laptop that struggles with 8. (And look, if you're blaming the browser for slowness before checking your residential proxy latency, you're troubleshooting backwards. Proxy first. Always.)

The Pricing Math

Let's be honest about numbers.

Incogniton's free tier gives you 10 profiles. That's generous — more than most competitors. But once you outgrow it, you're paying for cloud sync, storage, and additional profiles.

JustBrowser is $9.99/month for unlimited profiles. Or $99.99/year if you pay annually ($99.99/year). The 7-day trial gives you unlimited profiles to test the workflow before committing.

If you're running 15-20 profiles, compare what you're actually paying on Incogniton against $9.99/month flat. If you're running 50+, the math gets very clear very fast. Honestly? Per-profile pricing models are a racket for anyone running at scale. Flat pricing exists specifically because operators know what they need.

Run both tools in parallel while migrating. Don't rage-cancel Incogniton until your critical profiles have been stable in JustBrowser for at least two weeks.

Next Steps

Once your test profiles run clean for a week:

Batch migrate remaining profiles — Gets faster with practice. 5-8 profiles per hour is realistic.
Set up fingerprint monitoring — Monthly CreepJS checks catch detection drift before it matters.
Configure automation — If you're using Playwright or Puppeteer, the REST API quickstart covers programmatic profile control.

For click fraud protection on ad accounts during this transition, ClickzProtect monitors for invalid clicks. For privacy-first analytics that doesn't leak to the same platforms you're managing, JustAnalytics handles conversion tracking without cookie dependency.

Migration isn't fun. Never is. There's no magic button, no drag-and-drop import that just works. But Incogniton's cookie export is cleaner than most competitors, and if you follow the proxy-config-first approach, you'll get through this without burning accounts.

Take your time. Validate everything. And seriously — don't start with your most valuable profile.

Frequently Asked Questions

Does switching from Incogniton to JustBrowser cause account bans?

Not if you keep IP and timezone consistent. Platforms weight IP continuity far more heavily than browser fingerprint values. Same proxy, same timezone, same language — and fingerprint changes look like a normal browser update. The risk factors: switching proxy providers, timezone mismatches, or losing cookies that force re-authentication from a "new device" that doesn't match historical patterns.

Can I directly export Incogniton profiles into JustBrowser?

No direct profile transfer exists between antidetect browsers. You'll export cookies via browser extension or Incogniton's export feature, document your proxy credentials, then create new profiles in JustBrowser with matching OS, timezone, and language settings. Budget 15-20 minutes per profile for high-value accounts.

What happens to my profile aging and warm-up history after migration?

Session cookies carry login state, but browsing history doesn't transfer between tools. JustBrowser's cookie warm-up engine can rebuild realistic history signals across 127 curated sites. Run warm-up on migrated profiles for the first few days and maintain consistent activity patterns.

Should I wait until my Incogniton subscription expires before switching?

Run the numbers. Incogniton's free tier caps at 10 profiles. If you've outgrown that cap, you're paying for more. JustBrowser is $9.99/month for unlimited profiles — or $99.99/year on annual at $99.99/year. Run both tools in parallel for a month while migrating, then cancel whichever you're leaving.

Try JustBrowser

Native Chromium antidetect browser — not extension-based. Real C++ engine patches at the canvas / WebGL / font / TLS layer, so 40+ identity parameters are genuine, not faked. REST API for Playwright, Puppeteer, Selenium. 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