Migrate from Adaptix to Freshsales

Adaptix Contacts with a lifecycle stage indicating a known buyer or customer (e.g., customer, evangelist) map to Freshsales Contact linked to an Account. Contacts with lifecycle stage indicating a prospect (e.g., subscriber, lead) map to Freshsales Lead. We compute the routing decision from the Adaptix lifecycle_stage property during the transform phase and preserve the original value in a custom field adaptix_lifecycle_stage__c for audit.

Adaptix Company records map directly to Freshsales Account. The Company name becomes Account Name. If the Adaptix Company has an associated domain, that maps to the Account Website field and is used as the dedupe key during import.

Each Adaptix custom property on a Contact becomes a Freshsales custom field on the Contact or Lead object. We match field types during discovery (text to text, number to number, date to date, dropdown to picklist). Dropdown custom properties require the picklist values to be pre-created in Freshsales before migration because Freshsales only maps fields with matching value sets during lead conversion.

Adaptix custom properties on Company records map to Freshsales Account custom fields. Field type matching follows the same rules as Contact custom properties. Account-level custom fields are available from Freshsales Growth tier onward.

Adaptix tags used for audience segmentation and contact classification map to Freshsales Labels (the equivalent segmentation construct). Tags stored as multi-checkbox properties migrate to Freshsales multi-select picklist fields. We export a tag-to-label mapping table and advise the customer to pre-create the Labels in Freshsales during setup.

Adaptix automation workflows are not exportable in machine-readable form. We export each automation as a human-readable step-by-step document capturing the trigger, conditions, actions, delays, and tag assignments. The customer rebuilds these in Freshsales Workflows (available from Growth tier) or Freshsales bots (Pro tier). We do not execute the rebuild as part of the migration scope.

Adaptix landing pages export as static HTML with embedded form markup. Dynamic connections to Adaptix's form handler, tag assignments, and automation triggers are severed on export. We package each page as an HTML file and separately export the form field definitions. The customer rebuilds pages in their preferred landing page tool and recreates form-to-automation connections manually.

Adaptix form field definitions export as JSON with consent settings preserved. We map the field schema to Freshsales form fields during discovery. If the customer also licenses Freshmarketer, forms migrate to Freshmarketer Forms; otherwise, they migrate to Freshsales web forms. Consent checkboxes map to Freshsales subscription preference fields.

Adaptix SMS consent records are tied to Contacts as a property but have no equivalent native object in Freshsales. We flag SMS consent as a required custom field (sms_consent__c) on the Contact object, map the consent value directly, and include it in the compliance handoff documentation for the customer's admin to verify post-migration.

Adaptix audience segments are built from contact filter rules. We extract the segment definition (filter conditions, logic operators, and membership list) and document it for manual rebuild in Freshsales using its filter and view system. Segment membership lists (the specific contacts in each segment) are exported as CSV and can be imported as a static list in Freshsales if the customer prefers a list-based approach over filter-based segmentation.