Migrate from Actimo to Odoo CRM

Actimo contacts map directly to Odoo res.partner records with standard partner fields like name, email, phone, and street address translating one-to-one. Any company association in Actimo (workspace membership indicating employer) links via partner_id to an Odoo company partner record. The migration preserves the user's original Actimo join date as a custom field and maintains the manager-to-employee relationship by resolving the manager's email to an Odoo system user who becomes the responsible user on the contact record.

Actimo workspaces function as organizational units containing user rosters, department structures, and company-level attributes. Each Actimo workspace translates to an Odoo res.partner record with partner_type set to 'company', preserving the workspace name, industry classification, and company size data. Individual Actimo users within a workspace link to their parent company partner via the parent_id field on res.partner, maintaining the organizational hierarchy in Odoo's contact model. Workspaces without company-level metadata receive a default 'Company' partner designation to preserve the grouping relationship.

Actimo custom properties on contacts (department, shift schedule, employment type, etc.) have no Odoo CRM native equivalent. FlitStack creates Odoo custom fields (x_studio_fieldname) on res.partner before migration. Employment-specific fields like shift patterns or location flags are preserved as reference data — they do not drive CRM logic in Odoo.

Actimo pulse survey scores and response histories do not map to a CRM-native construct. We transform each survey response into an Odoo Note or activity record (mail.message) on the related res.partner, with the survey name and score stored as custom fields (Survey_Score__c, Survey_Name__c). Recurring pulse data creates an activity log for longitudinal reference.

Actimo learning path completion records become Odoo custom fields (Last_Learning_Path__c, Completion_Date__c, Learning_Module__c) on res.partner, plus a mail.activity record documenting the completion timestamp. Actimo's structured training curriculum does not natively map to Odoo eLearning module records — those must be rebuilt separately.

Actimo message records (announcements, updates sent to employees) migrate as Odoo mail.message records linked to the recipient's res.partner. Original send date, sender, and message body are preserved. Thread-level conversation context is lost since Actimo messages are broadcast-style rather than threaded.

Actimo's engagement and NPS scoring model has no Odoo CRM equivalent. Scores migrate to a custom float field (Actimo_Engagement_Score__c) on res.partner. The numeric value transfers but the calculation logic (weighting, recency factors) does not — Odoo does not run Actimo's scoring algorithm automatically.

Actimo onboarding flows (automated step-by-step employee journeys) have no Odoo CRM equivalent. Odoo's closest tools are Odoo eLearning + Studio automation rules, but these must be rebuilt. FlitStack exports the Actimo flow definition as a JSON schema package your Odoo admin can use as a rebuild reference.

Actimo group discussions and social wall activity have no Odoo CRM equivalent. Posts are preserved as text attachments or notes on the relevant res.partner records for historical reference. The interactive, social-layer context of Actimo groups cannot be reconstructed in Odoo's record-centric model.

Actimo assigns owners or managers to users. Odoo res.partner has a optional user_id field (responsible user) for follow-up assignment. We match Actimo owner email to Odoo system users by email. Unmatched owners flag as 'unresolved' before migration commits so your admin can assign a fallback Odoo user.