I I found this article which helps you in migrating SQL Server 2008 to 2017. Hope this help you out:
https://dzone.com/articles/best-way-to-migrate-sql-server-2008-database-to-20 

This may help you out. The blog covers the causes of getting this error and the resolution around them. 
https://www.systoolsgroup.com/updates/fix-microsoft-sql-server-error-18456-login-failed-for-user/

Go through this. This may help you out:
https://blog.sqlauthority.com/2014/01/17/sql-server-fix-login-failed-for-user-username-the-user-is-not-associated-with-a-trusted-sql-server-connection-microsoft-sql-server-error-18452/

Check out how can  you enable your DAC connection in SQL Server: 
https://www.systoolsgroup.com/sql-decryptor/enable-dac-connection.html

Here are the causes of getting SQL error 824 and the solution around them:
https://www.sqlserverlogexplorer.com/sql-error-824/

I found one helpful article that discusses high availability and disaster recovery. This may help you out:
http://mstechtalk.com/sql-server-high-availability-disaster-recovery-options/

The error comes when you are trying to convert numeric or decimal value into varchar data type and the length of this variable is not long enough to hold its...

This may help you out:
https://prashantd.wordpress.com/2015/03/18/4218/

Here is the workaround to remove SQL Server error message 3013:
https://www.sqlrecoverysoftware.net/blog/sql-error-3013.html

The error appears because you try to use an IP address for the listener which is already in use. This may help you out:
https://blog.sqlauthority.com/2018/03/24/ql-server-unable-to-create-listener-msg-41009-the-windows-server-failover-clustering-wsfc-resource-control-api-returned-error-code-5057/

Check out:
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup?view=sql-server-2017

Here are the step by step process to restore database to new location. Go through it:
https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-a-database-to-a-new-location-sql-server?view=sql-server-2017

You can recover your deleted data from transaction logs. Here are the step by step process to recover your records from logs:
https://dzone.com/articles/recover-deleted-data-from-sql-table-using-transact

Here is the guide to resolve SQL error 18204. Have a look:
https://blog.sqlauthority.com/2017/05/23/sql-server-error-18204-severity-16-backup-failure-operating-system-error-1240-account-not-authorized-log-station/