Migrate from Enterprise Operating System (EOS) to Dolibarr ERP

EOS Rocks map to Dolibarr Project records with quarterly cycle context preserved in the Project Description field and a tag in Dolibarr's Tags module (e.g., Q3-2024, Q4-2024). Rock owner maps to the ThirdParty record in Dolibarr's Project contact tab, and Rock due date maps to Project date fields. Milestone sub-tasks within a Rock migrate as Task records linked to the parent Project via the fk_projet field. We tag each Project with the parent quarter notation so that filtering by quarter is available in Dolibarr's project list view.

EOS Scorecard rows — metric name, numeric value, and measurement date — map to Dolibarr Project records with custom fields added via the ExtraFields system. Each metric becomes a separate Project record with a descriptive name (e.g., Monthly Recurring Revenue - Q3), the metric value stored in a numeric custom field, and the measurement date stored in the date_debut or date_fin field. For time-series analysis, we group Scorecard entries under a parent Project named after the metric category, creating a hierarchical project structure in Dolibarr that supports filtering across quarters.

EOS Issues raised during Level 10 Meetings and tracked through the Identify, Discuss, Solve workflow map to Dolibarr Task records. Issue status (New, In Progress, Solved) maps to Dolibarr Task status values (Todo, In Progress, Done), and the Issue owner maps to the assigned user in Dolibarr. The IDS workflow step is stored in a custom Task field so that the customer can preserve the problem-solving stage notation. Issues linked to a specific Rock are connected via the Task's fk_projet reference if the Rock was migrated as a Project.

EOS People records with seat assignments, accountability chart positions, and CAP ratings (Communicator, Asset, Passion) map to Dolibarr ThirdParty records of type Contact. The CAP ratings are stored as free-text in EOS One, so we migrate them into a Dolibarr Note attached to the ThirdParty record rather than into structured fields. The EOS seat assignment (which leadership seat the person occupies) maps to the Function field or a custom ThirdParty field. Team hierarchy from the accountability chart is preserved through the ThirdParty's Parent relationship if the org chart has reporting lines.

Level 10 Meeting outputs — structured agenda sections (Scorecard review, Rock review, To-Do list, IDS issues, Announcements) — migrate as a Dolibarr Project named with the meeting date and team. The meeting's Scorecard review and Rock review items migrate as Task records linked to that Project. Action items from the meeting To-Do list migrate as separate Task records with assigned user and due date. The meeting notes body migrates as a Note attached to the Project so that the full agenda content is preserved without requiring manual reconstruction.

The annual V/TO document (Vision, 3-Year Picture, 1-Year Picture, Rocks, People) migrates as a Dolibarr Project named V/TO with the year in the description. Each V/TO section migrates as a Note attached to the Project, preserving the full structured document content. Where the V/TO contains goal lists (1-Year Picture objectives, annual Rocks), we parse these into Task records linked to the V/TO Project so that the customer can track progress against the annual vision inside Dolibarr's project management view.

EOS Process documentation stored as structured text in EOS One migrates to Dolibarr Note records attached to the relevant Project or ThirdParty. For teams using the EOS Process Builder tool, we preserve formatted process content as HTML Notes. Free-text SOPs without structured fields land as plain-text Notes. We flag during scoping whether Process documentation was stored with the EOS Process Builder or as free-text, because Process Builder output requires more careful parsing to preserve formatting in Dolibarr's Note rendering.

Periodic team health surveys aligned to EOS's Six Key Components migrate as a Dolibarr Project named Org Checkup with measurement period as the date range. Numeric health scores migrate into custom numeric fields on the Project (one per Key Component). Free-text commentary from the survey migrates as a Note attached to the Project. The customer can use the Project's task list to track action items raised from the Checkup findings.

Core organization settings from EOS One — company name, fiscal year, and team hierarchy — are configuration-level data that do not have a direct Dolibarr equivalent in the standard database schema. We extract these values during scoping and document them in a migration handoff sheet for the customer's Dolibarr administrator to configure manually in Dolibarr's Setup > Company menu. Meeting templates and meeting frequency settings do not have a Dolibarr migration path and are documented for admin review.

EOS One integrations (calendar sync, email, Google Drive) connect through OAuth or API tokens that cannot be exported or migrated. These connections must be re-established manually in Dolibarr or documented for the customer's admin team to rebuild post-migration. We do not migrate integration connection states. The customer's IT team or Dolibarr administrator sets up calendar and email integrations from scratch in the new system.

Where customers have EOS Implementer session recordings, agendas, or slide decks stored in EOS One, we migrate these as Note records attached to the relevant V/TO or meeting Project. The implementer relationship itself cannot migrate, but historical session context preserved in notes gives the customer's leadership team continuity during the transition to Dolibarr's project management approach.

EOS Rock milestone sub-tasks migrate as Dolibarr Task records with a fk_projet reference pointing to the parent Rock Project. Milestone due dates and completion status map directly to Task date fields and status. Each milestone sub-task is connected to its Rock owner through the Task's assigned user field. We validate the Rock-to-milestone relationship after import to ensure no milestones are orphaned from their parent Rock Project.