Skip to main content
Three things move: your people, your keys, and the way you set up a test. History does not. Check the second table below before you start planning, because there is no workaround for any of it.

What you need first

  • A Userplay studio with your game named and its slug claimed. Everything else depends on it, and the slug is hard to change later.
  • Your tester list as a column of email addresses. Email is the only identifier Userplay uses to match players.
  • An access key, if you want to script any of this rather than clicking through the studio.

What comes over, in order

Do these in order. Groups, rosters, and key assignments all reference players by email, so the people need to land first. Build that first playtest in the studio, not over the API. Clicking through the editor shows you which components you actually need, and Preview lets you walk the player flow before anyone else sees it.

What does not come over

If you need the old numbers alongside the new ones, keep exporting from your current tool and join the two outside Userplay. Exports gives you every Userplay dataset as a file, which is already the right shape for that join.

How you know it worked

  • The All players tab on the Players page shows the tester count you expected, with no duplicate rows.
  • Each vault’s key total matches what you loaded, and every key is badged Available.
  • A rebuilt playtest walks end to end in Preview, with no stage you did not intend and none missing.

Migrate your players

The tester list, by CSV or over the API.

Migrate your key inventory

Bring your existing keys across in batches.

Automate with the API

What the API and CLI can and cannot do for you.

Set up your studio

The first thing to get right, before anything is imported.