Help justifying migration of a test solution control GUI from LabVIEW to MATLAB/Simulink?

We are working on a multifunction motor and battery system tester with a technical college partner who has some familiarity with LabVIEW, and some with MATLAB but not with Simulink. An advisor is an old hand with LabVIEW, though getting LabVIEW enabled equipment is more difficult than decades ago, where we can enable or buy just about any needed test equipment to work with MATLAB & Simulink. The student team involved is staying away from making their preference known letting the "grey hairs" make this choice!

Do any of you have other reasons to justify a move to MATLAB & Simulink? Yes we can incrementally migrate functions through a transition, but we are at a point to specify new test kit in a new phase of the project and I need more reasons than ubiquity and broader user base to push the senior advisor to consider MATLAB & Simulink. Target audience is this SE Asia technical team and regional technical college groups as well as international small businesses working in the field.

MATLAB/Simulink Pros vs LabVIEW

• broader array of components available with MATLAB/Simulink integration into test system solution
• compiler option to generate target code
• training available local to development team (both have extensive online training)
• higher cost for LabVIEW for deploy to partners

MATLAB/Simulink Cons vs LabVIEW

• senior advisor experience and contacts with NI
• initial cost MATLAB/Simulink higher (this is up in the air, I believe educational pricing is appropriate for development budget, sr advisor uses commercial pricing)
• extended team more familiar with LabVIEW

Thanks for any feedback!

[MR Smith]

PS - one private comment was good, use MATLAB/LabView integration where LV is already in use. I will test and put that in the next phase plan!