Migrate from Fello to Odoo CRM

Fello's AI lead score has no native Odoo equivalent — custom field creation required before import

Fello generates a 0–100 lead score using proprietary real-estate AI that analyzes listing propensity, market data, and engagement signals. Odoo CRM has no native equivalent field on res.partner — the native lead scoring module in Odoo Enterprise uses behavioral signals rather than Fello's model. If you want the score visible in Odoo, our migration engine creates a custom float field x_fello_lead_score on res.partner before the import runs. Without this, the score is lost. The score does not drive Odoo's native predictive AI scoring — that runs independently on Odoo's own signals.

Fello Smart Workflows do not migrate — consent-based outreach sequences must be rebuilt in Odoo Studio

Fello Smart Workflows automate outreach based on lead score thresholds, TCPA consent status, and listing-propensity changes. Odoo has no workflow migration path — automations in Odoo are built as server actions, automated actions (ir.actions.server), or Odoo Studio flows, none of which are generated by data migration tools. We export Fello workflow definitions as a JSON blueprint mapping triggers (score > 70, consent = True) to Odoo action types. Rebuilding typically takes 2–4 hours per workflow depending on complexity. Fello's Scale plan includes Smart Workflows; the absence of these in Odoo is a significant process change your team should plan for before go-live.

Odoo's crm.lead stage_id requires pre-created stage records before import — flat CSV imports fail without them

Odoo's crm.lead.stage_id field is a many2one pointing to crm.stage records that must exist in the database before leads are imported. Fello has no equivalent stage object — contacts are scored but not staged. If your team uses Fello's implicit pipeline model (e.g., 'Hot', 'Warm', 'Cold' based on score), we translate score ranges to Odoo stage names and create the corresponding crm.stage records during migration setup. The stage creation must happen before any lead import; otherwise Odoo rejects the import with a foreign-key constraint error on stage_id.

Fello's TCPA consent flag is platform-native — Odoo has no compliance model so the field must be custom

Fello builds TCPA consent collection directly into its contact forms and stores consent timestamps per record. This is a Fello-native compliance feature with no Odoo equivalent — Odoo does not have a built-in consent management module in its CRM. Our migration creates x_tcpa_consent (boolean) and x_tcpa_consent_date (datetime) custom fields on res.partner to preserve the consent record. These are reference fields only — Odoo's email marketing tools (mass_mailing) do not automatically read them. Your team must configure Odoo's mailing list consent checks manually post-migration to ensure the compliance logic carries forward.

Fello CSV export does not include activity history — logged calls, emails, and meeting notes require separate extraction

Fello's contact export (Settings > Import & Export > Export) produces a flat CSV of contact records with current field values. It does not include the activity log — call logs, email threads, meeting records, and note history are stored separately in Fello and are not surfaced in the standard export. Odoo's crm.lead model supports activity tracking via mail.message and crm.phonecall, but these must be created programmatically from extracted Fello activity data. If your team relies on historical engagement notes for pipeline context, a separate activity extraction step is required before or after the main migration run.