Leaving Dolphin Anty: Moving Your Team's Profiles to JustBrowser

11 min read

Moving a portfolio of profiles between multi-account browsers sounds like an export and an import. In practice a careless switch can leave a team locked out of a client's ad account mid-campaign, with a verification prompt going to the phone of someone who is out of office.

Most migration guides skip the unglamorous parts. This one covers a staged process for profiles that matter: ones attached to ad accounts and storefronts you own or operate with the owner's permission, where a login problem costs a day of work.

What You'll Have at the End

A working migration workflow that moves Dolphin Anty profiles to JustBrowser without losing access to anything. This guide is for accounts you own or operate with the owner's permission; it is not a way around a platform's rules or a restriction. You'll keep old and new profiles side by side during the transition, check each new profile for consistency, and cut accounts over in batches once everything works.

One thing to accept up front: to every platform, JustBrowser is a new browser. That's fine. The honest response to a "new browser" check is to complete it as the account owner, not to make the new browser pass for the old one.

This isn't quick. Plan for 2-3 weeks from start to finish for a 20-account portfolio. Faster than that and you have little time to catch a mistake before it affects a live account.

Prerequisites

Before starting:

  • JustBrowser account: the 7-day trial works for testing (unlimited profiles, card required); after that it is $9.99/month or $99.99/year. Start the 7-day trial.
  • Dolphin Anty access: 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, because too many variables make problems hard to trace.
  • Low-risk test accounts: 2-3 lower-stakes accounts, so any problem hits your least important ones first. Not your best performers.
  • A test page open: BrowserLeaks shows what a profile reports. You'll use it repeatedly.
  • Platform access for each account: The recovery email, phone and 2FA device for every account, in hand before you start, with the person who holds them available.

Step 1: Audit Your Dolphin Anty Profiles

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

  • Which account it holds, and who owns that account
  • Proxy (type, host, port, authentication)
  • Operating system the profile reports
  • Timezone (offset and IANA name, e.g., America/New_York)
  • Language (primary and accept-language header list)
  • Screen resolution your team works at (width × height)
  • Who verifies logins for that account: whose phone or authenticator gets the prompt

Why document this manually instead of relying on export? Because you're not importing into JustBrowser; you're creating new profiles with the same working setup. There's no need to copy GPU strings, CPU core counts or memory values: JustBrowser generates those to match the operating system you pick, and copying the old values wouldn't change the fact that it's a new browser.

Save screenshots of the BrowserLeaks results for each profile. You'll use them to check that the location, timezone and language carried over.

Step 2: Export Cookies from Dolphin Anty

In Dolphin Anty, export cookies for each profile in JSON format. Most multi-account 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 log out of accounts before exporting. Cookie export should happen while sessions are active. If you log out first, you're exporting dead cookies and you'll have to re-authenticate anyway.

Step 3: Create Matching Profiles in JustBrowser

In JustBrowser, create a profile for each one you documented:

  1. Operating system, timezone and language: Match what you documented. A timezone that disagrees with the proxy location is a common cause of confusing behaviour.
  2. Resolution: Match the screen size your team works at.
  3. Everything else: Let JustBrowser generate it. The engine keeps graphics, audio, font and hardware values consistent with the operating system you picked, and the browser version follows the engine, which is patched on every upstream Chromium release.
  4. Proxy: Same proxy you were using. Same authentication. Same rotation settings if any.

Don't try to change or "improve" the working setup during migration. You're trying to maintain continuity, not optimize. Save the tweaking for after accounts are settled on the new platform.

For teams doing this at scale, JustBrowser's local 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.

Then test session validity:

  1. Navigate to the ad platform (Facebook Business Manager, Google Ads)
  2. You should land authenticated, or be asked to confirm the login
  3. Check that account access is normal (can view campaigns, billing, settings)

If you hit a login prompt, the cookies didn't transfer cleanly, the session expired during migration, or the platform wants the owner to confirm the new browser. Sign in normally and complete the verification, or re-export from Dolphin while logged in and try again.

Don't make campaign changes yet. Just confirm session access. Changes come after the consistency checks.

Step 5: Check What Each New Profile Reports

This is the step most migration guides skip. It shows whether the new profile is set up the way you intended.

In the JustBrowser profile, open BrowserLeaks and check:

  • IP and location: the exit IP, country, city and timezone, against the screenshot from Step 1
  • WebRTC: no address other than the proxy's
  • Language, resolution, platform: should match what you set
  • Graphics and audio values: these will differ from the old profile, which is expected, but each should be stable across launches

If anything is inconsistent, something is misconfigured. Common culprits: a timezone mismatch, or a proxy IP that geolocates to a different region than your timezone. A typical mix-up is a timezone set to London with traffic routed through a Brazilian proxy. We covered how the timezone and the proxy relate in timezone consistency for proxied profiles.

Step 6: Parallel Operation Period

Here's where teams get impatient. You're paying for two subscriptions at once and the parallel period feels like wasted time. It's what keeps you from being locked out.

For the next few days, keep both profiles:

  1. Do your normal campaign work from the Dolphin Anty profile.
  2. Use the JustBrowser profile to go through every screen you rely on: reports, billing, settings, each client's assets. Don't make changes from it yet.

The goal is to confirm that the new browser works for every login, report and billing screen before the old one is archived. Platforms often ask the legitimate owner of an account to confirm a login from a new browser, and having the old profile still available means you are never locked out while that happens.

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), so that if something does go wrong you know it wasn't a campaign edit
  • Watch for verification requests or notices from the platform, and complete them through the platform's own process

If a platform restricts an account during the migration, stop migrating that account and use the platform's own recovery or appeal route.

Step 7: Gradual Cutover (Batch Migration)

Once your test accounts work fully from JustBrowser:

  1. Start doing normal work from JustBrowser, beginning with small changes such as a budget adjustment
  2. Confirm that edits, reports and billing all behave as they did
  3. After a few days of JustBrowser-only work with no problems, 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 done, do batches of 5. Batches keep a configuration mistake from reaching every account at once.

JustBrowser's team features help here. Team seats are free, and a seat can run the profiles shared with it, with view-only or launch permission, so the people who work each client can open the migrated profile without you passing around logins. Each person still signs into each platform with their own credentials.

For teams managing ad spend alongside profile migration, ClickzProtect monitors for bot clicks on your campaigns during the transition. For agencies running outbound alongside paid, VeloCalls handles the calling side while you focus on the migration.

Common Errors and Fixes

"Your session has expired" immediately after login

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. Or simply sign in from the JustBrowser profile and complete any verification.

Profile values look inconsistent

Cause: A timezone/proxy mismatch, or hardware values edited by hand. Fix: Check that the JustBrowser profile timezone matches the proxy IP's location. If you edited hardware values by hand, regenerate the profile's device settings so they match its operating system again. Use BrowserLeaks or the app's proxy checker to confirm the IP, location and timezone agree.

Account prompted for identity verification after JustBrowser login

Cause: The platform asked the account owner to confirm a login from a new browser. Fix: Complete verification from the JustBrowser profile, which confirms the new browser as yours. Extend the parallel period for remaining accounts. If verification keeps failing, use the platform's own account recovery or appeal route.

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 (and encrypted).
  • Tidy the settings: Now that accounts are settled, you can adjust individual profiles.
  • Set up API automation: If you're managing 50+ profiles, JustBrowser's local 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.

Migration is disruptive, and it is a one-time cost. Run it carefully once and you're done.

Frequently Asked Questions

Will my ad accounts ask me to verify if I switch browsers?

They may. Platforms commonly ask the account owner to confirm a login from a new browser or device, whatever tool you use. A staged migration keeps the old profile available while the new one is confirmed, so you are never locked out of your own account. Complete whatever verification the platform offers, and if an account is restricted, use the platform's own appeal and recovery route.

Can I import my Dolphin Anty profiles directly into JustBrowser?

Not directly. There's no one-click import between multi-account browsers. You export cookies from Dolphin Anty (JSON or Netscape format), create a JustBrowser profile for each one with the same proxy, operating system, timezone and language, import the cookies, then check the results. JustBrowser generates the rest of each profile's identity consistently, so there's no need to copy the old profile's hardware values.

How long should I run parallel profiles before cutting over?

Until every login, report and billing screen works from the new profile and any verification the platform asked for is done. For most accounts that's a few days. The point is to keep access while you confirm the new setup, not to wait out the platform. Longer parallel periods cost you the subscription overlap.

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

Migrating all accounts at once. Even with a good process, one bad cookie import or settings mismatch can leave a team locked out of a login until it is fixed. Start with 2-3 low-value accounts, run the full check cycle, confirm everything works, then migrate in batches of 5-10.


Try JustBrowser

A multi-account browser for teams, built on a custom Chromium engine, not an extension. Each profile is its own browser with its own cookies, storage, proxy and 40+ browser settings, kept consistent with each other. Local REST API + CDP 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

Tags
  • dolphin-anty-migration
  • multi-account-browser-migration
  • ad-account-profiles
  • facebook-ads-accounts
  • google-ads-multi-account
  • 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