Featurebase is the tool Tuti brings the most from: your team, users, feedback, changelog, help center and inbox. For where to start and what every import does, see Import from another tool.
Get an API key
In Featurebase, open Settings โ API and copy an API key. In Tuti, Get your API key opens that page. Paste the key in API key and choose Check the key and start.
What to bring
Team: your Featurebase team, as invitations you review and send.
Contacts: your users, with their custom fields and company, as Users.
Feedback: boards, posts, votes and comments, with their dates; the team's private comments as notes.
Changelog: your updates, published at their dates (drafts stay drafts), with their images.
Help center: collections and articles, with their images, files and the links between them.
Inbox: conversations with their messages, notes and images.
Profile pictures: your users' uploaded profile pictures, copied last so the rest doesn't wait for them.
Team
Each Featurebase admin with an email address becomes an invitation to your project, as a Member, and nobody is emailed. The invitations wait in Settings โ Team & roles under From Featurebase, not sent yet, with Send, Remove and Send all. Until you remove them, they count toward your plan's team members. Roles aren't carried over; owners can change them in Team & roles.
What a teammate wrote in Featurebase shows under their name, and becomes theirs once they join.
Feedback
Boards come by name, so posts land on a board of the same name if you have one. Statuses come by name, or by their kind in Featurebase (such as in progress or completed). Posts keep their author, status, ETA, votes and comments. Comments in Tuti are flat, so a reply follows its thread in time.
Left out, and counted:
Boards only some roles can see, and posts shown only to some companies.
Posts hidden from the portal or waiting for moderation, and deleted, spam or in-review comments.
A user's private comments.
Guests' votes, except the vote of a guest who wrote the post.
A post only its author could see comes as Private, seen by its author and your team.
Changelog
Entries come published at their dates, or as drafts. Their featured image becomes the cover, and categories like New, Improved, Fixed and Breaking become tags. An entry Featurebase already emailed to subscribers is marked as emailed, so publishing it again in Tuti doesn't email it twice. Entries only some people could see are left out. Comments on entries, the posts an entry shipped and changelog subscribers don't come across: Tuti's changelog has no comments, and Featurebase's API doesn't list the other two.
Help center
Articles come published or as drafts, as they were, with their images, files, videos and the links between them, which point to the matching page in your docs. Collections keep their order, up to five levels; deeper ones fold into their fifth-level parent. These come as drafts, and each is counted:
Articles that only some people could see in Featurebase.
Articles past your plan's article limit.
Articles too long for Tuti, which come in empty under their title.
Only your help center's default language comes across.
Inbox
Open, snoozed and closed conversations come with every message: your users', your team's, the bot's (as AI) and internal notes. Images in messages come as attachments. Events like assignments and status changes aren't messages, so they're left out. Closed conversations older than your plan keeps are counted, not brought.
A team reply your user read in Featurebase shows Seen; others show Imported from Featurebase, since they were never emailed from Tuti. Importing again adds the new messages in conversations that were already brought across.

