Migrate from Adaptix to Salesforce Sales Cloud

Adaptix Contacts map directly to Salesforce Leads because Adaptix does not distinguish between prospect and customer contacts at the object level. We compute the target object during scoping based on the customer's lifecycle stage distribution: contacts with a sales-engaged lifecycle stage may warrant a Contact+Account model, but most Adaptix contacts are prospect-level. Lifecycle stage and contact score preserve in custom fields hs_original_lifecycle__c and hs_contact_score__c.

If the customer has paid customer records in Adaptix that warrant a full Contact+Account structure in Salesforce, we split by lifecycle stage. Customer, evangelist, and partner lifecycle stages map to Salesforce Contact tied to an Account. Subscriber, lead, and marketing-qualified stages map to Salesforce Lead. We make the split rule explicit during scoping and apply it as the first transform during migration.

Adaptix Company records map to Salesforce Account. The Company domain becomes the Account Website field and serves as the dedupe key. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time. Standard firmographic fields (industry, employee count, annual revenue, address) map directly.

Adaptix Tags are contact classification labels with no direct Salesforce equivalent. We export the full tag assignment table (contact email + tag value). Tags used for audience classification map to a Salesforce multi-select picklist field on Lead or Contact. Tags used for campaign-style grouping map to Salesforce Campaign with CampaignMember records. The customer selects the strategy during scoping.

Adaptix Audience Segments are filter-based rules applied to the contact database. We export segment definitions (filter conditions, AND/OR logic, field criteria) as a written document. The contact membership list (which contacts matched each segment at migration time) exports as a Campaign membership file. The filter logic must be manually rebuilt in Salesforce as a Report or a Flow-based segmentation process.

Adaptix Automation workflows do not export as executable code. We export every automation as a written step-by-step document: trigger type, conditions, condition logic (AND/OR), each action (send email, add tag, update property, delay, goal), and delay durations. The destination admin or a Salesforce partner uses this document to rebuild the automation in Salesforce Flow. This is the most time-consuming post-migration activity for teams with complex lifecycle sequences.

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 deliver the HTML assets as a ZIP and separately export form field definitions as JSON. The destination team rebuilds pages in Salesforce Experience Cloud, a CMS, or a third-party landing page tool and reconnects form submissions to Salesforce Web-to-Lead or Flow.

Adaptix Forms are standalone lead-capture objects with field definitions, consent settings, and thank-you message configurations. We export field definitions and consent settings as JSON. Salesforce Web-to-Lead generates equivalent HTML form code, but consent fields and thank-you behavior require manual rebuild. We document the original form's field names, types, and required settings to accelerate the rebuild.

Adaptix Custom Properties on Contacts vary per account and are not standardized. We flag all custom properties during discovery and map each to a Salesforce custom field with a matching type (text, number, date, picklist, checkbox). Salesforce field names use the __c suffix and are renamed from Adaptix's convention to a Salesforce-standard naming scheme. Custom fields are pre-created in the destination org before migration begins.

Adaptix Company-level custom properties map to Salesforce Account custom fields using the same type-matching approach as Contact custom properties. We extract the full list during discovery and create the destination schema before migration.

SMS opt-in status is a contact property in Adaptix tied to compliance requirements. We flag the SMS consent field explicitly and map it to a Salesforce custom field (sms_consent__c, checkbox or date for consent timestamp). Consent state affects sending eligibility in Salesforce and any connected SMS tool. We preserve both the consent status and the consent date if available.

Adaptix Owners are team members assigned to contacts and companies. We resolve Owners by email match against the Salesforce destination org's User table. Any Adaptix Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner resolution is required before Contacts and Companies can be inserted because OwnerId is a required reference on most standard objects.

Adaptix tracks email opens, clicks, and sends as activity-level events. These are reference data rather than discrete records in most export scenarios. We flag them as documented but not migrated as discrete Salesforce Task or EmailMessage records unless the customer has a specific engagement history preservation requirement, in which case we use the Bulk API 2.0 with parent-record resolution.