Migrate from FranConnect to Odoo CRM

FranConnect Leads map to Odoo CRM Lead records. The Lead status, source category, owner assignment, and associated drip campaign membership migrate as custom fields on the Lead. We extract drip campaign enrollment as a computed property (e.g., campaign_id and enrollment_date) stored in an Odoo Char or Selection field. Territory assignment from FranConnect maps to a custom field on the Lead. No native Odoo Lead field exists for drip campaign sequence step; we represent campaign state as text properties for the customer's admin to rebuild in Odoo Automated Actions post-migration.

FranConnect Contacts (both franchisor staff and franchisee representatives) map to Odoo res.partner records. Standard fields (name, email, phone, address) migrate directly. For franchisee representatives, we set Partner Type to Individual or Company as appropriate. Custom contact properties from FranConnect map to custom fields on res.partner using Odoo's ir.model.fields API. We resolve the country/state from FranConnect address fields to Odoo's country_id and state_id lookups using ISO country codes.

FranConnect Units represent franchise locations and have no direct Odoo CRM equivalent. We map Units to Project records (project.project) using a naming convention of Unit-[Unit Number]-[Location Name]. Each Project inherits the site address as the Project Address, the owner/franchisee as a Follower, and custom fields for unit_status, opening_date, and territory_id. If the customer requires unit-level reporting across a portfolio, we recommend a custom site model as a separate configuration; this is designed during the schema phase.

FranConnect Franchisees are the individuals or entities operating units. We map Franchisee records to res.partner with a custom field franchisee_role__c (char or selection) storing the franchisee type (e.g., individual owner, corporate franchisee, master franchisee). Agreement dates, territory exclusivity flags, and ownership stakes migrate as additional custom fields on the partner record. Multi-unit franchisees get one res.partner record with a custom units_managed__c field listing associated Unit IDs.

FranConnect Territories define geographic boundaries tied to franchise agreements and have no native Odoo equivalent. We map Territory records to a custom Odoo model (e.g., franchise.territory) with fields for territory_name, geographic_definition (text description or polygon JSON if available), exclusivity_flag (boolean), and associated_unit_ids (one2many to Project). Geographic coordinate data from FranConnect, if present, migrates as a text field for the customer's admin to integrate with a mapping tool if needed.

FranConnect Tasks and checklists for opening procedures and compliance workflows map to project.task records linked to the corresponding Unit Project. Task groups become project.task records with a parent_id hierarchy for grouped checklists. Mandatory/optional flags and reminder schedules migrate as custom fields. We do not migrate active reminder triggers; these are represented as documentation for the customer's admin to rebuild using Odoo Planned Actions.

FranConnect Site Visit records (inspections, audits, compliance visits) map to project.task records with a visit_scheduled_date, completion_status, scoring_data, and response_analysis. If visit records carry structured audit data, we recommend a custom visit model during schema design so that scoring and response fields are typed correctly. We preserve the visit summary as a large text field for reporting continuity.

FranConnect Royalty Manager stores invoices, payments, and royalty calculations tied to Units and Franchisee agreements. Migration requires Odoo Accounting to be installed. If Odoo Accounting is present, Royalty invoices map to account.move records (type=out_invoice) with the franchisee partner as the partner_id and the Unit/Project referenced in an invoice line description. If Odoo Accounting is not in scope, we migrate Royalty records as a custom financial model for the customer's admin to import into their accounting system of record. We flag this decision during discovery.

FranConnect Training module tracks learning completion and certifications for franchisee employees. We migrate training enrollment records and completion status to a custom enrollment model. Quiz scores and course-specific metadata do not have a native Odoo equivalent and migrate as JSON text or are excluded based on customer priority during scoping. LMS-specific course content (video, SCORM) does not migrate.

FranConnect stores documents linked to Leads, Units, Franchisees, and Tasks. We extract document metadata (filename, mime_type, creation_date, URL) and migrate as ir.attachment records linked via res_model and res_id to the corresponding migrated record. File binary transfers are handled via FranConnect's document export API, and files are attached to the Odoo record using ir.attachment's datas field (base64-encoded) or stored as external URLs.

FranConnect Trouble Tickets tied to franchisee users map to Odoo Helpdesk Ticket if the customer installs the Odoo Helpdesk app. Ticket status, department assignment, and conversations migrate to the helpdesk.ticket model. If Helpdesk is not installed, we map Support Tickets to CRM Leads or a custom ticket model. Conversation threads migrate as message records on the ticket.

FranConnect Owners (franchisor staff managing leads, units, and operations) map to Odoo res.users records. We resolve owners by email match against the Odoo destination User table. Any FranConnect Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive FranConnect owners map to inactive Odoo Users to preserve assignment history.

FranConnect's BI module generates platform-rendered visualizations and franchise performance dashboards. These are not exportable as data. We migrate the underlying data (Lead counts, Unit status, Royalty totals, Training completion rates) as custom fields on the migrated objects so that the customer's admin can rebuild equivalent reports in Odoo Reporting or a BI tool of choice. The dashboards themselves are not migrated.