Run php artisan config:clear to clear out any stored config variablesĪnd that's it.Run php artisan migrate to make sure there are no outstanding database migrations.Make sure the storage and public/uploads directories (and all subdirectories) are writable by the web server.If your hostname (the name through which you access Snipe-IT) has changed, be sure to change that in your.Copy over your storage/oauth-private.key and storage/oauth-public.key.Copy over the directories and their contents from the storage/private_uploads directory.Copy over the directories and their contents from the public/uploads directory.env match the database name, username and password for your new target database. Make sure the database name and credentials in your new. env since your last version, as it's just typically easier than going through the example.env line by line and adding things to an existing. We recommend this if you're moving+upgrading and new things were added to the. env, or (if upgrading while moving), use the example.env for the current version and fill in the blanks, saving the revised copy as. Import your data into your target server's database.If you open your exported zip backup file, you'll see your SQL dump, and all of the files you'll need to move over to your target install. env (version 4.2 or greater only) before you do this, or copy over your. Make sure you have BACKUP_ENV=true in your existing. The easiest way to handle this is to simply run a backup through your Snipe-IT admin panel at Admin > Backups, but if for some reason that's not working for you, a regular database dump using phpMyAdmin or another MySQL/MariaDB tool should work fine too. You really only have a few things to worry about:

Moving/migrating Snipe-IT to a new server should be a pretty painless process.

Migrate lansweeper to new server