Leaving Dolphin Anty: Moving Ad-Account Profiles to JustBrowser Safely

Three weeks ago I watched someone lose a $12,000/month Facebook ad account in about four minutes.

The profile migration looked perfect. Cookies exported. Fingerprint parameters matched. Proxy configured. They logged in through the new browser, saw the familiar Business Manager dashboard, and started a campaign edit. Facebook's backend noticed the fingerprint discontinuity, flagged the session, and disabled the ad account before they'd finished adjusting the daily budget.

That's the nightmare scenario. And honestly? I've seen variations of it happen three times this year alone. "Just export and import" advice gets people banned. Every single time.

Look — I'm going to be direct here. Most migration guides are garbage. They skip the hard parts. This one doesn't. We're covering the staged migration process that actually works for high-stakes ad-account profiles, the kind where a fingerprint change mid-campaign gets you suspended before lunch.

What You'll Have at the End

A working migration workflow that moves Dolphin Anty profiles to JustBrowser without triggering fingerprint-change detection. You'll run parallel profiles during the transition, validate fingerprint consistency, and cut over accounts in batches after confirming session stability.

This isn't quick. Plan for 2-3 weeks from start to finish for a 20-account portfolio.

Faster than that? You're gambling. Your call.

Prerequisites

Before starting:

JustBrowser account: the 7-day trial works for testing (unlimited profiles, card required); after that it is $9.99/month for full migration. Start the 7-day trial to start.
Dolphin Anty access: Obviously. You need export capability for cookies and profile settings.
Proxy continuity: Same proxies you're using in Dolphin Anty. Don't switch proxies AND browsers simultaneously — too many variables. If you need reliable virtual cards for proxy billing, VeloCards handles multi-vendor payments cleanly.
Low-risk test accounts: 2-3 ad accounts you can afford to lose. Not your best performers.
Fingerprint testing sites open: CreepJS, Pixelscan, and BrowserLeaks. You'll use these repeatedly.

Step 1: Audit Your Dolphin Anty Profile Settings

Open each profile you're planning to migrate and document these parameters:

User agent (exact string, not just "Chrome 124")
Screen resolution (width × height)
Timezone (offset and IANA name, e.g., America/New_York)
Language (primary and accept-language header list)
WebGL vendor and renderer strings
Canvas noise seed if Dolphin shows it
Hardware concurrency (CPU cores)
Device memory value

Why document this manually instead of relying on export? Because you're not importing into JustBrowser — you're recreating profiles with equivalent parameters. The fingerprint needs to be consistent enough that Facebook's backend doesn't flag the change, but it won't be identical.

Close matters more than exact. I learned this the hard way on my own accounts, and yes, I'm still a little bitter about it.

Export screenshots of Dolphin's fingerprint test results for each profile. You'll compare these against JustBrowser later.

Step 2: Export Cookies from Dolphin Anty {#export-cookies}

In Dolphin Anty, export cookies for each profile in JSON format. Most antidetect browsers support Netscape format too, but JSON preserves more metadata.

Save cookies with filenames that match your profile naming convention. You'll need these organized when you're importing into 20+ JustBrowser profiles.

Critical: Don't logout of accounts before exporting. Cookie export should happen while sessions are active. If you logout first, you're exporting dead cookies and you'll have to re-authenticate anyway — which defeats the whole point.

(I've done this. More than once. Don't be me.)

Step 3: Create Matching Profiles in JustBrowser

In JustBrowser, create new profiles with parameters that match your Dolphin Anty documentation:

Resolution and timezone: Match exactly. Timezone mismatches are the #1 cause of fingerprint flags in our experience.
User agent: Use the same Chrome version and OS. JustBrowser's Chromium engine will render consistently — just match the UA string format.
Hardware specs: CPU cores, device memory, WebGL strings. JustBrowser pulls from real hardware signatures, so pick one that's close to your Dolphin profile.
Proxy: Same proxy you were using. Same authentication. Same rotation settings if any.

Don't try to randomize or "improve" the fingerprint during migration. I know it's tempting. Resist. You're trying to maintain continuity, not optimize. Save the tweaking for after accounts are stable on the new platform.

For teams doing this at scale, JustBrowser's REST API lets you script profile creation — we covered that in our Playwright/Puppeteer integration post. But for initial migration, do it manually. You need to catch configuration mistakes before they hit live accounts.

Step 4: Import Cookies and Validate Session

Import the exported cookies into each JustBrowser profile. JustBrowser accepts JSON and Netscape formats in the cookie manager.

After import, run the profile's cookie warm-up cycle. JustBrowser visits 127 curated sites to establish browsing history and refresh cookie timestamps. This isn't strictly necessary if you're importing fresh cookies, but it fills behavioral gaps in the profile.

Then test session validity:

Navigate to the ad platform (Facebook Business Manager, Google Ads)
You should land authenticated — no login prompt
Check that account access is normal (can view campaigns, billing, settings)

If you hit a login prompt, the cookies didn't transfer cleanly or the session expired during migration. Re-export from Dolphin while logged in and try again.

Don't make campaign changes yet. Just confirm session access. Changes come after fingerprint validation.

Step 5: Run Fingerprint Comparison Tests

This is the step most migration guides skip.

It's also the step that prevents bans. Funny how that works.

In both browsers (Dolphin Anty with original profile, JustBrowser with migrated profile), open these sites and screenshot the results:

CreepJS: Full fingerprint hash and trust score
Pixelscan: Detection summary and parameter breakdown
BrowserLeaks: Canvas, WebGL, AudioContext hashes

Compare the outputs. You're looking for:

Canvas hash: Should be different (different noise seeds), but both should show proper noise injection — not raw hardware hashes
WebGL vendor/renderer: Should match or be plausibly similar (same GPU family)
Audio fingerprint: Should show noise injection on both, not identical raw hashes
Timezone, language, resolution: Should match exactly

If CreepJS shows a trust score significantly lower on JustBrowser, something's misconfigured. Common culprits: timezone mismatch, incorrect hardware concurrency, or proxy IP geolocating to a different region than your timezone. We detailed fingerprint troubleshooting in the WebGL fingerprinting deep-dive.

JustBrowser's 40+ native C++ parameter patches should score comparably or better than Dolphin Anty's extension-layer approach. If they don't, your profile config is wrong — not the engine. I've seen people blame the browser when they had their timezone set to London but were routing through a Brazilian proxy. Come on.

Step 6: Parallel Operation Period (The Critical Phase)

Here's where most people get impatient and ruin accounts. I get it — you're paying for two antidetect subscriptions simultaneously, the parallel period feels like wasted time, and you just want to be done. But this part matters more than any other step.

For the next 3-7 days (longer for high-spend accounts), operate both profiles:

Morning: Log into ad platform via Dolphin Anty profile. Do normal campaign work.
Evening: Log into ad platform via JustBrowser profile. Just browse, check reports, don't make changes.

The goal is establishing the new fingerprint alongside the existing session before the old fingerprint disappears entirely. Facebook and Google track fingerprint consistency over time — they don't just check point-in-time. A sudden fingerprint change is suspicious. A fingerprint that appears alongside an existing session and gradually becomes the primary one? Normal browser update behavior.

During this period:

Don't delete the Dolphin Anty profiles
Don't make major campaign changes from either browser (pauses, budget increases, new ad sets)
Monitor for unusual account review requests or temporary restrictions

If you see account warnings during parallel operation, slow down. Extend the parallel period. The platforms are noticing the change.

This is frustrating. I won't pretend otherwise. But a two-week delay beats losing the account permanently.

Step 7: Gradual Cutover (Batch Migration)

After 7+ days of stable parallel operation on your test accounts:

Make a minor campaign change from JustBrowser (small budget adjustment)
Wait 24 hours. Check for account warnings.
If stable, make another change. Then another.
After 3 days of JustBrowser-only operation with no issues, the profile is migrated.

Now archive (don't delete yet) the Dolphin Anty profile and move to the next batch.

Batch size: Start with 2-3 accounts. After they're stable, do 5-account batches. Don't migrate more than 10 accounts per week, even if your parallel periods overlap. Yes, this takes forever. Yes, that's the point.

For teams managing ad spend alongside profile migration, ClickzProtect monitors for click fraud during the transition — helpful since you're watching accounts more closely anyway. For agencies running outbound alongside paid, VeloCalls handles the calling side while you focus on profile stability.

Common Errors and Fixes

Cause: Cookies are stale or the export captured a post-logout state. Fix: In Dolphin Anty, actively log into the account, wait 5 minutes (let session cookies refresh), then re-export. Import fresh cookies into JustBrowser.

Fingerprint trust score dropped significantly

Cause: Misconfigured hardware parameters or timezone/proxy mismatch. Fix: Check that JustBrowser profile timezone matches proxy IP geolocation. Verify WebGL vendor/renderer strings are plausible for the configured device. Run IPHey to check for IP/fingerprint consistency.

Cause: Platform flagged the fingerprint change as suspicious. Fix: Complete verification from the JustBrowser profile (establishes the new fingerprint as legitimate). Extend parallel period to 14+ days for remaining accounts. Consider that this account may have been on a watchlist already.

Proxy connection failures in JustBrowser

Cause: Different proxy authentication format or port. Fix: JustBrowser supports HTTP, HTTPS, and SOCKS5 with user:pass auth. Verify the proxy format matches Dolphin Anty's config exactly. Test with a fresh profile before migrating production cookies.

Cause: Export format mismatch or corrupted JSON. Fix: Try Netscape format instead of JSON. If that fails, manually check the export file in a text editor — corrupt exports are usually obvious (truncated JSON, encoding issues).

Next Steps

Once migration is complete:

Delete Dolphin Anty profiles: But only after 30 days of stable JustBrowser operation. Keep the cookie exports archived.
Optimize JustBrowser fingerprints: Now that accounts are stable, you can tune individual profiles for better detection scores. We covered audio and font fingerprinting optimization separately.
Set up API automation: If you're managing 50+ profiles, JustBrowser's REST API with Playwright/Puppeteer integration automates session health checks. See the API documentation.
Track analytics separately: JustAnalytics provides privacy-respecting analytics without feeding data back to the ad platforms you're staying clean on.

Migration is disruptive. No way around that. But it's a one-time cost — run it right once and you're done. Run it fast and you're re-doing it after account losses, probably with fewer accounts to migrate the second time.

The whole process is annoying. It takes too long. But every shortcut I've seen people take has cost them more than the time they saved.

Frequently Asked Questions

Will my Facebook ad accounts get banned if I switch antidetect browsers?

Possibly, if you switch mid-campaign without maintaining fingerprint consistency. Facebook tracks canvas, WebGL, and audio fingerprints across sessions. A sudden fingerprint change — even with the same cookies and IP — triggers their account-linking detection. The staged migration process in this guide uses parallel profile operation to maintain session continuity before full switchover.

Can I import my Dolphin Anty profiles directly into JustBrowser?

Not directly — there's no one-click import between antidetect browsers. You need to export cookies from Dolphin Anty (JSON or Netscape format), create matching profiles in JustBrowser with equivalent fingerprint parameters, import cookies, then validate. The profile settings (screen resolution, timezone, user agent) need manual recreation, but cookies transfer cleanly.

How long should I run parallel profiles before cutting over?

At least 72 hours for low-spend accounts, 7-14 days for accounts spending over $500/day. The goal is establishing the new fingerprint alongside existing session cookies before the old fingerprint disappears. Longer parallel periods reduce risk but cost you the subscription overlap.

What's the biggest mistake people make when migrating ad-account profiles?

Migrating all accounts at once.

Even if your process is perfect, one bad cookie import or fingerprint mismatch can flag an account. Start with 2-3 low-value accounts, run the full validation cycle, confirm they're stable for a week, then migrate in batches of 5-10.

Impatience costs accounts. I've said this three times now. I'll keep saying it.

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