Migrate from Touchpoint MX to Twenty CRM

Touchpoint MX Contact records map to Twenty Person records. Standard fields (name, email, phone) migrate directly. Touchpoint MX custom field values on Contacts map to Twenty custom fields on the Person object. We detect all active custom fields during scoping, create equivalent custom fields in Twenty Settings → Data Model before import, then populate values during the Person import. Owner assignments on Contacts map to Twenty workspace Members resolved by email match.

Touchpoint MX Journey Maps define custom stage labels (e.g., Awareness, Consideration, Decision, Retention) per organization. Twenty has no native journey concept, so we flatten each Journey Map stage label into a custom picklist field on the Person object (e.g., current_journey_stage__c). Stage transitions and timestamps migrate as additional custom fields (e.g., stage_entered_date__c). We produce a stage mapping table for customer approval before data lands, to prevent Contacts landing in the wrong lifecycle bucket.

Touchpoint MX supports Email, SMS, and Voice channels per Contact. We map active channel assignments to Twenty Person communication preference custom fields (email_opt_in__c, sms_opt_in__c, voice_opt_in__c). Channel history and delivery metadata are preserved as custom fields on the Person record or as Notes if the customer requires a chronological log.

Touchpoint MX Satisfaction Scores (numeric ratings tied to Contacts or specific interactions) map to a Twenty Person custom field (e.g., satisfaction_score__c) with timestamps preserved in a companion date field (satisfaction_score_date__c). If the score is tied to a specific interaction rather than the Contact overall, we attach a Note to the Person record with the interaction context and score.

Touchpoint MX Feedback Records (structured customer responses and comments) map to Twenty Note records linked via ContentDocumentLink to the parent Person. The Feedback text, date collected, and any associated rating migrate as Note title, body, and creation date. Feedback records tied to specific Journey Map stages are linked to the corresponding Person stage field via a custom reference in the Note body.

Touchpoint MX Message Templates (reusable outbound content with subject lines and personalization tokens) are exported as a structured reference document because Twenty has no native template management object. We deliver a written template inventory with template content, subject lines, token placeholders, and channel assignment. The customer's admin decides whether to store templates in Twenty Notes, a connected document tool, or a separate template management system.

Touchpoint MX custom fields on Contacts have Manager-only, Attendee-only, or Everyone visibility settings. We export all custom field values regardless of visibility during extraction. In Twenty, custom fields have workspace-level visibility only. We map to the most permissive read setting available in Twenty to avoid data suppression. All custom fields must be created in Settings → Data Model before the Person import; the CSV import creates records only, not fields.

Touchpoint MX User accounts are mapped by email and display name to Twenty WorkspaceMembers. We extract the full user list during scoping and create a Member mapping table. Owner assignments on Contacts and Journey Records resolve via email match. Users without a matching Twenty account go to a reconciliation queue for the customer's admin to provision before Person import begins.

Attachments associated with Contacts or Feedback records in Touchpoint MX are exported as files and re-associated in Twenty as File records linked via ContentDocumentLink to the parent Person. Large attachment volumes are chunked to avoid extraction timeout. We flag any file that exceeds Twenty's attachment size limits during scoping.

Touchpoint MX integrations (connected apps, OAuth tokens, webhook endpoints) are bound to the source account and cannot be exported or transferred. We do not migrate integration credentials. We export a written integration checklist listing every active Touchpoint MX integration with connection type, authentication method, and endpoint URL so the customer's admin can re-establish each integration in Twenty manually.