On this page

Planhat AirSync

The Planhat AirSync simplifies migration from Planhat to DevRev, supporting both one-time imports and periodic sync.

Supported objects

The following is a list of Planhat objects and their corresponding DevRev equivalents. Those marked as Sync to DevRev are eligible for import from Planhat to DevRev. Those marked as Sync to Planhat are eligible to be synced to Planhat from DevRev.

Planhat ObjectDevRev ObjectSync to DevRevSync to Planhat
UserDevUser
CompanyAccount
EndUserContact
CommentsComments
LicensesCustom Object
TaskConversation
ConversationConversations
Conversation.TicketTicket
Conversation.ChatDM
Conversation.MeetingDM
ProductUsageCustom field in Account

Import from Planhat

Follow these steps to import from Planhat:

  1. Log in to DevRev.
  2. Go to Settings > Integrations > Snap-ins, search for Planhat under All snap-ins.
  3. Click Add and Install snap-in.
  4. Go to Settings > Integrations > AirSyncs in the left-hand navigation.
  5. Click AirSync in the top-right corner and select Planhat.
  6. Create a new connection to authenticate with your Planhat workspace, or use an existing active connection.

Create Planhat connection

  1. Provide a name to the connection.
  2. In the Subdomain field, enter your Planhat domain, which can be found in the Planhat browser URL. For example, from https://app.planhat.com/, app.planhat.com is the subdomain.
  3. Enter token.
  4. On the next screen, select the authenticated Planhat workspace.
  5. Specify the DevRev part where the imported content should reside. Click Start.
  6. Initiate the import of the authenticated workspace.

:::tip Import duration varies from minutes to hours based on data size. :::

Limitations

  • Planhat does not support OAuth for API authentication.
  • Conversation-level or comment-level attachments are not supported.
  • User roles and permissions are not supported.
  • Reverse sync is only supported for licenses and tickets.
  • Historical data retention depends on your Planhat plan limitations.
  • Custom fields mapping may require manual configuration during setup.