Antidetect browser migration and profile import

Inventory profiles and source files

List each profile alongside its business account, group, platform, login URL and proxy. Record whether the move needs an existing login session or only the account configuration. Keep recognizable source names so that a seller's store, an agency client's account or an affiliate account can be matched to the correct destination profile.

A general import uses the information in your file. It does not mean every browser exports the same structure, and changing a proprietary file's extension does not make it a supported table. Inspect the field names and records first, then prepare CSV or a supported flat JSON array. Fill missing details from your own account records instead of copying another profile's credentials.

If the file already comes from a supported source, use the relevant instructions for BitBrowser migration or AdsPower migration. BitBrowser profile JSON has its own field conversion. General spreadsheet imports use column mapping, which you should review against the file you have.

Prepare a CSV or flat JSON table

In CSV, use the first row for headers and each following row for one profile. Supported fields include name, group, platform, account, proxy, OS template, language, time zone and cookies. A profile name is required. Other missing values may be left empty where allowed, but an empty proxy field cannot recover the source profile's connection.

Flat JSON uses an array of objects with direct field values. Avoid wrapping ordinary account fields in additional nested objects. The cookies field can contain an array. A source profile number is only data in that file; it does not cause the importer to contact another application and retrieve information that the export omitted.

Download a template from Import profiles to check the expected structure. The header row below uses names the importer maps automatically; case, spaces, underscores and hyphens are ignored. Add your own profile records below it. The header alone is not an importable set of profiles.

name,group,platform,username,login_url,proxy_type,proxy_host,proxy_port,proxy_username,proxy_password,os,language,timezone

Review column mapping and row validation

Open Profiles → Import and select Choose file. For a general table, the importer matches common headers such as name, profileName, username and account. Use the First rows preview to verify that each selected column contains the expected type of data. A matching header is a starting point for review, not proof that every row is correct.

Check Account and Password separately from Proxy user and Proxy password. Confirm Login URL and Startup URLs as well. For custom or abbreviated headers, select the source column manually; mark unused columns Don’t import. Choose Next: check rows and use the reported row numbers to resolve missing names, invalid URLs or invalid proxy values.

Set Default group for rows without a group. If you lack permission to manage groups, rows whose groups cannot be created also use the default group. Groups organize profiles; access for team members must still be configured separately. Check the group assignment as part of the migration, especially when different people maintain different accounts.

Map proxy connections

In a CSV file, you can use one complete Proxy column or split the connection into Proxy type, Proxy host, Proxy port, Proxy user and Proxy password. Supported protocols are HTTP, HTTPS and SOCKS5. Keep proxy authentication separate from the website account, and do not put a provider's extraction API URL into the proxy host field.

A mapped complete Proxy column takes priority over split fields. When only split information should be used, remove the complete column's mapping before checking the preview. A complete proxy value can also reference an existing proxy library name. Confirm that the named record is the connection intended for that profile rather than relying on similar names.

A valid row establishes that the fields can be parsed, not that the connection works. After importing, test authentication, reachability and the actual exit IP. Check the region against the account's intended configuration. The proxy setup guide explains how to inspect the connection before using it for a website login.

Check device templates and cookie data

When the table does not contain a full fingerprint, the importer generates one from a device template. Available templates include Windows 10, Windows 11 and Apple silicon Macs. Choose the system type your workflow needs and review language and time zone alongside the intended proxy exit. This does not copy every underlying value from another browser engine.

If the file includes cookies, the preview shows how many were recognized. Check that they belong to the expected website and account. An imported username and password does not establish that cookies were included, and a cookie count does not establish that the session remains valid. See cookie import for supported formats and checks.

General tables do not contain complete local storage. A website may require additional stored data or another verification step, so open it and follow its sign-in process when necessary. Later transfers between your own computers can use cloud sync, but synchronization cannot recreate data that was absent from the original migration file.

Confirm the import and resume account work

Before submitting, review duplicate names, Default group and the available profile allowance. Afterward, inspect the number created, skipped and failed, including any cookie import warnings. Retry unfinished records instead of submitting the entire source again. This keeps the destination list usable while you resolve individual data problems.

1. Open a small sample and compare account details, startup URLs, device templates and exit IPs with your source records. Check the website login state for each one.
2. Assign imported profiles to the appropriate team members and confirm who will operate and maintain them. Coordinate the handoff so the source and destination are not used for duplicate work.
3. For an existing automation task, replace the profile identifiers and review the connection and response handling using the Local API guide. Verify one complete task before gradually resuming batch work.

FAQ