Migrate from Follow Up Boss to Odoo CRM

Follow Up Boss Person records map 1:1 to Odoo crm.lead records with type='lead'. Stage, tags, assigned agent, custom fields, and original create date all migrate. The lead's name is split into contact_name; emails go to email_from. Unmatched agent emails default to the migration admin account.

Follow Up Boss Company records map to Odoo res.partner with company_type='company'. The company's name, website, address fields, phone, and industry (as a custom field) transfer directly. FUB primary-company association on a Person creates a partner_id link on the corresponding crm.lead.

Follow Up Boss Deal records map to Odoo crm.lead with type='opportunity'. Deal name becomes the opportunity name, amount maps to planned_revenue, and close date maps to date_deadline. The assigned agent resolves by email to an Odoo user_id. Pipeline and stage require explicit mapping to Odoo stage_id per crm_team.

Follow Up Boss agents assigned to People and Deals resolve to Odoo res.users records by email address lookup. Unmatched agents are flagged before migration; their records assign to a designated fallback user so no lead lands without an owner. Agents who do not yet have Odoo accounts must be invited first.

Follow Up Boss Action Plans are drip sequences, task triggers, and auto-responses tied to lead stage transitions. Odoo has no native Action Plan equivalent; its automation tools (Studio automations, ir.actions.server) work differently. We export Action Plan definitions as a structured reference document so your Odoo admin can rebuild each plan in Odoo's automation framework.

Follow Up Boss Smart Lists store filter-and-sort logic by lead source, stage, date range, or custom field values. Odoo's ir.filters handle saved filters but the query logic is platform-specific. We export Smart List definitions (field names, operators, values) as a rebuild reference for Odoo groups and saved filters.

Follow Up Boss tags migrate to crm.tag records and attach to crm.lead via tag_ids. Tags on Companies attach to res.partner via category_id. Each FUB tag name creates a matching crm.tag record; duplicate tag names across People and Companies merge into a single Odoo tag where the context allows.

Follow Up Boss custom fields of type text, date, or number map to Odoo custom fields (ir.model.fields) on crm.lead or res.partner as appropriate. The field name normalizes to snake_case. Odoo creates these as custom fields on the target model before migration loads the data.

Follow Up Boss dropdown custom fields map to Odoo selection fields on crm.lead or res.partner. Each FUB dropdown choice value maps to a corresponding Odoo selection option label. If Odoo selection options do not exist yet, we create them during the schema setup phase. Mismatched or orphaned values default to the first Odoo option.

Follow Up Boss call logs and emails migrate as Odoo mail.activity records linked to the parent crm.lead, preserving the original timestamp, activity type (call, email), and agent who logged it. Notes and Background text on a Person merge into the crm.lead description field. Plain text migration keeps formatting simple; rich-text notes are stored as-is.

Follow Up Boss stages map to Odoo crm.stage records scoped to each crm_team (sales team). Stage names and probabilities map value-by-value; the FUB pipeline name becomes the Odoo team name. Each stage's sequence order is preserved. If your Follow Up Boss account has multiple pipelines, each creates a separate Odoo crm_team with its own stage set.

Follow Up Boss lead source values migrate to Odoo utm.source records, linked to crm.lead via source_id. If a source value in Follow Up Boss has no matching Odoo utm.source record, we create one during migration. The source name is preserved exactly so existing attribution reports remain meaningful.

Follow Up Boss internal record IDs and original create dates are stored as custom fields on Odoo records (e.g., FUB_Person_ID__c, Original_Create_Date__c) for traceability, deduplication on delta runs, and reporting continuity. These fields are readable but not editable in Odoo's standard UI.

Follow Up Boss file attachments on People or Deals re-upload to Odoo ir.attachment records linked to the parent crm.lead or res.partner. Original filenames and content types are preserved. Large files are subject to Odoo's attachment size configuration; we flag any files exceeding the target system's limits before migration.

Follow Up Boss stores FUB number identifiers used for SMS routing and inbound call attribution. Odoo does not have a native FUB number field. We preserve FUB number values in a custom text field on the lead record so the data is visible but not used by Odoo's telephony module, which must be configured separately if SMS routing is needed.