Skip to main content
Userplay matches players on email, so migrating a tester list really just means moving a column of email addresses. Use a CSV upload in the studio, or push batches over the API. Both end up in the same place: one player record per address. If the list already lives in Mailchimp, sync the audience instead. It keeps itself current afterwards, which a file cannot.

What you need first

  • Your tester list exported as a column of email addresses. Names, tags, and notes from your old tool stay behind.
  • An access key, if you are scripting it instead of uploading a file.
A player you add by email or CSV skips screening entirely. Screening only runs on people who arrive through a public link. If you want this list screened, publish a waitlist and have them join through it instead.

The playbook

1

Get the list in

Pick a route.
A CSV is faster and needs no key. The API is worth it when the list lives in a system you would rather script against.
  • Go to Players in the sidebar.
  • Open the page’s overflow menu and click Add from CSV.
  • Upload a file with a column of email addresses.
  • Confirm the column Userplay picked.
The file is parsed in your browser and only the addresses are sent, so the CSV never leaves your machine.

Adding players

Every path a player takes into the directory, including Steam.

Players

Every player command, argument, and flag.
2

Re-run anything you are unsure about

Import the same file again. The All players count will not change.
Every email resolves to one player record, whether existing or new. No need to de-duplicate your list first.
3

Sort them into groups

On the Players page, open the Groups tab and rebuild the segments you actually use.Seed playtest rosters from those groups rather than from the flat directory.

Player groups

Custom groups against backing groups, and what each one can do.

Sort players into groups

Playbook: filter the directory and save the result as a roster.

The API has no upload endpoint

The public API has endpoints with import in the path, but they do not do what the word suggests. Neither accepts a file. There is no multipart form and no CSV endpoint anywhere in the API, and the CLI’s --body-file flag takes JSON. The CSV import in the studio parses the file in your browser and then calls the same add-by-emails endpoint you would call yourself.

How you know it worked

  • The All players tab shows the count you expected, and searching a few known addresses turns them up.
  • Re-running the same import leaves the count unchanged.
  • Players you added carry no screening status, because a direct add never goes through a screen.

Adding players

Every path a player takes into the directory, including Steam.

Build a group you can reuse

What to do with the list once it is in.

Rate limits

If you are pushing a long list through the API.

API keys

Create the access key a scripted import authenticates with.

Turn subscribers into playtesters

Playbook: the same job when the list lives in Mailchimp.

Migrate to Userplay

Playbook: what order to bring everything else over in.