I'd go a different route, now that you have backups of files and DB.
Meaning, I'd make sure I can run the site locally first. Later on, if/when needed, I'd bring the site into the project manager (e.g. to upgrade the sitefinity version for example).
I'd set up the DB in sql express (or any edition of mssql you're running). Make sure you can connect to the DB using mssql management studio.
Find the config file in your backed up site files folder that contains the DB connection string. Change the connection string to point to your local DB. (When you eventually bring up your local (dev) site, you want to prevent it from connecting to your production/hosted database.)
Move the folder with your site files to C:\inetpub\wwwroot and make sure that security for the "NETWORK SERVICE" user is set to Modify.
Launch IIS, set up a new site and make the physical path points to the folder with your site files.
I'd recommend reading through the following docs for anything I may have missed (e.g. application pools, etc.)
Start/Run site from IIS.
If the site runs, you're good.
Bring the site into visual studio for any development.
I hope this helps.