Migrate from Fans-CRM to Microsoft Dynamics 365 Sales

Fans-CRM subscriber records with engagement scores, subscription status, and lifecycle data map to Dynamics 365 Contact records. We preserve Fans-CRM-specific properties (engagement score, subscriber status, lapse date) as custom fields on the Contact using the custom field prefix field_1, field_2 naming convention that Fans-CRM exports use. The subscriber's OnlyFans username maps to a custom text field; email maps to standard email if available. The fan's lifetime value estimate from Fans-CRM maps to a custom currency field for revenue reporting in Dynamics 365.

Fans-CRM content posts (media references, PPV pricing, performance metadata) have no native equivalent in Microsoft Dynamics 365 Sales . We create a custom object Content_Post__c in the destination org with fields for post_date, media_type, ppv_price_usd, view_count, like_count, and subscriber_segment. The creator or agency name maps to the Account lookup on the custom object. Content posts are not required for standard CRM operations and are migrated as a supplementary data layer for reporting purposes.

Fans-CRM pay-per-view transaction records (amount, fan identifier, timestamp) map to a custom object PPV_Transaction__c in Dynamics 365. The fan identifier resolves to the Contact record created in the fan-to-contact mapping. Transaction amount maps to a custom currency field; transaction date maps to Transaction_Date__c. PPV transactions link to the creator's Account or to the specific Content_Post__c record depending on the client's reporting structure. This object requires pre-creation in Dynamics 365 before any records load.

Fans-CRM tier names (e.g., Free, $5, $15, $50) and fan counts per tier map to a custom object Subscription_Tier__c plus a custom picklist field tier_name__c on the Contact record. The custom object holds tier metadata (name, price, fan_count) for reporting; the Contact field holds the subscriber's current active tier assignment. Multi-tier setups create multiple Subscription_Tier__c records linked to the creator's Account.

Fans-CRM team members with role-based permissions map to Dynamics 365 User records. We extract role names from Fans-CRM export files and map them to Dynamics 365 security roles assigned post-provisioning. The agency admin identifies which team members need Dynamics 365 user licenses before migration. Inactive Fans-CRM team members map to inactive Dynamics 365 users to preserve historical assignment on records.

Fan-level engagement scores and chatter metrics from Fans-CRM migrate as custom numeric fields on the Dynamics 365 Contact record. Fields include engagement_score__c, messages_sent__c, messages_received__c, and last_active_date__c. These metrics serve as custom reporting dimensions for subscriber health and churn prediction in Dynamics 365 reports.

Fans-CRM Smart Folder tag data exports as a list of tag names per fan. We map these to a multi-select picklist field on the Contact record or to a custom Tags__c text field depending on tag count. The customer chooses the target field type during scoping. Tags enable segmentation reporting in Dynamics 365 without requiring the Smart Folder structure itself to migrate.

Fans-CRM Chat Assistant templates, bulk message scripts, and automated reply rules are platform-native logic with no Dynamics 365 equivalent. We do not migrate them. During discovery, we export the template names, body text, and trigger conditions and deliver a written inventory document so the client's admin can rebuild message automation in Dynamics 365 via Power Automate or third-party tools like HubSpot Sales Engage if needed.