Migrate from Fans-CRM to Nutshell

Fans-CRM fan and subscriber records map to Nutshell People. We preserve engagement score, subscription status, lapse tracking flags, and fan lifetime values as custom fields on the Person record. The fan's email address or username serves as the dedupe key. Because Fans-CRM organizes around individual fans rather than accounts, there is no natural Companies/Accounts hierarchy unless the client manages brand or agency relationships as separate records.

Fans-CRM PPV transaction records (amount, timestamp, fan identifier) aggregate into custom fields on the linked Nutshell Person record: ppv_total_amount__c, ppv_transaction_count__c, and ppv_last_date__c. If the client requires individual transaction history, we create a PPV custom object in Nutshell with a lookup to Person, storing each PPV event as a separate record. The client chooses between aggregate custom fields and a transaction custom object during scoping.

Fans-CRM tier names, tier prices, and fan counts per tier map to Nutshell People custom fields: subscription_tier__c (text picklist), tier_price__c (currency), and tier_start_date__c (date). We align the picklist values to match the tier names exported from Fans-CRM so that filtering and reporting work immediately in Nutshell after migration.

Fans-CRM content posts with media references, PPV pricing, and performance metadata have no native equivalent in Nutshell's People-Deals-Activities model. We create a Content custom object with fields for media_url__c, post_date__c, ppv_price__c, view_count__c, and fan_references__c (text). For clients with fewer than 200 posts, we attach a structured Note document listing each post with metadata instead of creating a full custom object schema.

Fans-CRM fan-level engagement scores, chatter metrics, and activity frequency scores migrate as custom numeric fields on the Nutshell Person record: engagement_score__c, message_count__c, and last_active_date__c. We preserve the original metric scale so that comparative reporting (e.g., segmenting fans by engagement tier) carries forward without re-normalization.

Fans-CRM agency users with role-based permissions map to Nutshell Users. We map admin, manager, and agent roles to Nutshell Admin and Standard User profiles. Active Fans-CRM users receive Nutshell user seats provisioned by the client's admin before migration; inactive users are noted in the migration inventory for optional provisioning.

Fans-CRM Smart Folders organize fans by tags (e.g., lapsed, high-spender, active). The underlying tag data exports as tag name strings. We create Nutshell Saved Views with filter conditions matching the Smart Folder logic, or we create Nutshell Tags on the Person records if the client prefers tag-based segmentation. The client confirms the preferred approach during scoping.

Fans-CRM Chat Assistant messages, bulk message scripts, and automated reply templates are platform-native automation logic with no equivalent in Nutshell. We document the template names, trigger conditions, and message body content during discovery and deliver this as a written template inventory. The client's admin rebuilds these manually in Nutshell's email templates and sequence tools post-migration.