Migrate from Adaptix to Microsoft Dynamics 365 Sales

Adaptix Contacts with a lifecycle stage of subscriber or marketing lead map to Microsoft Dynamics 365 Sales Lead. Contacts with a sales-qualified or active customer stage map to Microsoft Dynamics 365 Sales Contact tied to an Account. We read Adaptix custom property fields to determine the split and preserve the original Adaptix stage in a custom field adaptix_original_stage__c on both Lead and Contact for audit.

Adaptix Company records map directly to Microsoft Dynamics 365 Sales Account. Company domain maps to Account.Website. We use the Company name as the Account dedupe key during import. Account must be created before any Contact import so that the parent AccountId lookup is satisfied at Contact insert time.

Adaptix lifecycle stage values on Contacts routing to Lead map to a Microsoft Dynamics 365 Sales Lead Status picklist we configure during scoping. Status labels are mapped one-to-one from the Adaptix stage to a customer-approved set of Lead Status values.

SMS consent is a contact-level custom property in Adaptix. We map it explicitly to a Microsoft Dynamics 365 Sales consent field because SMS sending eligibility depends on this flag. If the destination org has the Telemarketing base table enabled, we use msdyn_gdproptout; otherwise we create a custom field adaptix_sms_consent__c as a boolean.

Adaptix Audience Segments are built from contact filter rules. We export segment definitions as a filter logic document and separately export segment membership as a contact-to-segment lookup table. The customer's Dynamics 365 admin rebuilds segments as either Static Marketing Lists or Dynamic Marketing Lists using the filter logic we document.

Adaptix tags used for contact classification migrate to Microsoft Dynamics 365 Sales custom multi-select picklist fields on Contact. If the customer licenses Dynamics 365 Marketing, tags migrate to Topics with TopicAssignment records. The tag strategy is chosen during scoping.

Adaptix custom properties on Contacts vary per tenant and are not standardized. We flag every custom property during discovery, map each to a corresponding Microsoft Dynamics 365 Sales custom field of equivalent type (text, number, date, boolean, picklist), and include type validation before import so that Dynamics 365 validation rules do not reject records.

Adaptix Company custom properties map to Account custom fields in Microsoft Dynamics 365 Sales . We apply the same discovery, type mapping, and validation step as for Contact custom properties.

Adaptix Automations are not exportable. We deliver a written automation inventory documenting every active workflow: trigger event, condition branches, action types, and delay durations. Each automation receives a recommended Power Automate or Dynamics 365 Business Rule equivalent. The customer's admin rebuilds these post-migration; we do not migrate automation logic as executable code.

Adaptix Landing Pages export as static HTML with embedded form markup. Dynamic connections to Adaptix form handlers, tag assignments, and automation triggers are severed on export. We package pages as HTML assets with a form field inventory. Rebuild in Dynamics 365 requires manual reconfiguration of any dynamic triggers.