AirSync

With DevRev's AirSync, you can migrate data from various platforms or keep data in sync between DevRev and external sources. Whether you perform a one-time import, set up a one-way sync, or establish a two-way sync, AirSync supports a flexible data migration or co-existence strategy.

What sets AirSync apart is its ability to unify all your enterprise data—both structured and unstructured—into a living knowledge graph. Unlike traditional sync tools that simply move data between systems, AirSync preserves the full context, relationships, and permissions of every record, ensuring that your information remains secure, compliant, and actionable. This means your teams and AI agents always have access to the most up-to-date, permission-aware insights, no matter where the data originated.

AirSync’s real-time, bidirectional synchronization breaks down data silos and eliminates manual work, empowering organizations to move faster and make smarter decisions. By connecting tickets, conversations, product backlogs, documents, and more, AirSync transforms scattered information into a unified source of truth. The result: improved collaboration, faster support resolution, and a foundation for AI-powered automation that truly understands your business context.

(AirSync was previously known as DevRev Airdrop.)

AirSync features

The AirSync features available vary per external source but support one or more of these:

• 1-time import: Migrate data from an external source to DevRev.
• 1-way sync: Keep data in sync from an external source to DevRev.
• 2-way sync: Synchronize data bidirectionally between DevRev and an external source.
• Recipe manager: Select the types and fields you want to AirSync from an external source.

General process

Set up a new AirSync

Whether you want to perform only a one-time import or set up an ongoing sync, performing an initial import is required.

1. Navigate to AirSyncs: Go to Settings > Integrations > AirSyncs and select AirSync (or Start AirSync if it's your first).

2. Choose Source: Select the external platform (for example, Jira, Zendesk) from which you want to import data.

3. Initiate the import process, which brings in enough data and metadata to allow you to configure the rest of the process.

4. Configure the Import: Configure the import settings, such as selecting specific objects and mapping fields.

For source-specific instructions, see Available Sources.

Post-import options

After a successful import, you have several options to manage and sync your data:

• Sync to DevRev: Synchronize new items created and modifications made in the external source to corresponding items in DevRev.

• Sync to External Source: Synchronize new items created in DevRev and modifications made in DevRev to the external source.

• Periodic Sync: Enable automatic periodic sync to keep data updated between DevRev and the external source.

• View Report: Access detailed information about the initial import and subsequent syncs.

• Delete Import: Remove the import and associated items from DevRev.

• Edit Connection: Modify the connection settings for future actions. This can be used if the connection goes stale or the connection owner leaves the company.

• Archive Import: Archive the import, preventing any new sync, modification, or accidental deletion while still preserving history. This action can be undone.

• Unarchive Import: Unarchive the import, allowing new syncs and modifications. (Only available for archived AirSyncs via the detailed report view.)

Historical AirSyncs

You can view information about currently running and previous AirSyncs from various sources, providing insights into migration activities.

To view existing AirSyncs, go to Settings > Integrations > AirSyncs.

Filter AirSynced records

• Sync status:

After an import, you can view the sync status of the imported items. The sync status indicates whether an item is in sync with the external source or if there are any discrepancies. You can apply the following sync status filters to the records:

• Succeeded: The import was successful, and the record is in sync with the external source/DevRev.

• Modified: Minor modifications were made to the record, but no constraints were violated.

• Staged: Data model constraints were violated, such as contact and account mismatch.

• Failed: The record was not synced.

• Sync date:

  You can filter the records based on the sync date. This filter helps you retrieve the records that were synced in or out at a specific time.

• Sync origin status:

  You can filter the records based on the sync origin status. This filter helps you retrieve the records that were synced in or out from the external source. For example, items synced in from Jira, Zendesk, and Salesforce Service.

• Sync unit:

You can filter the records based on the sync unit. This filter helps you retrieve the records that were synced in or out from a specific sync unit in the origin system, such as syncing from a specific project in Jira.

Record view

AirSynced items now have an icon at the top of the record, next to the display ID and subtype which indicates:

• Source origin system
• Sync Status
• Sync Date
• A convenient link back to this item in the external source

You can identify the imported items by the identifier right next to the display ID in the vista view without switching. You can use sync filters in vista view too.