PowerApps Collection Logic Migration

I have two canvas apps in my PowerApps environment: a well-tested source app and a newer app that will drive automation of processes, specifically task assignments. The source app already contains several ClearCollect/Collect chains, Patch statements, and OnStart variables that work perfectly; the destination app needs the same behaviour but currently throws errors whenever I replicate the formulas.

I’m looking for someone who can:
• Identify every collection and supporting variable in the source app and migrate them cleanly into the destination app.
• Troubleshoot any delegation issues, naming conflicts, or missing data sources so the collections load without errors.
• Provide concise notes (or comments in the code) explaining what was changed so I can maintain it later.

Acceptance criteria:
– Opening the destination app triggers all collections without red X warnings.
– Task-assignment flows that depend on these collections must populate galleries and forms exactly as they do in the original app.
– All fixes stay within standard PowerApps functions; no premium connectors are introduced.

The work will take place in a shared environment; I’ll grant you temporary access and stay available on Teams for quick questions. If you’re confident with PowerApps formulas, collections, and debugging, I’d love your help finishing this migration.