Migrate from Adaptix to Nutshell

Adaptix Contact records map 1:1 to Nutshell People. Standard fields (first name, last name, email, phone, address) map directly. Custom properties on the Contact record map to Nutshell custom fields on People, which we pre-create during schema design. The contact's lifecycle stage in Adaptix preserves as a custom field hs_lifecycle_stage__c on the Nutshell People record for reference and reporting.

Adaptix Company records map 1:1 to Nutshell Organization. Company name, domain, industry, employee count, and annual revenue map to the corresponding Nutshell Organization fields. Website from Adaptix becomes the Organization URL and serves as a dedupe key during import. We create Organization records before People records so that the Organization lookup is satisfied at the moment of People insert.

Adaptix supports Company-to-Contact associations (one Contact can belong to one Company). Nutshell's People records carry a primary Organization field. We extract the Company association from Adaptix and populate the primary Organization reference on each Nutshell People record. Secondary associations do not have a direct Nutshell equivalent and are preserved as a custom field secondary_organization__c if multiple associations exist.

Adaptix Tags (used for audience segmentation and contact classification) export as a mapping table of contact-email to tag-name. Nutshell supports Tags on People records. We map tag assignments per contact and import them as Nutshell Tags. If the destination has existing tags, we merge using the tag name as the dedupe key. Tag count and naming convention are preserved.

SMS opt-in status in Adaptix is tied to the Contact record. We flag SMS consent fields explicitly during extraction and map them to Nutshell custom fields on People (sms_opt_in__c as boolean, sms_consent_date__c as date). Consent state affects sending eligibility and compliance in Nutshell, so these fields are mandatory for any team using SMS in Adaptix.

Adaptix automation workflows do not export as executable logic. We export each automation as a written reference document capturing the trigger type, conditions, actions, and delays for every step. Nutshell Pro and above support workflow automation, but the customer must rebuild these manually using Nutshell's automation builder. We deliver a step-by-step mapping document organized by automation name to accelerate the rebuild.

Adaptix Audience Segments are built from filter rules on contact properties. We extract the segment membership (which contacts belong to which segment) as a static contact list. The filter logic itself cannot migrate. In Nutshell, we create a static List per segment containing the extracted contacts. The customer rebuilds the dynamic filter logic in Nutshell using the segment membership as a reference.

Adaptix landing pages export as static HTML with embedded form markup, but dynamic connections to Adaptix's form handler, tag assignments, and automation triggers are severed. We package page HTML and form configurations as exported assets. Nutshell does not have a landing page builder; the customer must deploy these assets on a web hosting platform or use a dedicated landing page tool. We flag each affected page during discovery.

Adaptix Forms export as JSON with field definitions and consent settings. We export the full form schema. Nutshell Web-to-Lead and native forms require separate configuration. The exported JSON serves as a field-level reference for rebuilding forms in Nutshell or a third-party form tool, but the export is documentation only, not an importable form object.