Article

Import Website Users

« Go Back

Information

 
Solution

Follow the steps below to create a CSV file and import your users (customers or members) in a batch upload to the Users section of your Springboard. Here's a sample .csv file to give you an example of how your columns of data should look.

Tips for preparing your CSV file with your user data:

1) Review the User Profile form in your Springboard and update if needed

  • Ensure the fields for the user profile form correspond with the data you're importing. The user profile form is found in your Springboard in the Website Users section, inside My Website. Click Manage Profile in the upper right corner.
  • Depending on the data in your CSV file, you may need to make adjustments to the user profile form (or vice versa), in order to ensure the fields exist and there's a place to put each piece of data.
    • For example, if your CSV file contains separate columns for City, State and Zip, make sure the user profile form (and ultimately the forms in the portals where the profile information autofills) are using the advanced Address field and not a plain text field.

2) Include a column in your CSV file for each of your user profile form fields and subfields.

Example list: Username, Password, First Name, Last Name, Email, Company, Address 1, City, State, Zip, Country, Phone, extension, etc.

NOTES:

  • The Username and Password fields don't display on the profile form management screen (Website Users > Manage Profile), but are accounted for during the import, so the Username and Password columns and values should be first respectively, in your csv file. You can upload user data without a Username and Password, but if you include a Username, then the Password is required.
  • When using the advanced Name field, your CSV needs separate columns for First Name and Last Name, as well as Middle, Prefix and Suffix if you're using those subfields. 
  • When using the advanced Address field, your CSV needs separate columns for Address Line 1 (and Line 2 and Line 3 if you're using them), City, State/Province abbreviations, Zip/Postal code and Country* abbreviation (US).
    • A Country column with the two letter abbreviation is required for a successful import whether your Address field is required or not, and whether the Country is displaying in the profile or not. 
  • You can include column headers in your file or not, it's your choice.

Import Your Users

1) Upload your CSV File

  • In your Springboard, click My Website and then Website Users and click Import User(s).
  • CSV File: Click Browse or Choose... to locate and choose your file.
  • CSV File includes header row? Choose Yes if your file includes a column header row, so that the import does not import it as user data.
  • Click Continue and review the information on the next screen.

2) Import Settings

Users to Import confirms the number of records in your file.

Add to Group:

  • Select a specific group to import the users to, which will automatically activate their permissions for the portal that group is associated with (ex: Board Members)
  • Leave it set to None if you plan to associate them later.
  • Optional: Select Create a New Group, and enter the new group title on this screen. If you choose this option, be sure to associate the new group with a portal.

Generate new auto-login tokens? Choose Yes or No.

Delete Existing Users?

  • Do NOT delete any existing users: This leaves everything in your current users list as it is, and adds the imported users.
  • Delete users in the selected group above: Means that the users you're importing now into this group will replace any users currently associated with this group.
  • Delete ALL existing users: Means that only the users you are importing now will be in your list of users when the import is done.

Resolve Duplicate Usernames?

  • Ignore duplicate usernames during import: Means that if a username already exists in your user list, the record in your CSV file will be ignored, not imported.
  • When duplicate username is identified, update all profile fields: Means that if a username already exists in your customer list, it will be updated with the information in the CSV file. If a field is blank in your CSV file, the user record will be overwritten with that blank, meaning that if a field contained data, the data will be removed and become blank (Exception: a Password will not be removed if the password field is blank).
  • When duplicate username is identified, update selected profile fields only: With this setting, if None is selected for a field in the Profile Field Associations section below, the current value will be kept in the existing user profile.

3) Profile Field Associations

  • All of the fields of the user profile are listed here, including Username and Password. Each field has a pulldown list of the column headers in your CSV file. The first value in each column appears in parentheses as a sample of the data.
  • If your file does not include a header row, the pulldown list displays COLUMN_1, COLUMN_2, etc (in place of the headers), and the first value in each column appears in parentheses.
  • If you're importing a list of users that do not have username/passwords, select None from the pulldown list for those fields.
  • Check the mapping of the fields and import data to ensure each column of data in your CSV file is set to import to the right profile field. If a profile field is not included in your CSV file, select None for that field. Update the remaining field associations as needed. This is especially important if you are importing data for usernames that already exist.

4) Check it again. There's no batch delete option.

  • Once you've reviewed each of the field associations to ensure they're correct, click Import Users.

The imported users are now in your Users list. If you added a new group, be sure to associate the group with the appropriate portal.



Troubleshoot: If your import isn't working, double check that there are no extra spaces in your csv file. Also, make sure you have a Country column with the US abbreviation listed for all users, even if you do not have a required address field.