Thank you for the followup Eirikur.

1) The data sources are separate OLTP databases on the same network, when I can successfully execute locally I will hand off the package to another network with different db credentials and will thus need to modify the connection manager.

2) The destination db is also OLTP

3) I don't believe the SSIS is running on a SQL Server instance, I'm not sure how I would validate that. Regardless, when I pass it off I believe it will run standalone. If it would help and it is NOT currently running on an instance I could change the strategy, I'm not sure how I would run against an instance.

I wonder since the FK constraint issue is distinct to 1 of 17 tasks, that it may be best to manage within SSIS, I dont want to over-complicate this right now - there's a potential that the need/requirement will expand where I may need to run SSIS on a MSSQL instance and become more "industrial", but Ill have a lot more insight at that time.

The second image in the below OneDrive directory illustrated the specific object Im having issue with.

https://1drv.ms/f/s!Ai9bJ2dV87SLgfwGrYuaLBK3qZgVjw

Separating tasks into several packages, though provoking... I can see the benefits. Once I get this to run I think I want to enhance the project by doing that.