Tuti brings your Intercom users and help center across. Conversations and your Intercom team don't come across yet. For where to start and what every import does, see Import from another tool.
Get an access token
Intercom calls its key an access token, and it belongs to an app in your workspace.
In Intercom, open the Developer Hub. In Tuti, Get your API key opens it.
Open an app, or create one. Intercom makes its access token as soon as the app is created.
Copy the token from the app's Configure โ Authentication.
In Tuti, paste it in API key and choose Check the key and start.
The app needs permission to read users and companies (for Contacts) and articles (for Help center). If it can't read one, Tuti says which part, so you can change the app's permissions or leave that part out.
What to bring
Contacts: your users, with their custom fields and company, as Users.
Help center: collections and articles, with their images, files and the links between them.
Profile pictures: your users' uploaded profile pictures, copied last so the rest doesn't wait for them.
Contacts
Users come with their custom attributes and their first company's name. Leads come as leads, so they're never matched to someone in Tuti by their address. Intercom's generic placeholder pictures are left out: Tuti draws its own.
Help center
Collections keep their nesting and order. Articles come published or as drafts, as they were, by their author when that person is on your team. Articles that aren't for everyone come as drafts. Links between articles, at their Intercom help center addresses, point to their new pages.
Left out:
Languages other than your help center's default.
Unpublished changes to published articles: Intercom's API gives only the published version.
An article in more than one collection comes in the first one.

