When you copy a session to a different repository, the session uses the same database connection name and type as it has in the source folder. If a connection of the same name does not exist in the target, you can do one of the following:
Select any connection of the same type in the target folder.
Copy the connection to the target repository.
Skip the connection conflict.
If you override the lookup or stored procedure database connection in the session properties, the Copy Wizard prompts you to either copy the connection information or choose another connection. Otherwise it uses the connection name in the session properties, even if the connection does not exist in the target folder. After you copy the session, you must verify that the lookup or stored procedure database connection exists in the target folder to validate the session.
You cannot copy connection objects when you copy workflows.