[miles-myredis]

I posted a more in depth response in this thread, but the short of it is this.

1. I'd tried finding new people to help with the increased workload of new customers. Everyone I found failed, causing me months of setbacks while I did 2x the workload, and then tried to train a new person on the stack.

2. I've been funding this completely out of my own pocket. No VC money, or even buddy money. After the most recent co-founder being arrested, I had to make a decision. Either my customers suffer, or my family suffers. Since I was unwilling to have either of those out comes, the only logical (yet painful) solution was to have a company with the proper resources and expertise take over.

[sgrove]

While I was initially disappointed in what seemed like irresponsible post-acquisition behavior after reading the linkbait title, after knowing what kind of a situation you were in, it makes a ton of sense. Don't worry about the ridiculous critics in the crowd, it's a very different world when you're in the thick of a failing startup with people/family depending on you.

This seems like the most responsible action you could have taken, and is a noble way of handling your customers' trust. The option to migrate anyone who asks but to encourage developers who know what they're doing to do it themselves is similarly appropriate.

The only seemingly missing piece is a longer notification window.

Sorry for the rough ride of a failing company, but well done for handling the transition appropriately.

[miles-myredis]

The really crappy part was, the traction was starting to pick up this last month. :(

[aneth4]

Ok - I guess it was just REALLY inept messaging after the acquisition, maybe mostly acquiring company's fault.

How about:

We've been acquired. Over the next 3 months we will be migrating customers and will notify you of any action required.

Instead of:

We've been acquired. Piss off.