Migrate from Flexie to Odoo CRM

Flexie Workers map to Odoo CRM Contacts. Name, email, phone, and employment status migrate as standard Contact fields. Availability windows (Flexie's weekly availability blocks) migrate as custom Char or Text fields since Odoo CRM has no native availability schedule object; a separate availability summary note is attached to each Contact. Worker's employment type and hourly rate become custom fields on the Contact.

Flexie Venues map to Odoo CRM Accounts. Venue name becomes Account name, address fields map to the Account's street, city, state, zip, and country. Venues with child locations (franchise branches) can be mapped as child Accounts via the parent_id lookup, preserving the multi-location hierarchy. Operational settings specific to the venue (scheduling rules, coverage thresholds) become custom fields on the Account.

Flexie Shifts have no native Odoo CRM equivalent. Odoo CRM has Task and Event objects but no shift scheduling object. We migrate Shift records as Notes attached to the Account (Venue) with a structured body: shift date, start time, end time, duration, required headcount, and current fill status. Alternatively, for customers who want to track shift activity in the CRM timeline, we create Task records with a custom shift_type field and attach them to the related Account and Contact (assigned Worker). The customer selects the strategy during scoping.

Flexie Shift Assignments—the junction between Workers and Shifts—map to Odoo CRM Tasks linked via the Worker's Contact record and the Venue's Account record. Assignment status (confirmed, pending, declined), notes, and timestamps migrate as Task fields. Unfilled shifts (coverage gaps) are documented as Tasks with no assigned Contact and a custom status field, giving managers a coverage gap report in Odoo.

Flexie Entity Forms are data entry points and workflow triggers with no direct Odoo equivalent. Form submission records are treated as field data and mapped to custom fields on the relevant Odoo object (Contact for worker-facing forms, Account for venue-facing forms). Form structure and submission history are documented for manual Odoo Studio configuration. The form logic (validation rules, conditional visibility) requires manual rebuild in Odoo.

Flexie Workflows are automation sequences built on triggers and actions that are platform-specific and cannot be migrated 1:1. We document every active Flexie Workflow with its trigger object, conditions, actions, and intended outcome. The Odoo replacement uses Studio automations (record rules, time-based actions) and server actions defined in XML. We provide the documented workflow inventory and recommended Odoo equivalents, but the rebuild is a separate engagement or internal admin task.

Flexie uploaded files attached to Workers, Shifts, or Venues migrate as Odoo ir.attachment records linked to the corresponding Contact (Worker), Account (Venue), or Task (Shift Assignment). We extract document metadata (filename, file type, upload date, attached record reference) and import it to Odoo. Actual file hosting requires separate data transfer from Flexie's storage to Odoo's document management or an external DMS.

Flexie custom properties on Workers vary per account. We extract the live custom property schema during discovery, map each property to a typed Odoo Contact field (Char, Integer, Float, Selection, Many2one, etc.), and pre-create any missing fields in the Odoo database via XML before migration. Multi-select picklists become Selection fields; relationship properties require Many2one fields pointing to pre-created related records.

Flexie custom properties on Venues migrate to custom fields on the Odoo Account. Venue-specific operational settings, scheduling constraints, and coverage thresholds map to Char, Boolean, or Selection fields on Account. Venue-specific picklist values are pre-created as Odoo Selection field options before migration.

Flexie custom properties on Shift records map to custom fields on the Odoo Task representing the Shift. Shift-specific attributes (uniform requirements, equipment needs, break policy) become Char or Text fields on the Task.

Flexie Owner records (managers and administrators) map to Odoo CRM User records by email match. We resolve HubSpot Owner references on Workers, Venues, and Shift Assignments to Odoo User records via the email lookup. Owners without a matching Odoo User are placed in a reconciliation queue for admin provisioning before record import resumes.

Flexie Worker availability windows (day-of-week and time-range blocks) have no native Odoo Contact equivalent. We store availability as a structured custom field on Contact, either as a formatted text block (for display only) or as a serialized JSON field that Odoo's custom reporting or a custom module can parse. Customers with complex scheduling needs are directed to Odoo's Project and Timesheet module as a more complete scheduling solution outside the CRM scope.