Post Published on September 19, 2013.
Last Updated on April 29, 2016 by davemackey.
I finished migrating my most important sites off Bluehost and decided the load would be light enough that the rest could run on Bluehost’s shared hosting. I was planning on staying around for Bluehost’s shared hosting and keeping side projects on this host. I was informed that there was no migration path from VPS to shared hosting. Maybe they told me this when I signed up – probably – but it was quite the shock.
I asked what I’d need to do to get down to a shared hosting plan. They said I’d need to cancel my account and then recreate it. Essentially, I’d have to offload absolutely everything onto my local computer, then reupload and reconfigure everything.
Not what I wanted to hear, but I gave it a try. I canceled the VPS expecting to be able to instantaneously reorder the shared hosting…but that didn’t happen.
Having experienced more than a few IT transitions that haven’t gone as smoothly or quickly as desired, I had done this during the night hours – so I’d have time to work out any kinks that might arise…
Unfortunately, apparently, I needed to remove my domain from my bluehost account and literally create an entirely new account. Now we were talking about not only moving hosting files and databases but also DNS records. Okay, I guess I can do that…nope.
I can’t disconnect a domain from my account after cancellation by myself – Bluehost has to do it for me – but the department that handles this is not open 24/7 – so I have no choice but to leave the site down and wait until normal business hours. Well, that kind of undermines the point of having 24/7 support, imho.
I didn’t want another VPS – I already have them with DigitalOcean – so Linode was out of the picture. My first choice was A Small Orange – but their hosting is expensive in comparison to the other providers (though I hear their customer service is great).
I also found Ryan Sullivan’s post on WP Site Care which reviewed seven top WordPress hosts (and I use WordPress extensively in my sites). The comparison included A Small Orange, Bluehost, GoDaddy, HostGator, Dreamhost, MediaTemple, and Site5.
A Small Orange was out of the picture due to price as mentioned above and I added MediaTemple to this grouping. I was on Bluehost, so that wasn’t an option and Sullivan’s research showed problems with HostGator’s response – so those two were out.
I’ve never been a big fan of GoDaddy – in part b/c of their juvenile marketing – which I know they have abandoned, but I decided to make them a last choice. I wasn’t really influenced by Sullivan’s observation that once he hit 25+ users performance degraded due to GoDaddy’s security software “Sentinel” which prevents traffic believed to be a DoS. While Sullivan thought this was too low, I didn’t think so. I can’t see many shared sites getting 25 simultaneous users coming across a single IP – unless one is being used as an example in a college classroom and an entire class loads the site at once…still this is unlikely, and even if it does happen, there may be enough variation in the identifying elements from the computers (e.g. OS, browser) for GoDaddy to determine it is not a DoS attack.
This left me with Dreamhost or Site5. I started with Dreamhost b/c Lifehacker had a “deal” where I could get Dreamhost for $20 for one year.
The home cooked control panel took some getting used to – I’ve been using cPanel for so long and webMin on most Linux boxes I’ve managed that this interface was foreign and somewhat confusing…but I got the hang of it.
Ooohh…They have a cPanel importer. Could I really import my cPanel backup from bluehost and save tons of time?!? Unfortunately, no. I tried several times and while the emails said the import had succeeded – it failed. Ohh well, I’ll try doing it manually – but then I see that in at least some cases I have to transfer my domains to use their DNS. What?! I ask if I can get around this – but the answer is no. I use CloudFlare for DNS and other acceleration features and don’t want to use Dreamhost’s DNS.
I decided to sign up for Site5. Maybe they would make me happy – and they did. There were still a few minor inconveniences – once again, their control panel doesn’t look like a regular cPanel. but, But they excelled on support – their techs. responded within seconds to each of my live chat requests, were knowledgeable, and seemed to have the power to accomplish the necessary tasks (as opposed to Bluehost, where segmentation of responsibilities so firmly meant technicians were unable to help me when I needed it, since the other departments weren’t open).
I now have my sites transferred over to Site5. I’ve canceled Dreamhost. My Bluehost is already canceled (though I’m still using them as my domain registrar – from habit and convenience, not b/c they offer such low prices [they don’t on domains]). We’ll see how things go from here.
P.S. I don’t think Bluehost is the devil. I’m not sure what is going on over there – I think they need to be a little more transparent about what is happening and why. It is obvious that they launched the VPS product before it was fully baked. This resulted in huge problems at the beginning – the most significant being that sometimes my support tickets would not be answered for days!
I think of myself as a pretty patient guy. If Bluehost had sought to proactively work with me, I probably would have stayed with them…but their product failed and they didn’t bend over backwards to make it work, so I left.
What do I mean by proactively work with me? Simply that they would have done whatever it took to get the site up and running and figuring out the issues. As long as I know someone is working on things, I can be pretty flexible (these aren’t sites that have to have 99.9% uptime, though I prefer that they do). I also enjoy helping companies work through issues like this – and as long as you “compensate” me (by giving my high quality tech support and perhaps some free credit for hosting) – I’ll work with you…but I got the feeling that Bluehost had taken off such a big bite that they couldn’t do this and weren’t interested in doing this.
All this to say, Bluehost may be a reasonable choice in a few months – if they are able to put out all the fires that have been haunting them. Keep an eye open for others reviewing and saying better things about Bluehost in upcoming days. Unfortunately, Bluehost has lost me as a hosting customer…and I don’t see myself returning, even if the situation improves, for the foreseeable future (there is no incentive to do so).