It wasn't exactly planned; the new fees from cPanel were given to x10 and instead of shutting down free hosting, x10 made an emergency change to DirectAdmin. There's been a lot of catching up the admin team has done, but obviously it's not 100% there yet, and they're aware. Please just report the issues when they arise and I'll present them to the admins to be fixed.
It was kind of planned, though it would obviously not have been done if they cPanel licensing had not gone up so drastical. But the migration itself was carefully planned and the conversion process for the account was properly tested once the choice was made for DirectAdmin as the best option, it's not like it happened over night. We tried negotiating a better deal with cPanel to no avail as well.
As for the cloudflare issue, not sure what causes it, any time I take a look on the servers everything looks as it should. There may be some information on cloudflares end that could shed a light on the problem, the Ray ID that is given should correspond to an entry in the firewall section on cloudflare, only the account holder can see that information though, but it could hold a clue that could help us prevent it.
Also, make sure you do not have conflicting entries with A records for more then one IP related to the domain (I have seen it done where the new IP was added to a new A record instead of editing the existing), though that should have caused a problem as soon as the old servers went offline bit over a week ago.