If your contacts already live in a spreadsheet or another system, don’t re-type them: the import tool brings in an unlimited number of records in one go, families included.
Importing your database
One import per set of people
An import can’t update people who are already in the database: once someone is in, a second import won’t change their details (though you can delete the imported records and start again). So take your time preparing the file and getting every column right before you run it; almost all import problems come from the data, not the tool.
-
Log in to your web office, go to the top group and open the Members tab. Under ‘Tasks’ you’ll find ‘Import users from a file’ and, if your people are grouped into families, ‘Import users and families from a file’.
-
Before importing, open your chosen option and use the two links there: ‘Import file column details’ tells you every field the import accepts and the exact format each one needs, and ‘Download a sample CSV file’ gives you a template that includes any custom fields you’ve set up.
-
Prepare your data as a CSV file (TSV also works). First name and surname are required; any other column can be left blank, though gender is worth including if you know it.
-
Run the import: choose to start a new import, select your file and format options, then map each column of your data to the right field. Mandatory fields show in red, and columns you don’t want can simply be left unmapped.
-
The data is checked and any errors summarised. If several rows have problems, export the file with the error descriptions, fix them in your spreadsheet, and re-import; that’s quicker than fixing rows one at a time.
-
Review the summary of how many contacts were imported and click ‘Finish’. Your new people are on the Members tab.
Good to know
-
The users-and-families import uses two files, one for people and one for shared family details like address and home phone, connected by a Family ID column in each. It stores the address once per family, which makes future editing much easier.
-
Passwords can’t be imported; people receive a link to set their own when their login is enabled.
-
Extra information like DBS expiry dates needs custom fields set up before the import so they appear in the mapping step; custom fields have their own guides in Site Settings. Custom-field data must come in with the main import, not as a later update.
-
Set the rota reminders field to ‘on’ in your import file; if it’s left unset, imported people can end up with reminders switched off without anyone realising.
-
Record people’s consent to hold their data before importing it; the import is the moment your database inherits your data protection obligations.
Still stuck? We’re real people.
Raise a support ticket and our UK team will get back to you.
Contact support