Import profiles from a spreadsheet

A CSV or an Excel .xlsx workbook: from Excel, from a sheet or from your supplier. In a CSV, commas, semicolons and tabs are all read, the byte order mark Excel writes is dropped, and a quoted cell may hold commas and line breaks.

An old Excel workbook in the xls format and a password-protected one are not read: save the sheet as xlsx or CSV.

UTF-8, a file from Excel on Russian Windows and Unicode Text are read; for another encoding the app asks you to save the file as CSV UTF-8.

One import takes up to 1000 rows.

Download an example writes a file with the column names the importer already knows.

Name, group, scenario, fingerprint template, notes, tags and the two-factor key are matched by meaning rather than by an exact string, in several languages at once.

Each column has a This column choice: recognised ones are set, one that matches nothing stands at Not used, and you pick its field. Guessing would produce profiles that look right and behave wrong.

Two columns set to one field stop the import until you keep one.

A single proxy column in the seller's own notation is read, and so are separate host, port, protocol, proxy login and proxy password columns.

Only column names that say proxy are taken as the proxy's credentials. A bare Login or Password column in a table of accounts belongs to the account.

Latitude, Longitude and Accuracy columns are read, and so are the location columns from another program's export: the answer to location requests, location by address or own coordinates. The preview shows in its Location column what each row will get.

When a row asks for its own coordinates and they cannot be read, or they are 0 and 0, which such exports use for an empty value, this is named under the row and the profile gets "Near the proxy address". A file with no location at all gives a new profile the same.

The WebRTC columns from another program's export are read: the mode, whether WebRTC is on, whether the public address comes from the proxy, and the public address itself. The column map names them like any other column.

A value the program does not know, or an own address that is not an internet one, gives the row Proxy address, and a note under the row says why. A file with no WebRTC columns gives a new profile Proxy address too.

The first screen is a preview and creates nothing.

1. 1

   Press From a spreadsheet

   On the toolbar above the list of profiles.

2. 2

   Press Choose a file

   The file name and the number of rows appear.

3. 3

   Read the column map

   Columns not used are named and so are rows read only in part.

4. 4

   Press Create profiles

   It reports how many were made and how many proxies went to the library.

Export all opens How to export: a table comes back through this import, the ARMANOS settings file through Import. A restore keeps each profile's number wherever it can, because the number is the seed of the fingerprint.

When you are signed in the account issues the numbers instead, so some profiles come back as a different machine and the app says how many.

A script does the same through the local API: POST profile/export returns the settings of up to 100 profiles, and POST profile/import brings them back with an answer for each. A profile that came back as a different machine is marked identityChanged.

Each cookie file becomes its own profile named after the file, and its cookies go into that profile. JSON and Netscape files will do.

1. 1

   Open “Create a batch”

   On an empty list the “From cookie files” button stands right there, without this window.

2. 2

   Press “From cookie files” and “Choose files”

   You can pick many files at once.

3. 3

   Read the list

   For each file: the profile name, how many cookies, how many have already expired and why an unusable file is skipped. The line above the list says whether your plan has room.

4. 4

   Press “Create profiles”

   The result stays in the window: how many were created, where and why the batch stopped, and what became of each file.

Site data is not in a spreadsheet, so a profile from it usually starts logged out. Sign-ins travel separately: in cookie files (the section above), in a transfer file or through a shared folder.