Freshchat — Migration Reference

Role in migrations

• Staff (HD): supported as target.
• Contact (HD): supported as target.
• Ticket (HD): supported as target.

Field-level support migrating TO Freshchat (Ticket)

Migration options available for Freshchat

• No specific migration options documented.

Freshchat — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/freshchat-migration-guides/

How to get Freshchat to API Token?

Follow these steps to generate an API Token:

1. Log in to your Freshchat account. And navigate to the Admin settings.
2. Scroll down and select "API Settings" under "API".
3. Verify yourself as a human by completing the "I'm not a robot" check. Open up API Authentication.
   Note: Ensure that your Freshchat account is activated before creating an API Token.
4. Click on “Generate token” next to “Your API Key”.
5. Copy the generated API Token.
6. Return to the Migration Wizard and fill in the required field with the copied API Token. Once you've successfully connected Freshchat, proceed with setting up your Demo Migration.

Note: Don’t delete an API Token while a Free Demo or Full Data Migration is in progress. Deleting the token will result in suspension of your data migration if your access credentials become invalid.

Freshchat migration peculiarities

1. Chatbots cannot be included in the migration. When a chat is created, chatbots automatically assign the chat to themselves, which prevents the migration from updating the chat's status and assignee.
2. Contact custom fields can be migrated/updated on Freshchat. To do this, the client must create a contact with all custom fields on the Freshchat side, populate them, and provide a list of the custom fields along with their types.