Migrate from Adaptix to Pipedrive

Adaptix Contacts map directly to Pipedrive Persons. Email, name, phone, address, and all standard contact fields transfer 1:1. Custom properties on the Contact record map to Pipedrive custom fields on Person. We preserve the Adaptix contact ID in a custom field adaptix_contact_id__c for reconciliation.

Adaptix Companies map directly to Pipedrive Organizations. Company name, domain, industry, employee count, and address fields transfer to matching Pipedrive Organization fields. The Organization is created before any related Person records to satisfy the Organization-lookup requirement on Person.

Adaptix lifecycle stage and lead status are tracked as contact properties rather than a distinct object. We preserve these values in custom fields on Person and optionally apply Pipedrive Labels (e.g., Lead, MQL, SQL, Customer) to replicate lifecycle stage segmentation using Pipedrive's native labeling.

Adaptix tags used for audience segmentation map to Pipedrive Labels. Each unique tag becomes a Pipedrive Label, and tag assignments per contact are translated to Person-Label relationships. Pipedrive Labels are a native feature at all paid tiers with no field configuration required.

Adaptix audience segments are built from contact filter rules. We extract the segment definition (filter conditions and contact membership) and rebuild equivalent static or dynamic filter views in Pipedrive. Segments with complex multi-condition rules may require multiple Pipedrive filters or a custom field strategy.

Adaptix automation workflows cannot be exported as executable logic. We deliver a written inventory of every active Adaptix Automation with its trigger, conditions, actions, and delays documented step-by-step. The customer's Pipedrive admin uses this inventory to rebuild equivalent workflows in Pipedrive Workflows or a connected automation tool.

Adaptix custom properties on Contacts and Companies vary per account. We flag all custom properties during discovery, map each to an equivalent Pipedrive custom field on the matching object (Person or Organization), and configure the field type (text, number, date, picklist, checkbox) to match the Adaptix source data type before migration.

Adaptix landing pages export as static HTML without dynamic form connections and automation triggers. We do not migrate landing pages as functional assets. We deliver page HTML and form definitions as reference assets for manual rebuild in a landing page tool or web platform of the customer's choosing.

Adaptix forms export as field definitions and consent settings. Pipedrive CRM does not include a native form builder at the sales layer. We deliver form field definitions as JSON and recommend Pipedrive Web-to-Lead, Typeform, or a marketing-automation form tool as the replacement.

SMS opt-in status and consent records tied to Adaptix Contacts migrate to Pipedrive as a custom field on Person (e.g., sms_consent__c as a checkbox or date field). We flag SMS consent explicitly because it affects sending eligibility and compliance in the destination platform.

Adaptix tracks email engagement events (opens, clicks, sends) as activity-level data that is not exported as discrete records. We do not migrate engagement event history. We deliver a written reference of engagement summary statistics (total sends, open rate, click rate) for manual entry into Pipedrive reports or a BI tool.

Send Time Optimization scores, subject line performance history, and Spintax configurations are internal to Adaptix and not exportable. We document these values at migration time for manual reference. The new platform's AI tools will establish fresh send-time baselines. We advise teams to screenshot key AI dashboard metrics before cutover.