Migrate from Fans-CRM to Twenty CRM

Fans-CRM subscriber records map to Twenty Contacts. The fan's display name becomes Contact name, email address (if captured in Fans-CRM) maps to the email field, and the engagement score, subscription status, and lifecycle stage data migrate as custom fields on the Contact record. Subscription start date maps to a custom date field. If Fans-CRM stores a phone number or username handle, those map to custom text fields since Twenty standard Contact does not include username fields. The migration user must confirm which Fans-CRM fields are populated before field mapping is finalized.

Fans-CRM tier names (e.g., $5, $15, $50 monthly) and the fan's assigned tier migrate as a custom picklist or text field on the Twenty Contact. Tier pricing can be stored as a separate numeric custom field if the creator wants per-tier revenue tracking. The tier assignment also serves as a segmentation signal for Twenty's tagging feature or a custom 'Tier Level' field that can drive Views and reporting.

Pay-per-view records (fan identifier, amount, timestamp, content reference) map to a Twenty custom object named PPV_Transaction__c with lookup relationships to the Contact record (fan) and an optional Content_Post__c reference. Amount migrates as a currency or numeric field; timestamp migrates as a datetime field. We aggregate PPV history per fan during migration to surface total spend, purchase frequency, and last purchase date as rollup fields or reporting metrics in Twenty.

Fans-CRM content posts containing media references, PPV pricing, and performance metadata map to a Twenty custom object named Content_Post__c. The post's title or description, media URL, PPV price, and engagement metrics (likes, comments, saves) migrate as fields on the object. Post date migrates as a date field. Since Twenty does not have a native media library, the media URL is stored as a text reference; the customer configures Twenty's file storage separately for actual media hosting.

Fan-level engagement scores, chatter metrics, and interaction frequency data stored in Fans-CRM migrate as custom numeric fields on the Twenty Contact record. Fields like engagement_score, messages_sent, and last_active_date map directly to typed custom fields. These values are preserved for historical analysis even if the fan becomes inactive, and they can be used to segment active versus lapsed subscribers in Twenty Views.

Fans-CRM tag-based content organization folders map to Twenty's tagging feature applied to Content_Post__c records. We export the underlying tag data and assign tags during import. If the fan-level tagging in Fans-CRM captures subscriber characteristics (e.g., 'PPV buyer', 'long-term subscriber', 'refunded'), those tags migrate to Contact records as well. The customer chooses during scoping whether to use native Tags or a custom multi-select picklist field.

Fans-CRM agency users with role-based permissions map to Twenty User records. We extract the username, email, and role assignment from Fans-CRM and create matching Twenty User accounts. Permissions are mapped to Twenty's workspaceMember role system. If Fans-CRM roles do not map cleanly to Twenty's role model, we document the gap and the customer configures permissions in Twenty post-migration.

Fans-CRM message templates and bulk messaging rules are platform-native automation logic tied to the Chat Assistant feature. Twenty CRM does not have a native bulk messaging module, and message templates cannot be migrated programmatically. We extract the template content, conditions, and personalization variables during discovery and deliver a written inventory documenting each template so the customer can recreate them in Twenty's workflow tools or a third-party messaging integration.

Fans-CRM's automated reply rules and Chat Assistant branching logic are platform-specific automation that has no equivalent in Twenty's workflow model. We document the trigger conditions, message flows, and personalization variables during discovery and deliver a written map showing how each automation could be reconstructed in Twenty using its API-based extensibility or a third-party chat automation tool.

Fans-CRM subscriber lapse dates and re-engagement campaign records migrate as custom fields on the Twenty Contact. Fields like last_active_date, lapse_date, re_engagement_campaign_sent, and re_engagement_campaign_opened map to date or boolean custom fields. This preserves the retention analysis data without requiring the customer to rebuild it from activity logs post-migration.