Skip to content

Importing a roster

A group’s owners and admins import a roster from People → Roster → Import a file. The file can be a CSV or an Excel (.xlsx) file of up to 1,000 rows, from Troop Web Host, another system or your own spreadsheet. Upload it as it is: you don’t need to rename its columns.

Nothing changes on the roster until you press Import the file at the end.

Choose the file, or drop it on the page. An old Excel file (.xls) can’t be read; save it as .xlsx or .csv first.

Each row is an adult, a youth with their parents (guardians), whichever a column says, or from their age:

  • A column that says: “Adult or Youth”, “Member Type”, or a yes or no such as Troop Web Host’s Adult column (Y or N).
  • From their age: under 18 is a youth and 18 or over an adult, by an Age column in years or a birth date. A row with neither is left out. Grouperly picks this when the file’s Age column has numbers.
  • Someone already on the roster: for a file that only adds to the people you have, such as Troop Web Host’s Emergency Contact List. Each row is found as an adult or a youth, whichever they are on the roster, and no one is added: someone it can’t find is left out. Grouperly picks this for a file with emergency contacts and no emails.
  • When the file has parents’ columns, each row is a youth.

What each column is: Grouperly suggests where each column goes from its header, and you can change any of them.

  • A tick means Grouperly knows the header: “First Name”, “Cell Phone”, “Address 1”, “Date of Birth”, “BSA Member ID”.
  • Check marks a guess from the header’s words. Pick something else in the menu, or press Looks right.
  • Parents’ columns on a youth’s row, such as “Parent 1 Email”, “Parent 2 Cell Phone” or “Mother’s Email”, come in as that youth’s parents and are linked to them. Up to three parents a row.
  • A row for each scout and parent, such as Troop Web Host’s Scout Parent Cross Reference: “Scout” is the youth’s name, “Parent/Guardian” is Parent 1’s, and “Relationship” is how Parent 1 is related to them. The Phone and E-mail columns after the parent’s name are guessed as the parent’s, so check them. A scout on several rows is one scout, with every row’s parent.
  • Several emails or phones in one cell are read, split by semicolons: “H: 555-0100; C: 555-0101”. A number’s H:, C: or W: says whether it’s a home, cell or work number, and the cell number is kept first. Email #2 and the extra emails help find the person. The first email is theirs and the others are kept as other emails, which Grouperly never sends to. The cell number is their mobile, and a home and a work number are kept beside it.
  • Age can be a number of years: 13 or over is 13 to 17, otherwise Under 13. A birth date, when there is one, decides instead.
  • Their whole name and gender: “Prefix”, “Middle Name”, “Suffix”, “Nickname” and “Gender” (F, M, Girl, Boy, Another) are read too.
  • Your group’s subgroups, such as dens, patrols or teams, can be filled from a column: by a subgroup’s name (“Patrol Name”), or by what its type keeps, such as a den’s rank (“Den Type”) and its number (“Den Number”). Two columns can say one subgroup.
  • Your group’s roles can be given from a “Position” or “Leadership” column, if you can give roles. Otherwise the column can go to a person’s title, as free text.
  • Emergency contacts, up to three a row: “Emergency Contact 1”, “Emergency Contact 1 Relationship”, “Emergency Contact 1 Cell Phone”, “EC2 Email” and the like. Each contact’s phone columns are read, the cell number first.
  • Your group’s fields can be filled from a column too: Member ID, or a field of your own.
  • Don’t import leaves a column out.

Grouperly remembers your choices in this browser. The next file with the same columns starts from them.

Before anything changes, you see who in the file is new, who’s already on the roster, and what the file would fill in.

Someone in the file is the same person as someone on the roster when they have the same:

  • email, any of theirs in the file;
  • member number (Member ID), ignoring spaces and leading zeros;
  • name and birth date. Names are compared without capitals, accents or a Jr., and a nickname counts as a first name;
  • name and phone, for an adult, any of their numbers in the file;
  • name, for a parent already listed for that youth;
  • name, for a youth whose parent in the file is already on the roster as their parent.

When the name alone matches, you decide. Is this the same person? asks about each one: Same as … or Someone new. Where there’s one obvious choice, it’s marked suggested. In a file of people already on the roster, Someone new is Not them: leave out.

Two people with different birth dates or member numbers are never taken to be the same person.

Family emails: a youth’s row with a parent’s email links that parent to the youth, and the email stays the parent’s. Two adults can’t share one email on the roster, so the second is skipped: add them with an email of their own.

Each subgroup the file names gets a list of its own, such as Patrols in this file or Dens in this file, with where its people go and why. Grouperly looks for, in turn:

  • the one with that number, for a type that keeps one, like a den. A den keeps its number as its name and rank change each year, so next year’s file still finds Den 3;
  • the one with that name, or that name with the type’s after it: “Hawk” is Hawk Patrol;
  • the one with that rank, where it doesn’t have a number yet, which the file then fills in.

If there isn’t one, it makes a new one, such as Bear Den 7. Pick another one in the menu, Make a new …, or Don’t import.

Roles in this file lists each role the file names, and which of your group’s roles it is.

  • A name that’s only nearly the same, such as “Asst. Senior Patrol Leader” or “Unit Treasurer”, is marked Check.
  • A role your group hasn’t got waits for you: Add it as a new role, or Don’t import. A new role comes with no permissions.
  • A role held in a subgroup, like a Patrol Leader, is held in the patrol the file puts them in.
  • A file fills in what’s blank, and never changes what’s already on the roster. For example, a phone, an address, a birth date or a Member ID.
  • Anything it says differently is listed under Kept as they are on the roster, with what’s on the roster and what the file says. Download the list and fix any you want on the person’s page.
  • An address stays together: a city and ZIP code from a different street aren’t mixed into this one.
  • Subgroups, like dens and patrols: someone is put in one only if they’re in none of that type yet. A different one in the file is listed, not moved.
  • Roles are given, never taken away. When the file names someone else for a role that takes one person, it’s listed for you.
  • Tags in the file are added to the ones already there.
  • A parent’s relationship (Mother, Guardian) is filled in where it isn’t said yet.
  • Active or inactive (a Standing or Active or inactive column): someone the file adds comes in as it says. Someone it adds as inactive is one of your group’s alumni, and hears Alumni news until someone chooses. Someone already on the roster stays as they are, and a different value is listed. Alumni are matched like anyone else, and stay alumni. See Your group’s alumni.
  • The alumni’s history: Why they left (aged out, moved…), Years with the group (1985–1992), and With the group from (year) and until (year). Blank ones are filled in. To bring in a whole file of past members, tick Everyone this file adds is one of the alumni under Each row is. See Bring in your group’s past.
  • Emergency contacts are filled in for someone who has none. Someone who has some keeps theirs, and the file’s are listed if they’re different. The same people in another order aren’t a difference. A contact who is on the roster, found by their email, their name and phone, or as the person’s parent, is linked to their roster entry. Anyone else is kept as typed, and one with no phone or email is left out.

You see how many were added, filled in and already up to date, the subgroups filled and made, the roles given and added, and what’s left for you: what was kept as it is and what was skipped. Both can be downloaded.

A new youth with no age, age group or birth date comes in as Under 13. Edit any who are 13 to 17.

Import one file, then the other: for example Troop Web Host’s roster, then your unit roster from another system. Each fills in what the roster doesn’t have yet, matched to the same people, so nobody is added twice. The first file to bring in a value keeps it. If the second says something else, it’s listed for you.

If someone still ends up on the roster twice, say with a different name and email in each system, merge them on the Roster.

A roster downloaded from People → Roster → Download has a Grouperly ID column at the end. Edit the file in a spreadsheet and import it back. Its rows are edits: they replace what they say. Tick Emergency contacts when you download to edit those too: a row’s emergency contacts in the file replace the person’s. A row for someone you’ve merged since you downloaded only fills in what the person they were merged into doesn’t have.

  • A blank cell clears nothing.
  • An email, whether someone’s an adult or a youth, and whether they’re active or inactive (the Standing column), are changed on the person’s page, not by a file.
  • A change of access goes by the usual rules: only an owner makes someone an owner.
  • An adult with no email who doesn’t match anyone on the roster. Adults are added by their email. One of the alumni is the exception: they can come in without one.
  • A youth row with no name.
  • Health form dates, when you lead the group from a group above. Only the group’s own owners and admins change them.
  • A field kept by an add-on: only the add-on changes it.