Migrate from Fortifi to Odoo CRM

Fortifi Customers map to Odoo res.partner records. We distinguish between company-type partners (parent_id set) and individual contacts using the Customer Type field. Standard fields (name, email, phone, address) map directly. Any Fortifi custom properties on Customers migrate to custom fields on res.partner created via Odoo Studio or a custom module. Partner IDs are preserved in an external reference field for reconciliation.

Fortifi Actions (behavioral event logs tracking customer interactions) map to Odoo crm.activity records. Action type classifications from Fortifi become activity_type values in Odoo. We preserve the action timestamp, customer reference, and type metadata so reporting dashboards that depend on action history retain their data foundation. Large action volumes (exceeding 100,000 records) migrate via batched API calls with Odoo's XML-RPC with chunking.

Fortifi Conversions (goal completions tied to marketing or sales workflows) map to Odoo crm.lead records. Attribution data from Fortifi (source channel, campaign, UTM values) migrates to crm.lead fields or custom fields on the lead. The customer link resolves to a res.partner record created earlier in the migration sequence. Funnel stage from Fortifi maps to crm.stage within the customer's designated pipeline team.

Fortifi Interactions (customer touchpoints across support and engagement channels) map to Odoo mail.message records linked to the relevant res.partner. Channel type (email, phone, chat, social) migrates to the message_type and author_id fields. Timestamps are preserved to maintain the chronological interaction log in Odoo's chatter. Interaction metadata (duration, disposition) migrates to custom fields on mail.message if required.

Fortifi Email records (sent, delivered, opened, bounced states with template associations) map to Odoo mail.message records with message_type = email. Template associations migrate as custom fields or attachments. Bounce status from Fortifi maps to Odoo's mail.mail state tracking. Email history and campaign attribution data are preserved so the customer can rebuild campaign reporting in Odoo.

Fortifi Invoices (full financial data including line items, payment status, due dates, and tax codes) map to Odoo account.move records with move_type = out_invoice. Customer linkage resolves to res.partner. Line items migrate to account.move.line records with proper account_id, quantity, and price_unit. Payment status and due dates preserve so the customer can run aging reports in Odoo Invoicing post-migration.

Fortifi Subscription records (recurring billing models, cycles, and plan assignments) map to Odoo sale.subscription if the customer enables the Subscriptions app. Plan definitions, billing cycle, and linked invoices migrate as subscription template and account.move references. Advanced billing rules (prorated cancellations, upgrade paths) require manual review and reconfiguration in Odoo because they often involve Fortifi-specific logic not directly translatable to Odoo's subscription model.

Fortifi Pipeline definitions and stage associations map to Odoo crm.team (pipeline container) and crm.stage (stage values within each pipeline). We create crm.team records per Fortifi pipeline and configure crm.stage records with the corresponding stage names and sequence order. Stage-to-pipeline linkage migrates as crm.team assignment on crm.lead.

Fortifi custom properties on Customers and other objects map to Odoo custom fields. In Odoo Community, custom fields require a custom module with Python class inheritance of the target model and XML view modification. In Odoo Enterprise or with Studio, custom fields can be created via the UI on res.partner, crm.lead, and account.move. We assess the customer's Odoo edition during scoping and create fields via the appropriate method before data import.

Fortifi Users (with role and permission assignments) map to Odoo res.users. We match by email address. Role names from Fortifi migrate as custom fields on res.users or as Odoo group membership (Sales Manager, Sales User, etc.). Permission set details may require post-migration verification because Fortifi's permission model and Odoo's group-based access control do not map one-to-one.

Fortifi automation rules, dunning sequences, and renewal triggers are configuration-level settings rather than exportable data records. We document the workflow configuration during discovery (trigger conditions, actions, delays, and escalation paths) and deliver a written inventory for manual re-implementation in Odoo. Odoo automated actions and server actions provide equivalent functionality but require rebuild as Odoo does not import workflow definitions from external platforms.

Fortifi pre-built and custom reports reference live data connections that do not survive export. We migrate the underlying data (Customers, Actions, Invoices, etc.) so that Odoo's reporting engine can recreate the analyses. The report definitions themselves (chart types, filters, grouping logic) are documented separately for the customer's admin to rebuild in Odoo Reporting or via a BI tool integration.