Upgrade SSIS packages
Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.
Plenty out on the internet re this issue. A search in your favourite search engine would yield a number of results.
Hopefully you have everything in source control, if not go and do it now before anything else.
In a nutshell, install the right version of Visual Studio, the right version of SSDT, upgrade the packages, deploy and test, fix deploy test, rinse repeat until all issues are resolved.
If i have a SSISDB backup and restore to new server, it sounds good or not.
Never tried it, personally I wouldn't try it either, don't know what will be missing from the SSISDB database between a 2014 version and a 2017 version.
Source control, upgrade, redeploy is how I have always done it and not had no issues.
It's not listed as an "upgrade" option on the MS Docs (https://docs.microsoft.com/en-us/sql/integration-services/install-windows/upgrade-integration-services?view=sql-server-ver15), so if you want to do it that way I would proceed with caution
Furthermore, make sure that you have the encryption password for the SSISDB. You'll need that to fully restore the database elsewhere. Without it, you won't be able to decrypt anything. As @anthony.green mentions, using source control and a deployment process is a cleaner way to go IMHO.
18 People are following this question.
ssis card number check
SSIS 2012 For Each File treats .zip file as a folder
File System Task SSIS
ssis scheduled job on ssas fails on excel connection
Kill and Fill strategy