Skip to content

From API key to verified migration.

No scripts inside your game, no Studio plugin. Everything runs over Roblox Open Cloud.

Four steps. No scripts in your game.

  1. 01

    Connect Open Cloud

    Paste an API key with DataStore permissions. It’s encrypted at rest and never shown again.

  2. 02

    Pick source & destination

    Choose universe, DataStore and scope on both sides — same experience or across experiences.

  3. 03

    Dry run

    See how many keys move, which already exist and what your conflict rule will do.

  4. 04

    Migrate & verify

    Run the job, watch progress live, and retry only the keys that failed.

See it in action

A real recording of DataBridge: connect Roblox, add DataStores, dry run, migrate and verify — in 90 seconds.

What happens to every key

Each key is processed independently with a checkpoint, so a job can pause, resume or retry only the keys that failed — without redoing the ones that succeeded.

  1. read source
  2. transform
  3. check conflict
  4. write destination
  5. read back & verify
MIGRATION · job_7f3a4,512 / 10,000
SOURCEuniverse/111111 › PlayerData_V1 › global
  • Player_10482231read
  • Player_10482237read
  • Player_10482290read
  • Player_10482301read
  • Player_10482318read
DESTINATIONuniverse/222222 › PlayerData_V2 › global
  • Player_10482231verified
  • Player_10482237verified
  • Player_10482290skipped · exists
  • Player_10482301writing
  • Player_10482318pending

Safe defaults, not settings you have to remember.

  • Source is read-only

    DataBridge never deletes or edits your source DataStore.

  • No overwrite by default

    Existing destination keys are skipped unless you explicitly confirm overwrite.

  • Keys stay on the server

    API keys are encrypted with AES-256-GCM, masked in the UI and never logged.

  • No cookies, no scraping

    Only the official Roblox Open Cloud API — never your account session.