Skip to main content

Handle DB migration from old website

There’s existing deck data hanging out in some old schema in your prior website, you really ought to migrate that over as part of the initial rollout

1 comment

Log in to comment and vote

Comments1

  • Evan Farrell

    Team•

    Jun 3

    Thanks, I grouped this with the related legacy event migration feedback for product triage as HYD2-7566. If you have specific deck/player examples from the old schema that need to survive rollout, please add them here so we can validate the migration scope.