Same here.
Meanwhile I started the 5th attempt (no joke!) to get OH2 into same state as my well running OH1.8.3 but I have to say that the expected benefit isn’t visible at all, even worse - I’m struggling again and again with issues (Hue, Zwave, charts, slow performance, distribution of several configuration to many places, etc.).
My reason for migration was that I wanted to switch from Windows 10 machine to RPi3 in order to use the ComfoAir-binding (this is not working with the serial interface on my windows machine). My expectation was that I would struggle with the Linux stuff (to be honest: I’m not at all a fan of Linux) but at the end it turned out that this is the easy part (thanks to @ThomDietrich for his hassle free linux setup) - getting OH2 with all its new concepts into a similar state like OH1 - this is the painful thing. And I haven’t been at that point that I could start testing the ComfoAir binding.
Now, I am at that point that I try to get OH2 running on my windows machine - even when that means to go without the ComfoAir-binding but still there are a lot of issues that I also had on Linux, some I could resolve but there are also some new.
Long story short: in case a OH1 instance is running smoothly and a binding for the desired technology is available - from my point of view there is no need to migrate.
The disappointing thing is: I can’t even say whether I am too stupid or the technology is not mature enough or usability for non-techies hasn’t been considered properly or if it is a lack of documentation/tutorials. Most likely a bit of everything.