Shari K.
RecruiterFlow Failed the Migration, then Blamed the Customer.
The migration process was oversold. What I was told would take a couple of months to migrate approximately 19,000 records stretched to about 8 months and was never completed. During that time, RecruiterFlow continued billing quarterly, in advance, for multiple user licenses. I paid for three quarters of subscription fees while my team never had a usable ATS. I repeatedly asked for billing to be addressed until the migration was complete, but no accommodation was ever provided. Instead, I was repeatedly told we were "almost there" and would be up and running soon. Meanwhile, I was paying for both RecruiterFlow and our current ATS as well as supporting tools it was supposed to replace. We were spending thousands without an end in sight. The most disappointing part of this experience wasn't that the migration failed. It was the lack of accountability afterward. After spending thousands of dollars on a platform my business never got to use, the Director of Customer Success (Raman) concluded that the extended migration was MY fault. I also reached out to the CEO (Manan), who initially said he would look into the situation, but no resolution was offered and now communication has stopped. Over the last couple of weeks, I've learned that other customers have reported similarly difficult migration experiences. I also know of at least one agency that received a refund under comparable circumstances. That makes it difficult to understand why my repeated requests for a reasonable accommodation were denied. Based on my experience, RecruiterFlow's handling of failed implementations appears inconsistent, with different customers receiving different outcomes. Software implementations can fail. What defines a company is what happens next. RecruiterFlow chose to keep the money, blame the customer, and walk away. Based on my experience, that's not a company I can recommend.



