Question: I wanted to know the utility of carrying out a conversion in project connection in the connection managers in ssis

[![enter image description here](https://i.stack.imgur.com/NanDj.png)](https://i.stack.imgur.com/NanDj.png)

Answer: 
Project-level connection managers allow you to define the data source connection once and use it in all packages that are part of the project. 

You can create a new project connection by right-clicking on the Connection Managers node shown above, 

[![enter image description here](https://i.stack.imgur.com/08oNm.png)](https://i.stack.imgur.com/08oNm.png)

Project-level connection managers allow you to set up a connection manager on the project level. This means that you can define a connection for the whole project and use it in all packages that are part of the project.
When you convert a package connection to a project connection it can be used by any number of packages in the project without having to manage changes to them individually. This has a couple of advantages:

1. You can see how many different connection your project has from looking at the project and not having to open and look at every package.
2. You can change a connection string in your project connection manager and know it will make all the packages work towards the new source or destination.
3. You can make the project connection manager's connection string a project parameter, allowing the entire project to be reconfigured without redeployment by just changing the parameter sent in when executing any package using the connection.
4. To build further on 3, you can set up one or more environment configuration to the deployed solution allowing you to select the parameter to be sent to the project during execution and have the same package work different environments without redeployment while also keeping track of which configuration does what.

For example in one of my installation if some source system decides to move to a new server, I just open my production configuration and paste in the new connection string for the value that is connected to the affected project parameter representing the connection string of the project connection. I can still keep the testing configuration since it has a different source which hasn't moved.