Migrate from Enterprise Operating System (EOS) to Odoo ERP

Rocks are 90-day priority objects with owner, due date, status, and milestone sub-tasks in EOS One. We migrate each Rock to an Odoo CRM Project record and each Rock milestone to a Project Task child of that Project. The quarterly cycle (Q1-Q4 + year) is preserved as a Project tag (e.g., tag_2024_q1) so that filtering by quarter is available in Odoo's Project kanban and gantt views. Rock status (On Track, Behind, At Risk) maps to the Project stage. The Rock owner is resolved to an Odoo Employee or User record by email match.

EOS Issues with the IDS workflow (Identify, Discuss, Solve) migrate to Odoo Project Task records. The IDS status (Identified, Discussed, Solved) maps to Odoo Task stage values. Issues are linked to the parent Rock Project when the Issue references a Rock in EOS One. Issue owner resolves to Odoo Employee by email. Free-text resolution notes migrate as Task description text.

EOS Scorecard rows store metric name, unit, numeric value, and measurement date per week. We migrate each row to an Odoo CRM dashboard metric record with the metric name, value, and date preserved. Odoo's dashboard builder then renders these as line charts or KPI tiles. The metric-to-project assignment is preserved via a tag so managers can view Scorecard history filtered by team or quarter.

EOS Level 10 Meetings have a structured agenda (scorecard review, to-dos, Rock review, issues, acknowledgments). We migrate meeting metadata (date, duration, attendees) to an Odoo Calendar Event and the structured agenda items as a Note attached to that Event. The to-do items from each Level 10 meeting migrate as Project Tasks tagged with the meeting date so that the cadence of weekly commitments is preserved. We flag upfront that EOS One's native export may not cover all agenda sections, requiring either multi-step export or manual extraction for full coverage.

The V/TO is the annual strategic document covering 3-year picture, 1-year picture, Rocks, and people seat assignments stored as a structured document in EOS One. We export it as a composite text blob and attach it as an Odoo Documents record tagged as V/TO. Because EOS One stores V/TO content as free-text sections rather than typed fields, we cannot parse it into Odoo structured fields without a manual normalization step. We flag this during scoping and provide a structured template so the customer's Odoo admin can repopulate the V/TO content in Odoo's Documents or CRM module as a formatted record.

EOS People records include name, email, seat assignment, accountability chart position, and CAP ratings (Communicator, Asset, Passion) stored as free-text in EOS One. People with a seat assignment (employees) map to Odoo Employee records. External advisors, board members, or contractors map to Odoo Contact records. CAP ratings migrate as text notes on the relevant record because EOS One does not expose CAP ratings as structured fields. Seat assignments (the Accountability Chart) migrate as an Odoo department hierarchy under the Company record.

EOS Process documentation is stored as structured text in EOS One, and where the EOS Process Builder tool was used, it has a specific structure. We export Process records as text blobs and attach them as Odoo Documents records tagged as SOP. Processes built with the EOS Process Builder retain their structural tags if the export preserves them. We flag that free-text Processes without the Process Builder structure land as plain text documents and cannot be automatically converted to Odoo workflow steps.

Core org settings — company name, fiscal year start, and team structure — migrate to Odoo's ResCompany record. The EOS Accountability Chart (people seat assignments by function) maps to Odoo Departments under the Company record. Meeting templates from EOS One are not exportable via standard CSV export and do not migrate; we document the meeting cadence and agenda structure in the handoff inventory so the customer's Odoo admin can configure Odoo Calendar event templates manually.

Periodic Org Checkup surveys aligned to EOS Six Key Components produce numeric scores and free-text commentary. We migrate the numeric scores as Odoo CRM dashboard metric records tagged with the checkup date. Commentary text migrates as a Note attached to the metric record. This preserves the longitudinal trend of team health scores but does not create a native Org Checkup equivalent in Odoo, which does not have a built-in EOS Checkup model.

EOS One integrations connect to Google Calendar, Google Drive, and email. There is no documented REST API for third-party data pull, and integration connection states (OAuth tokens, calendar sync preferences) cannot be exported. We do not migrate integration states. We deliver a written checklist of every EOS One integration connection that must be re-established manually in Odoo (Google Calendar sync, email alias routing, Drive folder re-link). This work is outside migration scope.