Migrate from Timefold to Odoo CRM

Timefold employees map to Odoo res.partner records. Skills, availability windows, and contract constraints become custom fields on the partner. Email-matched users receive Odoo internal user records with active status; others become inactive partners with a Source_System__c reference preserving the original Timefold identifier for reconciliation. For example, a Timefold employee with email [email protected] and skills 'HVAC Certification' and 'Forklift Licensed' creates an active Odoo user with custom fields skill_ids and availability_window__c populated.

Timefold shifts, visits, and route stops are not native Odoo CRM entities. FlitStack AI creates crm.lead records per planning entity, populating custom fields (shift_date, planned_hours, visit_address, visit_priority) to preserve scheduling metadata. Constraint configuration applied to each lead is stored as a JSON custom field for rebuild reference.

Customer locations stored as problem facts in Timefold merge into the partner address on res.partner and into visit_address on the corresponding crm.lead. Geographic coordinates (latitude/longitude), time windows, and service duration migrate as custom fields on the crm.lead record for geospatial queries and service-level agreement tracking in Odoo after migration.

Vehicles and capacity resources from Timefold map to a custom resource model in Odoo (stock.quant or a dedicated res.partner subclass). Vehicle capacity and utilization percentages migrate as custom float fields on the resource record, linked to visits (crm.lead) via a Many2one relationship.

Timefold skill requirements and constraint rules have no native Odoo equivalent. Each skill tag migrates to a custom text or char field on crm.lead. The constraint configuration (required skills, minimum qualifications, legal compliance rules) is exported as JSON and stored in a constraint_config__c custom field for your Odoo admin to translate into Studio rules.

Timefold's hard/medium/soft score and score breakdown migrate as custom integer fields on each crm.lead record. This preserves the optimization quality of the original schedule without requiring Odoo to rerun the solver. Score__c stores the overall score; Hard_Score__c and Soft_Score__c store individual constraint levels.

Timefold constraint configurations (e.g., employee availability rules, travel time limits, fairness constraints) are model-level definitions. No native Odoo equivalent exists, so FlitStack exports each configuration as a JSON blob in a Constraint_Config__c custom field on crm.lead as a reference for manual Odoo Studio rebuild.

Timefold platform members are matched to Odoo res.users by email. Active Timefold members receive active Odoo users; inactive members become inactive Odoo users with a Source_System_ID__c reference. Roles and tenant assignments are not portable and require Odoo access rights configuration post-migration.

Timefold visits and appointments with confirmed start and end times map directly to Odoo calendar.event records, linked to the partner (res.partner) and optionally to the corresponding crm.lead. Original planned times and actual times are preserved in separate datetime fields. This ensures scheduling continuity for customer-facing appointments and enables Odoo calendar views and reminders post-migration.

Sub-tasks and sub-activities within a Timefold shift or visit map to Odoo mail.message records attached to the crm.lead or calendar.event. Original task names, descriptions, and status flags migrate as custom fields and message body text for full activity audit trail continuity.