MIT vs Apache 2.0 for open-core licensing and contributor agreements

[Mark.H]

I'm the lead developer for a small startup, and we're preparing to open-source the core library of our software under a permissive license to build community and adoption. However, we plan to keep certain advanced features and our cloud management platform proprietary. I'm diving into open source licensing to understand the legal implications, but I'm confused about the compatibility and obligations of mixing licenses, especially if community contributions are made to the open-source core. For those who have navigated a dual-licensing or "open-core" model, what are the critical considerations when choosing the initial license (like MIT vs. Apache 2.0) to ensure we retain the ability to build a commercial product alongside it? How do you structure contributor license agreements to protect the project's future, and are there any common pitfalls with dependencies that could force unintended license propagation?