Customize users in the CSV file

You can customize your migrated users by applying different actions to each of them. This
lets you fix any problems with their email addresses or just modify some details. Note
that we won't change any of your original users, only the ones created in cloud as you
migrate.

Actions you can apply in this file:
- Change email addresses
- Merge any users together
- Migrate users as former users

** About the CSV file **
In the advanced experience, there is only one CSV file for all users. You can modify
existing users in the file, but you can't add or delete users. If the number of users in
the uploaded CSV file is different than in the original file, you won't be able to upload
it.

** Example CSV file **
Here's sample data that you'll see in the file:

|  UserKey  | UserName | ErrorType |    OldEmail   |      NewEmail      | Tombstone | AccountType |
----------------------------------------------------------------------------------------------------
| USER10105 |  user1   |    INV    | user1@atl     | u10105@example.com |   FALSE   |    USER     |
| USER10106 |  user2   |    INV    | user2@user2   | u10106@example.com |   FALSE   |    USER     |
| USER10107 |  cust1   |    DUP    | user@atl.com  | u10107@example.com |   FALSE   |    USER     |

What the columns mean:
 * UserKey: User key.
 * UserName: Username, the primary identifier in Server and Data Center.
 * ErrorType: Problem with the email address, either invalid, duplicated or none.
 * OldEmail: Current email address.
 * NewEmail (editable): Pre-generated email address that unblocks the migration.
 * Tombstone (editable): Controls whether a user should be migrated as Former user
   and deactivated in Cloud. The values are True or False.
 * AccountType: User type. For Confluence, it's always a regular user.

** How to edit the CSV file **
The values you can change in the CSV file are 'NewEmail' and 'Tombstone':

 * NewEmail *
 The pre-generated email addresses are always valid so they meet the requirements and
 let you migrate. Note that these emails aren't actually working and your users won't be
 able to log in with them. If you'd like some of them to keep access, change the value
 to an address your users have access to. However, in the case of active users, we
 recommend that you update their emails directly in the source (e.g. Confluence user
 directory, external directory).

 Note: If you use an email address that already exists in cloud or is shared by other
 users in this file, the users will be merged. You can use this option to merge users.

 * Tombstone *
 Change the value to 'true' if you'd like to migrate specific users as Former users.
 Such users have their activity preserved, but not the identity. Every interaction they
 ever made will be displayed under the name 'Former user'. Former users don't count
 towards your license and can't be restored as active users. If set to 'true',
 the 'NewEmail' is not used.

** Recommendations **
Here are all the options you can use in this file:
 * For users that should exist in cloud, but don't need access: use default values.
 * For users that should exist in cloud and need access: set 'NewEmail' to a working email.
 * For users that should be merged: set 'NewEmail' to the same address for all of them.
 * For users that should be deactivated: set 'Tombstone' to 'true'.