Laravel comes with it's own database versioning system called migrations. Instead of writing SQL scripts you write the change you want to do in Php. For Voyager it's a bit different.

If you need to change the structure of the tables that Voyager use, you can create a migration. But that doesn't work for all the configuration you do from the admin UI. Here you need to export the content of most of the Voyager tables.

One easy way to do that, is by using a package to create seeder from an existing database. I have used "orangehill/iseed" and it's working great.

To export the relevant data:

php artisan iseed data_types,data_rows,menus,menu_items,roles,permissions,permission_role,settings --force

To override an existing database with the new version:

php artisan db:seed