Migrate from Enterprise Operating System (EOS) to Infor CloudSuite Corporate

Rocks migrate to Infor CloudSuite Projects with their milestone sub-tasks as child Task records in the project WBS hierarchy. We tag each Project with a fiscal period custom field carrying the parent quarterly cycle (Q1/Q2/Q3/Q4 + year) so that cycle context is preserved after import and the Infor project list can be filtered by EOS quarter. Rock owner (individual) maps to the Project Manager field in Infor. Status, due date, and description migrate directly. If the destination is Infor CloudSuite Industrial or Manufacturing, Projects may map to Production Orders or Work Orders depending on the Rock type flagged during scoping.

The V/TO annual document decomposes into a hierarchy of Infor CloudSuite Goal records (vision and 3-year picture), Initiative records (1-year picture and annual Rocks), and Target records (quarterly milestones). The CAP card section for each People seat becomes a custom field group on the linked Employee record. This is the most complex object transformation because the EOS V/TO document stores multiple levels of strategic content in a single structured block; we parse it during the normalization step and reconstruct it as a relational hierarchy in Infor. Process documentation stored within the V/TO migrates separately to Infor Document Management.

EOS Scorecard rows (metric name, unit, value, measurement date) migrate to Infor CloudSuite KPI Actual records linked to a KPI Framework header. We preserve the weekly measurement cadence by setting the ActualDate to the original EOS scorecard timestamp and the MetricName to the KPI Description. Where EOS Scorecard metrics map to Infor Financial Management modules (budget vs actual), we link the KPI Actual to the corresponding GL account or cost center. High-frequency Scorecard histories (daily or weekly entries spanning multiple years) are chunked by fiscal year to avoid exceeding Infor ION batch size limits.

Each EOS Level 10 Meeting migrates as an Infor CloudSuite Event record with structured fields for meeting type (Level 10), date, facilitator, and score. Agenda topics (Rocks review, Scorecard review, IDS section) migrate as Event detail lines or linked Task records. Issues raised during the IDS section migrate to Infor Case records with the original Issue description, owner, status, and resolution notes preserved. The EOS Issue-to-Case mapping uses the IDS workflow status to set the Infor Case Status field.

EOS Issues with IDS workflow status (Identified, Discussed, Solved) map directly to Infor CloudSuite Case records. The Issue title becomes the Case Subject, description becomes the Case Description, owner maps to the assigned Case Owner, and IDS status maps to Case Status. Issues without a resolution (Identified or Discussed only) become open Cases in Infor; Solved Issues become Closed Cases. We link each Case to the parent Event record (the Level 10 Meeting where the Issue was raised) via the WhatId relationship for traceability.

EOS People records migrate to Infor CloudSuite Employee records with seat assignment mapped to Department or Job function. CAP ratings (Communicator, Asset, Passion) are free-text fields in EOS One; we parse the text values against the customer's stated rating scale and populate custom picklist fields (e.g., cap_communicator__c, cap_asset__c, cap_passion__c) on the Employee record. Where CAP ratings are stored as unstructured text, we flag them during normalization and preserve the raw text in a custom long-text field for manual categorization post-migration. Accountability chart hierarchy (who reports to whom) maps to Infor's organizational reporting structure.

EOS Process Builder documents and free-text SOP records migrate to Infor CloudSuite Document Management as structured text files (RTF or HTML) attached to the relevant department or project. Where processes were built using the EOS Process Builder tool, we preserve the document structure and any linked visual elements as attachments. Standard operating procedures in EOS One that reference Rocks or People seats are relinked to the corresponding Infor Project and Employee records post-migration. Process documentation migrates as a document blob, not as workflow-configured process objects.

EOS Org Checkup numeric scores (Six Key Components assessment) migrate as Survey Response records in Infor CloudSuite, with score aggregates mapped to the relevant KPI Framework category. Free-text commentary on checkup responses migrates to a custom Notes field on the Survey Response. Historical checkup results spanning multiple quarters are loaded as separate response records with the assessment date preserved for trend analysis in Infor Birst.

EOS org-level settings (company name, team structure, fiscal year) migrate to Infor CloudSuite Company records with the fiscal calendar configured to match the EOS quarterly cycle (four fiscal quarters aligned to the Rock cadence). Team hierarchy from the EOS Accountability Chart maps to the Infor organizational structure under the Company record. Meeting templates and UI-level settings from EOS One are not exportable via standard CSV and do not migrate; the Infor implementation team configures these during onboarding.

EOS One integrations to calendar, email, and Drive tools have no documented REST API for migration. We cannot export integration connection states or OAuth tokens from EOS One. Calendar integrations migrate as a written reference of which EOS meetings were connected to which external calendars so the Infor implementation team can re-establish native Infor Calendar integrations post-migration. Drive documents that were attached to EOS records migrate as file attachments to the corresponding Infor Document Management records.