We are looking at moving from Aha! to Jira Product Discovery and curious if any others have done the same and would be willing to share experience?
We moved from Aha to JPD. Aha was not supportive in giving us a full backup of our account due to our license so we just exported to CSV using reports and then used our Boomi Integration platform to cleanup the data before we imported into JPD using the Jira API. We decided to segment our Customer Feedback/Ideas into a separate JPD project. Normal roadmap items from Aha we put into a "Roadmap" project. The biggest thing we miss is the concept of "hierarchy" in Aha. JPD only has "Ideas" at a single level. But apparently they are working to address that to make it more similar to native Jira that has multiple Issue types.
Overall we have been pleased with the move. JPD is a lot less complex, way more cost effective and the integration with Jira is way better then what we got with Aha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We moved from Aha! to Productboard and now finally to JPD. While JPD is still behind in feature completeness and i’m especially missing how insights could be created and organised in PB, all of this is more than outweighted by having every piece of information in one platform. In that journey, Aha! is the one tool that i miss the least. The one exception is maybe if you used customer voting in Aha! It’s a quite ok feature, but then there’s a really interesting talk by Tanguy about why there’s no voting in JPD, so not having it is rather a feature (link: https://youtu.be/6P7HBBQyQ5U?t=867&si=jxbD8XFa0jexHthK)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Dirk, for your response, greatly appreciated. Did you migrate data from Aha! or just start with a clean slate?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We migrated data from Aha! to Productboard and then again from PD to JSD but manually and took it as an opportunity to get rid of stale ideas. We stretched that over a few months and migrated a handful of ideas each day (and there's still a few hundred sitting in PD - where they maybe just will stay. On the first migration from Aha! to PD, we just downgraded Aha! to a single user license to get some wiggle room and kept it for maybe another year.
What i learned during the migration: There's not that one perfect tool. They all have their flaws. But hunting for the "best" is a direct road to chaos. Decide on some tools and then just live with them as long as possible. We have been Atlassian customers maybe 10 years ago, added Aha!, then moved to GitLab + Aha!, then replaced Aha! with Productboard. Then GitLab took a very wrong turn, we moved to GitHub, were deeply dissatisfied with issues / projects in GitHub, gave Atlassian a second try - and there we are. It's a completely different product from 10 years ago and the deep integration, especially between Jira and Confluence is a godsend and so so much better than notebooks in Aha!.
The moral? Had we just kept using Atlassian, we not only had saved a buttload of money but we would also still have all the data that we discarded on each migration. So, if you are already using Jira, add JSD and enjoy. It's maybe no the best tool, but great enough - and if you are using the full Atlassian suite, you'll get a lot for your money.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.