Switching
Moving to Argus from another anti-detect browser
Proxies and cookies come across in bulk. Profile configuration comes across by CSV. Fingerprints and anything sitting behind a device check do not, and no product in this category can move them for you.
Most "switch to us" pages imply a button that swallows your old workspace whole. There is no such button here, and there is not one in the other direction either — this industry has no shared profile format, and the two products that do export a whole profile export it in a shape only they can read. What follows is what genuinely moves, what has to be rebuilt, and the order that makes the rebuilding shortest.
The honest inventory
Five things, and only two of them arrive intact
Read this before you buy anything, not after. If the row that matters to you says rebuild, that is the real cost of moving and it belongs in your decision.
Proxies
Comes acrossThe bulk importer reads the shape every vendor hands out — host:port:username:password, with commas, semicolons, tabs or pipes instead of colons, credentials before or after the @ either way round, a scheme prefix that sets that line's type on its own, and a hostname exactly like an IP. A headed CSV works too, and a `type` column lets one file mix HTTP and SOCKS5. Paste the list you already have.
Profile rows
PartlyCSV, with the columns the importer actually reads: name, proxy, proxy mode, profile id, status, folder, tags, start URL, created date, operating system, browser version, user agent, language and timezone. That is the configuration of a profile — what it is called, where it sits, and which machine it should look like. It is not the profile's identity or its session.
Cookies
PartlyA whole folder at once. Argus reads a cookie file as JSON — a bare array, or an object with a `cookies` key — and falls back to Netscape format, then matches each file to a profile when the file name contains that profile's name. That is the shape an exported set from another tool usually already has, so the common case is: export cookies per profile, drop the folder on Argus, and the sessions come with you.
Fingerprints
Rebuild itArgus generates a coherent hardware identity per profile from the operating system you name in the CSV, and there is no field anywhere that ingests another product's fingerprint. This is a design decision rather than a missing feature: a fingerprint lifted out of one engine and replayed inside a different one tends to contradict the browser rendering it, and a contradiction is more legible to a site than a fresh, consistent identity would be.
Automations, extensions and team roles
Rebuild itNo importer exists for any of the three, and no format is shared with any other product. Extensions are re-added by Chrome Web Store ID or from a local folder, automations are rebuilt in the step editor, and a workspace's members are re-invited.
The thing we do not have
There is no profile-with-identity import, and we are not going to imply one
Two products in this comparison export a whole profile to a single file. Octo Browser writes a .octofile carrying a profile's fingerprint, cookies and proxy; Multilogin writes an encrypted archive with its fingerprint settings, cookies, saved logins and cached data inside. Both formats are theirs, both are readable only by the product that wrote them, and Argus cannot open either. Nothing on this site will suggest otherwise, and if a page ever does, it is a bug worth reporting.
Argushas no equivalent of its own to hand you on the way out, either — which is the same limitation seen from the other side, and it is listed on every comparison page here for that reason. What it does have is a CSV export that writes the importer's own column names, so a file Argus produced can be fed straight back into Argus rather than being a dead end.
The order that works
Proxies, then profiles, then cookies, then re-verify
Proxies first, because the profile CSV refers to them by connection string and the importer matches and reuses a proxy by type, host, port and username — so repeating one across forty rows does not create forty copies of it. Include the credentials: most exports from other tools leave them out, and a proxy that needs a login and has none fails its health check, which in Argus blocks the launch rather than quietly falling back to your own address.
Then the profile rows. The importer shows you the parsed file as a table and lets you fix it before anything is written, so a mangled column is caught at review rather than discovered forty profiles later. Name the operating system per row and the identity is generated to match it — platform, cores, memory, screen, timezone and languages as one coherent set, with the user-agent and its UA-CH metadata agreeing with all of it.
Then the cookies. Export one file per profile from the old tool, put them in a folder, and point the cookie importer at it. Matching is by name: a file is claimed by a profile when the file name contains that profile's name, which is the shape most exports already have. JSON and Netscape are both read.
Then expect to re-verify. A cookie restores a session; it does not restore a platform's memory of the device that session was created on. Accounts protected by a device check will ask for one, and moving a handful at a time over several days looks a good deal less like a migration than moving two hundred in an afternoon does.
Where you are coming from
What each product gives you to leave with
Read from each vendor's own documentation — the same sourcing the comparison pages use, with a link on every claim. If one of these is out of date, tell us and it gets corrected rather than defended.
AdsPower
“JSON and Netscape are both supported formats for AdsPower” Source, checked 17 August 2026.
Multilogin
A profile exports to an encrypted archive holding “Metadata (fingerprint settings)”, “Browser data (cookies, extensions, saved logins, etc.)” and cached files, and imports elsewhere. Available on Pro 50 and higher, owner only Source, checked 17 August 2026.
Dolphin{anty}
Export and import cover cookies and local storage rather than a whole profile; profiles are shared or transferred between accounts inside the product Source, checked 17 August 2026.
GoLogin
“Gologin supports profile import and export via CSV files” — configuration only: “This feature only works with profile configuration, not actual browsing data” Source, checked 17 August 2026.
Octo Browser
A profile exports to a .octo file carrying its fingerprint, cookies and proxy, importable once, at a cost of 0.5 tokens; profiles also transfer to another account in the same workspace Source, checked 17 August 2026.
Before you move anything
Four reasons not to
Argus runs on macOS with Apple Silicon and on Windows 10 and 11. There is no Linux build, no Intel Mac build and no mobile app, and several products in this category have all three. If your machines are Ubuntu, stop here.
Everything runs locally. There is no hosted API and no cloud runner, so a schedule entry whose slot passed while the launcher was shut is marked missed and skipped rather than caught up. That is the right trade for people who want nothing of theirs on someone else's hardware and the wrong one for anybody who needs profiles working while their laptop is closed.
The cheapest paid plan is $89 for 30 days, and the free plan is 5 profiles. Two products compared here start at around $10, so if you need thirty profiles and nothing else, the arithmetic does not favour moving.
And teams share one pool with no per-resource permissions and no activity log yet, which the teamwork page states in the same words. If you are moving a team specifically for governance, that is the row to check first.
Ready to run profiles at scale?
Download Argus for Mac or Windows and start free with 5 profiles.