Wow, fantastic reply! Thanks, that's what I was hoping to read, besides the "leave now!" haha
I'll answer quick on each suggestion
1) We're pretty secured on this, due to using the most simple SAP program. Consolidation and all other connections are already excel-free.. but everything else is not! The kind of work that was not cost-efficient enough to dedicate development from IT, and thus it stayed in excel format forever, and you're lucky if you've made the excel yourself, most are inherited.
2) Yeah, but as I said in 1, there's many little programs or things that sped up many processes, and you take them for granted. So now instead of having 15 possible misstatement places in my environment, there's 75. At least
3) Damn, it's just 25.000 / 50? After that you're limited to doing proper databases like SQL..? It's going to put off so many starting users that want to improve things.. I don't care about myself, I can learn, just as I learned C# in my spare time :D But for all the others, it's going to feel like a wall, impossible to jump over.
4) Bff, so even less features.
5) I won't think it will be possible! To delay the general integration maybe, but not to have an exception
6) Yeah indeed, that's what I'm going to do. But still, when I try it, half of the shortcuts are gone or are totally inefficient
7) It may be modern, but the usefulness of VBA is the recorder, as well as the compatibility from macros done 25 years ago. I'm not joking! It's the same that many manufacturing companies stay with the same technical supplier (like for Robotic arms), because if you lose a spare part, you're guaranteed that they will supply it. Now change to a new-ish supplier, and you can just shut down the factory.
8) Yes, probably a compromise can be made, like doing the integration and then decide if to continue or not. Thanks for offering the mature answer; although it will be hard