Migrate from APSIS One to Twenty CRM

APSIS One Profiles contain both individual contacts and organizational data depending on how the account uses the CRM integration layer. We split Profiles by detecting whether the APSIS profile carries CRM-sourced account fields (company name, industry, employee count) or individual fields (first name, last name, personal email). Profiles with organizational data become Twenty CRM Companies with a primary Person record; Profiles with individual data become standalone Persons. The original APSIS profile ID is preserved in a custom field apsis_profile_id__c for audit and cross-reference.

Standard APSIS One Attributes (email, first_name, last_name, phone, address) map to Twenty CRM's built-in Person fields. Custom Attributes migrate as Twenty CRM custom fields created during schema design, with field type inferred from the APSIS data (text to TEXT, numeric to NUMBER, date to DATE, boolean to CHECKBOX, multi-value to MULTI_SELECT). Attribute values with no corresponding Twenty field are held in a custom JSON field apsis_attributes__c for post-migration review.

APSIS One Tags are flat string labels applied to Profiles. They export as a list per Profile and migrate to Twenty CRM's Topic tagging system. We create Topic records matching the APSIS tag names and link them to the migrated Person or Company via TopicAssignment. Tags used for segmentation logic are flagged in the segment rebuild inventory so the admin can recreate those groupings as filtered Person views in Twenty.

APSIS One Events with type email_open, email_click, form_submit, page_view, and custom event types map to Twenty CRM Activity records. We preserve the event type in a custom field apsis_event_type__c and the original event timestamp in the Activity's dueDate. Events with no timestamp are skipped and logged. The Activity subject uses the event type as a prefix for filtering in Twenty's timeline view.

APSIS One Segments are dynamic or static audience groupings with rule-based logic that has no direct equivalent in Twenty CRM. We export the segment definition (rule conditions, operator logic, filter stack) as a written specification document during scoping. The customer's admin rebuilds each segment as a Twenty CRM Person filter view or a custom field grouping. Complex multi-condition segments are flagged as higher-effort rebuild items.

APSIS One Marketing Automation Canvas Flows have no public API export. We capture flow screenshots, trigger conditions, action steps, and branch logic during the discovery call and document them in a written rebuild specification per Flow. The customer's admin or a developer uses Twenty's workflow primitives to reconstruct the logic. Multi-branch Flows with time delays and CRM actions are flagged as highest-effort rebuilds.

APSIS One's bidirectional CRM sync with webCRM, Efficy, Dynamics, and Lime maps Contact records to APSIS Profiles and Account/Deal records to CRM-linked Attributes. We export the current CRM-sourced data as Person and Company records in Twenty. Sync re-establishment requires re-pairing the CRM integration on the destination side and triggering a full resync; we deliver a written integration-rebuild checklist for the customer's IT team.

APSIS One Consent 2.0 stores opt-in flags and timestamps per channel (email, SMS) as Profile Attributes. We preserve consent exactly as typed fields on the Twenty CRM Person record (email_consent__c, sms_consent__c, email_consent_date__c, sms_consent_date__c) to avoid re-permissioning campaigns. This is critical for GDPR compliance on the migrated audience.

APSIS One Sections organize Segments and Flows within the account hierarchy. We map Section names to Twenty CRM Workspace names and document the workspace-subworkspace structure. If Twenty CRM's workspace model differs from the customer's Section hierarchy, we create a recommended workspace mapping in the migration documentation.

APSIS One channel configurations (sending limits, sender identities, domain authentication) are account-level settings not tied to individual Profile records. We capture channel preferences per Profile as consent attributes and document the DNS and sending domain configuration as a written handoff. Re-establishing email sending infrastructure (SPF, DKIM, custom tracking domain) in Twenty requires separate configuration outside the migration scope.