How to move a hundred profiles out of a spreadsheet in an evening

A row usually carries the account name, a group or a project, a proxy address and a note. Next to them sit the 2FA key, the tags and a word about the operating system. The From a spreadsheet button above the profile list opens Import from a spreadsheet and reads all of it as it stands.

That is exactly what a profile needs in order to open and sign in. Renaming columns for the move is not part of the job.

1. 1

   Name and group

   The profile name and the group you will later find it in.

2. 2

   Proxy

   One column in the seller's own notation, or separate columns.

3. 3

   The sign-in key

   The 2FA key, if you already have it written down.

The worst outcome here is not a refusal but a quiet success. A hundred profiles appear, look correct, and carry somebody else's name next to somebody else's proxy.

A column shifts over small things. A semicolon instead of a comma, a quote inside a cell, a line break in the middle of a note: any of those moves everything standing to the right of it.

The app matches a column by meaning rather than by an exact string. Name, profile name, Название and имя профиля all mean one field to it.

Case, spaces, underscores and dots in a header change nothing. The app matches thirteen fields this way, and the header itself may be Russian, Ukrainian, Spanish, German, Polish, Turkish, Japanese, Chinese, Korean, Thai, Arabic or Vietnamese.

A column the app did not understand is named back to you and left aside. Guessing it is out of the question: a quiet guess is that very shift by one column.

A proxy line from your seller does not need rewriting. The app reads five ordinary shapes as they are, and a label after a pipe too: a city name, or the link that changes the address.

There are four kinds of connection: a plain proxy, the same one encrypted, socks5, and an exit through your own server over SSH. The app takes an empty kind column for a plain proxy, because that is how the column is usually filled.

A named but unknown kind is a refusal on that row. A quiet downgrade to a plain proxy would mean you think you go one way while you go another.

Vendors spell the connection kind differently: socks5 and socks5h mean one and the same thing, and the program reads both as socks5. It does not treat the spelling difference as an error, because one and the same path stands behind it.

socks4 is a different path, and the program does not support it: such a row gets a refusal naming the reason rather than a quiet downgrade to socks5 or to a plain proxy. A bare socks with no number the program reads as socks4 and refuses too, and the refusal suggests putting socks5 if the vendor offers it. A refusal on a row is cheaper than a profile taking the wrong path.

In a table of accounts the Login and Password columns belong to the account: to give them to the proxy, name the columns Proxy login and Proxy password. The address and the port, though, are recognised by bare names too: IP, Host, Server, Address, Port. If your IP column is the address an account was registered from, rename it, or it becomes the proxy.

The difference is not cosmetic. An account password taken for a proxy password would go to the proxy provider on every launch, the real proxy password would be gone, and the host would answer 407.

So the app does not attach the bare words login and password to the proxy at all. Your account password stays in your spreadsheet and never moves into the profile.

The 2FA key usually sits in the same spreadsheet, next to the password. It travels with the row, so you do not set the sign-in up a second time.

An otpauth link with its own settings travels whole: the number of digits, the length of the step and the algorithm. The defaults are six digits, thirty seconds and SHA1, and a default may never stand in place of your settings.

A key that cannot produce codes is named back to you and never stored. A wrong code fails the sign-in, and a few failed sign-ins lock the account.

The whole path is five steps, and the check sits between the fourth and the fifth. That is the one place worth five minutes of your time.

Row numbers are the ones you see in your own spreadsheet: the header is line one, the first profile is line two. You will walk to the trouble by line number, not by a count of profiles.

1. 1

   Download an example

   Its columns are named the way the app expects them.

2. 2

   Put your own rows in

   The order of columns is yours, and nothing needs renaming.

3. 3

   Choose a file

   You are shown which column became which field.

4. 4

   Check the first five

   The first five rows are shown as values, not as column names.

5. 5

   Create the profiles

   Rows with trouble can be skipped or created without the broken part.

A real spreadsheet has blank lines between blocks, and the program skips them. The number does not shift: a refusal on line thirty of the file is called line thirty, however many blank lines stand above it.

A row broken by a line feed inside quotes is counted the same way: it takes two lines of the file and gets one number. You will go to the trouble by the number you see in your own spreadsheet, not by the count of accepted profiles.

A hundred profiles is not always a hundred slots. The free plan holds two, and the Professional steps go 10, 20, 50 and 100 profiles, Business starts at 200 and reaches 1000, and Enterprise takes 5000 and up.

A row past your quota hits a refusal and stays in your file. So the step is worth choosing before the import rather than after the hundredth row.

A group from the column is created for you, and case does not make a second one: Sales and sales are one group. Proxies from the file land in your shared ARMANOS library, and a duplicate means the address together with the login: one host with per-session logins lands as many rows as there are logins in the file.