Migrate from APSIS One to Nutshell

APSIS One Profiles map directly to Nutshell Person records. Default Attributes (First name, Last name, Email, Mobile with country code, Birth date) map to the corresponding typed Person fields. Custom Attributes in APSIS One map to Nutshell custom fields on Person, which we pre-create during schema design using the Attribute name as the field label and the detected data type (text, number, date, boolean) as the Nutshell field type. CRM-ID from APSIS One maps to a custom field for reference back to the source system.

Standard APSIS One Attributes (firstName, lastName, email, mobile, birthDate, CRM-ID) map to the equivalent Nutshell Person field by exact name match. Mobile phone numbers must include country code per MSISDN format; we validate and prepend country code if missing before import to avoid Nutshell phone field rejection.

Custom Attributes in APSIS One (created in the Section Data Model) map to Nutshell custom fields on Person. We pre-create each custom field in Nutshell during schema design, mapping the APSIS One attribute data type to the nearest Nutshell field type. Multi-value attributes (arrays) map to text fields as comma-separated strings. We flag any attribute that exceeds Nutshell's field name length limit for truncation.

APSIS One Tags export as flat string labels per Profile. We preserve the tag set exactly and apply each tag as a label association on the corresponding Nutshell Person record. Tags with special characters (spaces, slashes) are cleaned to Nutshell's allowed character set. Tag count per Profile is preserved as a reference for the customer to decide whether to create Nutshell custom fields for frequently used tag categories.

APSIS One Segments (dynamic or static) export via the Profiles in Segment Report endpoint. We export the full Profile membership list for each Segment and create a corresponding Nutshell List. Dynamic Segments cannot be replicated as dynamic lists in Nutshell (Nutshell Lists are static); we deliver a written description of each dynamic segment's rule logic for the customer to recreate manually as filter-based segments if Nutshell introduces that capability.

APSIS One Event history (email_opened, email_clicked, page_viewed, custom event types) maps to Nutshell Task records with a custom activity-type field carrying the original event name. Each Task's description holds the event payload as JSON text. ActivityDate on the Task is set to the original APSIS One event timestamp to preserve timeline ordering. Large event histories are chunked to avoid request body limits and written in batches.

APSIS One Consent records (Consent 2.0) store opt-in status and timestamp per channel (email, SMS) as Profile Attributes. We map consent flags to Nutshell Person fields: email opt-in to the standard email field active flag and SMS opt-in to a custom SMS consent field with the consent timestamp stored as a custom date field. GDPR-compliant consent records are preserved exactly to avoid re-permissioning campaigns in Nutshell.

APSIS One Sections (organizational units holding Segments and Flows) map to Nutshell Workspaces. We create one Nutshell Workspace per APSIS One Section during migration so that Lists and tag groupings remain scoped to the same organizational context the customer used in APSIS One. If the customer has only one Section, no workspace mapping is required.

APSIS One bidirectional CRM sync (with webCRM, Efficy, Microsoft Dynamics, and Lime CRM) maps Contact, Account, and Deal integration data to Nutshell Company records linked to Person records. We export the current sync state, map CRM Account data to Nutshell Company, and map CRM Contact data to Person records with a lookup to the Company. The CRM-ID attribute from APSIS One preserves the link back to the source CRM record for reconciliation.