So again, you need to make the determination on the path since the constraints seem to be on you and your workload. That being said, 3CX is fairly simple to install and administer as long as you follow one of two paths:
- Stay with-in the 3CX approved environment. This means OS/hosting platform, dialtone provider, handsets, etc
- Use a 3CX partner for implementation who can guide you as well as provide experience for items that may not be 3CX approved but work as good as or better than the 3CX approved options.
The other factor is what I mentioned regarding your implementation time frame. If your current system is smoking and could die any day now then you probably want to work with a partner. But if this a 6-12 month project and you'll have time to tinker then spinning up a free license and playing is a good way to go. You can still enlist the help of a partner just so you have a resource for the occasional question but otherwise you are free to work at your own speed.
If you look careful in the forums I'd venture to say at least 90% of the 'problems' aren't actual 3CX problems. They are network issues, poor design choices and how can I use 'xxx unsupported' device/feature/environment. Lots of people think that because they can save money with 3CX because it is inexpensive compared to to other PBX products and then want to pair it with 8 year old unsupported phones and free forum support. In reality they should be taking the money saved on the 3CX license and spend it on supported equipment and proper support from a partner.
Full disclosure I am a platinum partner but I am also a small business owner and straight shooter. So my opinions here are biased but not so much about putting coin in my pocket but as to doing things the right way.
Good luck!
