Moving from Canny or Featurebase in an afternoon
Posts, votes on the people who cast them, comments and statuses come across. So do your Intercom and Zendesk conversations.
The reason most teams stay on a tool they've outgrown isn't the price. It's the history. Two years of posts, thousands of votes, and a promise to every voter that they'll hear when it ships.
So the import keeps all of it.
What comes across
From Canny or Featurebase, with an API key from their settings:
- Boards, and every post on them
- Votes, attached to the people who cast them, so revenue sorting and "you asked for this" emails work on day one
- Comments, in order, with their authors
- Statuses, mapped to yours
From Intercom or Zendesk, conversations come across as threads in your inbox with the customer, the messages in order, internal notes as notes, and first-response and close times kept.
From anything else, a CSV of posts works. The CLI can dry-run it
first (harkly import posts file.csv --check) and show what would be
created before anything is.
Safe to try
Every import is recorded. Run it again and it skips what it already brought over instead of duplicating it. For seven days, one click undoes the whole import: the posts, votes, people and conversations it made.
The order we'd do it in
- Import feedback from Canny or Featurebase, and check a few busy posts.
- Drop the SDK into your app so new votes land on identified customers.
- Import support history from Intercom or Zendesk.
- Point support@ at your Harkly inbox and embed the messenger.
- Publish your next update from Harkly, and link the posts it ships.
Most teams are through step 3 in an afternoon. Step 5 is the one your customers notice.