Migrations
Live players & cutover
A checklist for migrating while your game is live.
- 1Run a dry run during normal traffic to measure duration and spot conflicts.
- 2Announce maintenance and pick a low-traffic time.
- 3Shut down servers or disable saving to the affected DataStore.
- 4Run the migration and wait until every key is verified.
- 5Publish the game update that reads the new DataStore.
- 6Keep the old DataStore untouched for at least a week as a rollback path.
Rollback
Because the source is never modified, rolling back means publishing the previous game version that reads the old DataStore. Data saved to the new store after cutover is not copied back automatically.