How do I handle customer passwords when importing

1. If you have hashed passwords from another WordPress site:

- Enable the option "This is a hashed password from another WordPress site" when mapping the password field[1][4].
- This allows you to directly import the hashed password values without rehashing them.

2. If you have plaintext passwords:

- Disable the "This is a hashed password" option[1].
- Map the plaintext password field.
- WP All Import will automatically hash the passwords securely during import.

3. For maximum security, it's best to use hashed passwords rather than plaintext when possible[4].

4. The User Import Export plugin can handle both plaintext and WordPress hashed passwords in the same import file[4].

5. If migrating from a non-WordPress platform (e.g. PrestaShop), the passwords likely use a different hashing method and cannot be directly imported[4]. In this case, you may need to reset passwords for all users.

6. When importing, you can choose whether to:
- Send "new account" emails to new customers
- Send password reset emails to existing customers being updated[5]

7. For large imports, consider disabling email sending during import and sending a mass "reset password" email afterwards instead.

8. Always back up your database before performing a customer import, especially one involving passwords[3].

The most secure approach is to use hashed passwords exported from another WordPress site when possible. For plaintext passwords or passwords from other platforms, having users reset their passwords after import is the safest option. Carefully consider the email notifications you send during and after the import process.