The Planhat AirSync connector migrates data from Planhat to DevRev, supporting both one-time imports and periodic sync.
The following table lists Planhat objects and their corresponding DevRev equivalents. Objects marked Sync to DevRev are eligible for import from Planhat to DevRev.
Planhat object | DevRev object | Sync to DevRev | Sync to Planhat |
|---|---|---|---|
User | User | ✅ | ❌ |
Company | Account | ✅ | ❌ |
EndUser | Contact | ✅ | ❌ |
Comments | Comments | ✅ | ❌ |
Licenses | Custom Object | ✅ | ✅ |
Task | Conversation | ✅ | ❌ |
Conversation | Conversations | ✅ | ❌ |
Conversation.Ticket | Ticket | ✅ | ✅ |
Conversation.Chat | DM | ❌ | ❌ |
Conversation.Meeting | Custom Object | ✅ | ✅ |
ProductUsage | Custom field in Account | ✅ | ❌ |
Install the Planhat snap-in from the DevRev Marketplace by searching for Planhat and following the installation prompts.
Navigate to Settings > Integrations > AirSyncs.
Click AirSync in the top right corner and select Planhat.
Create a new connection to authenticate with your Planhat workspace, or select an existing active connection.
To create a new connection, provide a name for the connection. In the Subdomain field, enter the hostname from your Planhat browser URL. For example, for https://app.planhat.com/, the subdomain is app.planhat.com. Then enter your Planhat API token in the Token field.
The token must have full access with the following permissions — Portfolio: Full access. Data Module: Company (View), End Users (View), Conversations (View, Create, Update), Tasks (View), Licenses (View, Create, Update), Users (View), Custom Fields (View, Create, Update), Comments (View, Create, Update).
On the next screen, select the authenticated Planhat workspace.
Specify the DevRev part where the imported content should reside, then click Start to initiate a bulk import of the selected workspace.
The duration of the import depends on the size of the Planhat workspace. It can take anywhere from a few minutes to several hours depending on data volume.
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 tickets and custom objects.
Tags are not supported.
When creating a custom object (for example, License) in DevRev during reverse sync, CompanyId, FromDate, and ToDate are required fields.
In incremental sync, all data is extracted first and then filtered, which can cause the sync process to take longer than expected.
Conversation type changes are not supported during incremental sync, which may result in duplicate data and missing comments.
After a successful import, the following options are available for the imported workspace:
Sync to DevRev
Synchronizes any modifications made in Planhat with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any data added to Planhat after the last sync or import. Eligible object types include companies, users, contacts, licenses, tasks, conversations, tickets, and custom objects.
View Report
Provides detailed information about the initial import and any subsequent syncs performed.
Delete Import
Removes the import and all data imported from Planhat into DevRev, including users, accounts, contacts, and conversations.
Edit Connection
Changes the connection used for any subsequent actions. This is useful if a connection becomes inactive or the user who established it is no longer available.
After a successful import from Planhat, you can sync the imported data with DevRev. This operation imports any companies, users, contacts, licenses, tasks, conversations, tickets, custom objects, and any changes made to previously imported items from Planhat.
To perform a one-time sync to DevRev:
Locate the previously imported project.
Select ⋮ > Sync Planhat to DevRev.
To perform a reverse sync from DevRev to Planhat:
Locate the previously imported project.
Select ⋮ > Sync DevRev to Planhat.
⚠️ Warning: A one-time sync may overwrite fields in previously imported items, even if they were modified in DevRev.
To view running and previous imports:
Select the import you want to view.
Click ⋮ and select View Report.
After a successful import, you can enable periodic sync to automatically synchronize data with DevRev on a regular basis. By default, sync occurs once per hour.
To configure periodic sync:
Locate the previously imported project.
Select ⋮ > Set Periodic Sync.
The following periodic sync options are available:
Planhat → DevRev: Syncs data from Planhat into DevRev.
DevRev → Planhat: Reverse sync to Planhat (supported for tickets and custom objects only).
The Enable automations for synced items setting is optional and can be activated during periodic sync configuration. When enabled, newly created or updated items trigger events, which can initiate webhooks, notifications, snap-ins, and other processes as if the events originated directly in DevRev. When disabled, updates do not trigger any event-driven processes. This behavior applies only to periodic syncs; no events are triggered during a first-time import or a manual sync.
⚠️ Warning: Deleting an import permanently removes all content it created in DevRev, including users, accounts, contacts, and conversations — even items that were subsequently modified in DevRev.
To delete an import and all the content it created:
Locate the previously imported project.
Select ⋮ > Delete Import.
Deleting an import can be useful when running proofs of concept or when you need to change the configuration used during the original import. After deletion, you can re-import the project at any time.