Assemble supports importing users, adding notes or touchpoints and address book entries from CSV files.
Example CSV files for each import type are available for download below should you be manually generating imports.
Where working with exports from other systems there is no need to match the export CSV files to the examples, i.e. field names or order, as the import process allows for field mapping. However the system will use the first row for column headings (to support mapping), so this should be added if it is not included.
To support import planning please download the excel mapping template. This contains all the available fields and related options for each import type.
Importing data from CSV
The process is identical for all imports, but fields and options vary depending on the type of import being run. See below each import type section for more details.
Imports are available from the admin menu under bulk actions. The page will show any running, or previously run imports and you can click on these to view status/history.
As a file is loaded the system will analyse the file, using the first row as column headers for the mapping process. Where an import is being repeated, the system will remember fields that were previously mapped and pre-populate the import tool.
The headers will be listed on the screen with a dropdown beside each for selection of the related Assemble field. Selecting nothing will ignore the field on import.
The unique identifier when selected will use the related field to match the existing record for updates (e.g. User ID). If none is selected the system will perform a basic check for email, or first name/last name before creating a new user.
The final field on the import allows you to name the import if desired. This is just for reference.
Once triggered an import runs as a separate process in the background. While you can monitor from the page (which will live update), this is not required, as the system will trigger a notification email once the import process has finished.
Progress will be shown on the header, and errors (by default) shown on the detail pane. You can change the view to show All, completed or Not processed rows using the filter button.
On completion, each successfully imported item will show a view link allowing you to check the imported data if desired. Please allow up to 24h for the data to be aggregated to the organisation statistics.
Error items can be corrected and re-run in line, or corrected in the CSV and re-imported in case of large numbers of issues.
Imports cannot be "undone" easily. Please carefully validate import files before loading large volumes of data.
Imported users will be checked against the unique ID, email and first/last name match before a new record is created.
User imports must meet the requirements below to create a user:
- Must include role and role start date, the end date is optional but must be after the start date.
- Must include the related team and manager for the role.
* Note where a role has an end date in the past, users will be made inactive (if no other active role remains) but this may take up to 24 hours to show.
Only one role can be imported with a user, for users with multiple roles add these by repeating the import of the user as an update with the additional role. Each additional import will add another role based on the unique ID. Is best to try to use UserID where possible to ensure a match with additional roles. This can be obtained either in the system or by exporting the imported users to obtain a list for lookup.
- Unique Identifier can only be set to User ID, Email Address or any custom field that has been marked in its setup as 'unique'.
- For both custom fields and training, these must be configured manually in the system prior to the import to be available for mapping.
- When importing to a custom field ensure the importing user has access to write to the field and your imported data matches what you have configured as acceptable values for the custom field.
- When importing training you only import completion date (where relevant), as what training is needed is configured by role, not user. Ensure the training mapped is relevant to the role you are importing.
- When importing diversity data for any field containing the word "other" the other category can also be provided. For example, if for "Nationality" column the value provided is "other", then provide a value for "other nationality" column.
Touchpoints can only be imported to existing volunteers and the volunteer needs to be identified by the UserID created by Assemble. This can be seen on a users record or exports of users from Assemble.
- On user - This is the ID of the user you wish to add the touchpoint on/to
- Author - This is the ID of the user who should be shown as writing the touchpoint, if not specified this will default to the user performing the import.
Notes can only be imported to existing volunteers and the volunteer needs to be identified by the UserID created by Assemble. This can be seen on a users record or exports of users from Assemble.
- On user - This is the ID of the user you wish to add the note on/to
- Author - This is the ID of the user who should be shown as writing the note, if not specified this will default to the user performing the import.
The address book import will default to all users, but can also be imported on a per-user basis where specific addresses are limited in use. To limit to a user you must specify the UserID from Assemble in the import.
The name field specifies what can be searched on, for example 'Your Name HQ'. Latitude and longitude (decimal degrees) can be provided in lieu of an address to pinpoint a location. If not supplied the address will be used via google to translate to a location.