Seems like a rather subjective question but here are some suggestions. Take them all with a grain of salt, as your situation and client situation is not, and cannot be fully described here.
Requirements drive technology choice, not the other way around. Consider the scalability requirements, maintainability (industry profesional availability and rates), etc. These are your "ilities" consider them carefully, and ask for clarification from the business where needed. Consider additional or hidden costs/savings. SQL Server comes with analysis services, integration services, and integrates well with SharePoint.
Start small and move out. Agile methodology can work wonders, even though it has its own pitfalls. Find a project sponsor, someone in the business whose needs you can meet in a timely fashion. Deliver a quick, capable and competent solution. Other business units and users will take note, and you'll get buy-in much quicker and easier than just trying to convince people with charts and promises. Start creating value as quickly as possible.
You really don't want to waterfall a massive upgrade, in a single swoop. It's extremely difficult and likely to end in failure, at least in some form. Look up some of the SAP implementations undertaken by massive companies and the lawsuits and losses that follow (just as example, not out to get SAP).
Don't be afraid of a multi-phase project. It's easier to move from somewhat disjointed individual projects that were all built off SQL Server, SSIS, SSRS, and competent, modern, design to a unified whole, in a year, when the business loves you, than from multiple languages, platforms, architects and the array of data issues that come with that.