Migrate from Flowlu to Odoo CRM

Flowlu Contacts map to Odoo res.partner records with partner_type set to contact. Email is the dedupe key; we run deduplication before insert and flag duplicates for customer review. Custom fields on Contacts (list, text, date, checkbox types) require pre-creation in Odoo via Studio or developer mode because Flowlu does not export custom field type definitions through its API in a form that maps directly to Odoo field types. We extract the full custom field schema per object during scoping and create matching Odoo custom fields before the contact import phase begins.

Flowlu Companies map to Odoo res.partner records with partner_type set to company. The company name maps to the name field and industry to industry_id via Odoo's industry taxonomy. Address, website, and phone fields migrate directly. Flowlu's contact-to-company relationship (one contact linked to one company) maps to the parent_id on the Contact partner record. We create company partners first so that the parent_id reference is satisfied when contacts import.

Flowlu Opportunities map to Odoo crm.lead records. The pipeline stage, amount, probability, expected close date, and custom fields migrate. Flowlu's pipeline is defined in Flowlu settings and carries stage names and probability values; we create a matching Odoo CRM stage set before opportunity import so that stage_name and probability map correctly. Owner assignment migrates via email lookup against Odoo User records.

Flowlu Pipelines define deal stages with display order and probability. Each Flowlu pipeline maps to an Odoo CRM stage set configured in CRM > Configuration > Stages. Stage probability percentages migrate to the Odoo stage probability field. Active deals retain their current stage and pipeline assignment at migration time so the pipeline view in Odoo reflects the same deal positions as the Flowlu board.

Flowlu Tasks live inside Projects and carry parent-project relationships, assignees, due dates, and time tracking. We map tasks to Odoo based on destination scope: tasks without a parent project map to CRM Activities (mail.activity) as a log activity on the related Contact or Opportunity; tasks with a parent project map to project.task if Odoo Project app is installed. Task dependencies from Flowlu are documented but cannot be natively recreated in Odoo CRM Activities because Odoo does not have a native dependency chain feature in the CRM module. We provide a task-dependency map in the handoff document.

Flowlu Product Catalog entries map to Odoo product.product records. Product name, SKU (hs_sku equivalent), list price, and cost price migrate. If Flowlu products carry custom fields (e.g., weight, dimensions), those require pre-created custom fields in Odoo before import. Product categories map to Odoo product.category records.

Flowlu Invoices map to Odoo account.move records with move_type set to out_invoice. This mapping requires the Odoo Accounting app to be installed and configured in the destination environment. Flowlu invoice line items, tax rates, payment status, and issuer details map to the corresponding Odoo invoice fields. Invoices linked to closed Flowlu Projects may reference parent Projects that do not exist in Odoo CRM; we attach these invoices to the related Contact partner record and flag orphaned references for the customer's admin. Historical invoices are migrated as readonly records.

Flowlu Users (admins, managers, members) map to Odoo res.users records by email match. Owner assignment on Flowlu records (contacts, companies, opportunities, tasks) migrates by resolving the Flowlu owner email to the Odoo User record's partner_id. Any Flowlu owner without a matching Odoo User is placed in a reconciliation queue for the customer to provision before the record import phase continues. Team groupings in Flowlu do not map to Odoo Odoo Teams automatically; we document the team structure for the admin to configure in Odoo after migration.

Flowlu Custom Fields attach to Projects, Tasks, Opportunities, Contacts, Companies, and Knowledge Base articles. Each custom field has a type (text, number, date, list, checkbox, object picker) and may be required or read-only. During scoping we extract the complete custom field schema per object type and create matching Odoo custom fields via Studio or the fields API before data import begins. List-type fields in Flowlu map to Odoo selection or many2one fields depending on whether the list references a static set or a dynamic object picker. Required-field constraints are replicated in Odoo validation rules.

Flowlu Time Entries log hours against Tasks or Projects with user assignment, date, duration, billable flag, and optional description. We map billable time entries to Odoo account.analytic.line (timesheet) records if the Odoo Timesheet app is installed; otherwise time entries are mapped to mail.activity records attached to the relevant CRM record. Time entry-to-task parent references resolve to the corresponding Odoo project.task or CRM activity at migration time.

Flowlu Notes attached to Opportunities, Contacts, or Companies map to Odoo note.note records linked via mail.activity.model and mail.activity.res_id to the parent CRM record. Rich text content migrates as plain text with basic formatting preserved where possible. Note creation date maps to Odoo's create_date for timeline ordering.

Flowlu Agile Projects use sprints, backlogs, issue trackers, and story points that have no direct Odoo CRM equivalent. Odoo does not ship a native Agile or Scrum module in its standard app set; teams requiring Agile tracking typically install a third-party Odoo app or use the Project app with task stages configured as a kanban. We document the Flowlu sprint backlog, issue assignments, and story point values in a structured export for the customer's admin to manually rebuild in Odoo Project if that app is in scope.