Migrate from Fans-CRM to Odoo CRM

Fans-CRM subscriber records with engagement scores, subscription status, lifecycle data, and chatter metrics map to Odoo CRM Contact records. We preserve engagement_score, subscription_status, lapse_date, and re_engagement_flag as custom Char, Selection, or Date fields on res.partner. The fan's email address becomes the Contact email; the OnlyFans username becomes a custom field (no native Odoo equivalent). Subscription tier assignments from Fans-CRM map to a custom Selection field on the Contact.

Fans-CRM tier definitions (tier name, monthly price, fan count per tier) map either to Odoo Product Templates with specific pricelist rules or to a custom Contact field depending on whether the client wants to track tier as a contact property or as a sellable product. We confirm the client's preference during scoping. If tier-as-product, we create one product per subscription tier with a recurring invoice policy in Odoo Sale app.

Fans-CRM PPV records (amount, fan identifier, timestamp, content reference, media type) do not map to any standard Odoo object. We create a custom Odoo model x_ppv_transaction with fields for fan_partner_id (Many2one to res.partner), transaction_date (Date), amount (Monetary), content_reference (Char), and media_type (Selection). We build this via Odoo's Settings > Custom Structures > Models interface or via CSV with Odoo's external ID format before import.

Fans-CRM content posts contain media references, PPV pricing, post date, and performance metadata (likes, comments, tip amount). We create a custom Odoo model x_content_post with fields for post_date, media_type (Selection: photo/video/audio/text), ppv_price, performance_likes, performance_comments, performance_tips, and fan_partner_ids (Many2many to res.partner for tagged fans). Media files cannot migrate as binary content through CSV; we document the storage location so the client's admin can attach them via Odoo's document management module post-migration.

Fans-CRM stores fan-level engagement scores and chatter metrics as numerical values on the subscriber record. We map these as custom numeric fields on res.partner: x_engagement_score (Float), x_chatter_count (Integer), x_last_active_date (Date). These are stored directly on the Contact record for use in Odoo CRM filters, kanban views, and segmentation.

Fans-CRM agency users with role-based permissions (Admin, Manager, Content Creator, Support) map to Odoo User accounts with corresponding access rights groups. We map Fan-CRM role labels to Odoo default groups (Sales / Administration / Portal) and create custom access rights groups for agency-specific roles if the client's Odoo deployment includes the Odoo Studio app. Inactive users from Fans-CRM map to Odoo User records with Active=False.

Fans-CRM Smart Folders are tag-based content organization structures that may reference fans, posts, or both. We extract all underlying tag data and import them as Odoo Contact Tags (res.partner.category) for fan-level tags. If content-level tags exist, we store them on the x_content_post custom model as a Char field or a second custom tag model x_content_tag, depending on whether the client wants tag-based filtering across both fans and posts.

Fans-CRM Chat Assistant templates, bulk message scripts, and automated reply rules are platform-native automation logic that has no Odoo equivalent in standard CRM scope. We do not migrate these. During discovery we capture screenshot exports and structured notes of every active template (trigger condition, message body, delay, personalization variables) and deliver them in a written Template Inventory document so the client's admin can rebuild them in Odoo Email Marketing, Odoo Social, or Odoo Studio.

Fans-CRM bulk messaging campaigns with fan segmentation, message sequences, and performance tracking do not map to Odoo CRM. We document the campaign structure (segment filter criteria, message cadence, performance metrics) during discovery and deliver it as a written Campaign Inventory. Rebuild options include Odoo Email Marketing for fan email sequences, Odoo SMS for text campaigns, or Odoo Social for social media engagement. Which tool depends on the client's channel priorities.

Fans-CRM's official OnlyFans platform connection is a platform-access feature that cannot migrate. Odoo CRM does not have a native OnlyFans integration. The client's admin must re-establish the OnlyFans account connection through whatever browser or API method OnlyFans supports independently of Fans-CRM. We do not attempt to transfer session cookies or authentication tokens from Fans-CRM's anti-detect browser environment.

Fans-CRM's AI-powered Chat Assistant and automated reply rules are proprietary platform logic that cannot be extracted as portable configuration data. We do not migrate them. We deliver a written description of the Chat Assistant's current behavior (trigger phrases, response routing, escalation rules) so the client's admin can evaluate Odoo helpdesk automation or third-party AI reply tools as replacements.

Fans-CRM's bundled anti-detect browser stores OnlyFans session data (cookies, fingerprints, IP bindings) that are specific to that browser environment and have no portable equivalent. These sessions cannot transfer to Odoo CRM or any other platform. We flag this during scoping so the client's admin understands that OnlyFans re-authentication will be required after migration. Odoo CRM handles this limitation by running OnlyFans access through standard browsers with standard security practices.