Migrate from Enterprise Operating System (EOS) to Epicor Prophet 21

EOS Rocks with owner, due date, status, and milestone sub-tasks map to Epicor Project Task records under a migrated Project record representing the quarterly cycle. Each Rock inherits the parent quarter tag (Q1/Q2/Q3/Q4 + year) as a custom field on the Project Task. Rock milestones map to Epicor sub-tasks using the Epicor Task dependency structure. Rock status (behind, on hold, diff hit, done) maps to Epicor Task status values with a custom field eos_original_status__c preserving the original EOS label. The Rock-to-owner mapping resolves against the Employee record created in the People migration phase before Task import begins.

EOS People records with seat assignments and accountability chart positions map to Epicor Employee records. Each Employee record receives the EOS seat role title, reporting manager (resolved via email match against other migrated People records), and department. Epicor's HR module or basic Employee table is used depending on the customer's Epicor tier and configuration. Owner email from EOS is the dedupe key for matching against existing Epicor Employee records.

EOS CAP ratings (Communicator, Asset, Passion) are free-text fields in EOS One with no standard structure. We extract the CAP text from EOS One CSV exports and create three custom fields on the Epicor Employee record — CAP_Communicator__c, CAP_Asset__c, CAP_Passion__c — preserving the original CAP rating verbatim. If EOS One exports CAP ratings as structured picklist values, we map them to Epicor multi-select picklist fields. This mapping is configuration-dependent on Epicor edition; basic Employee tables require the customer to enable UD fields.

EOS Scorecard rows (metric name, unit, value, measurement date per week) represent a time-series KPI table with one row per metric per measurement period. We migrate Scorecard data into an Epicor User-Defined table keyed on measurement period and metric name. Each row carries value, unit, and source_eos_scorecard flag. For customers using Epicor Dashboard or BI tools, we provide a supplemental CSV import file for Epicor BI/Report Builder that populates a reporting layer without modifying the transactional schema.

EOS Issues tracked through the IDS (Identify, Discuss, Solve) workflow map to Epicor Help Desk Cases if the customer licenses Epicor Service and Support module, or Epicor Project Tasks under a dedicated Issues project if the Help Desk module is not active. Issue status (open, pending, solved) maps to Case Status or Task status depending on destination module. The IDS owner field resolves to the Epicor Employee record via email match. Resolution notes migrate as Epicor Case Resolution or Task completion comments. Issue created date and last modified date migrate to preserve temporal context.

EOS Level 10 Meeting outputs include meeting date, To-Do list, Issues identified, and the quarterly Scorecard score. We split this into two Epicor records: the To-Do items and Issues become Epicor Project Tasks under a Meeting-themed Project record, and the meeting metadata (date, score, attendees by email) becomes an Epicor Document record attached to the Project. The meeting score (1-10) migrates to a custom field on the Document record. Because EOS One meeting notes are stored as structured text blocks rather than typed fields, we parse the CSV export rows by agenda section and reconstruct them as separate Task and Document records.

The EOS V/TO is the annual strategic document covering 3-year picture, 1-year picture, Rocks, People, and core values. Epicor has no native annual planning document equivalent. We migrate V/TO content as an Epicor Document Management record with sections preserved as document chapter headings. The 3-year and 1-year picture text migrates as document body text. People CAP card excerpts and company values migrate as document attachments. This is a best-effort reconstruction; the V/TO's visual layout in EOS One does not translate directly to Epicor's document viewer.

EOS Process documentation stored as structured text in EOS One migrates to Epicor Document Management as Document records tagged by process type. Processes documented via the EOS Process Builder tool (which generates structured step-by-step content) receive priority attention as Epicor Document records with chapter-based navigation. Informal free-text process notes migrate as Epicor Document records with a process_documentation flag. Large SOP volumes (100+ documents) are migrated as bulk Document imports via Epicor DMT with a process_library project grouping.

EOS org settings (company name, fiscal year start, team hierarchy) map to Epicor Company Configuration records. The EOS company name becomes the Epicor Company Name. The EOS team accountability chart (who seats where) migrates to Epicor Employee reporting relationships via manager email matching. EOS fiscal year settings are mapped to Epicor Fiscal Calendar configuration during Epicor implementation. Some EOS meeting templates and branding settings are not exportable and are flagged for manual reconfiguration in Epicor.

EOS Org Checkup periodic team health surveys with numeric scores per Six Key Components and free-text commentary migrate to Epicor custom metrics on the Company or Employee records. Numeric health scores (0-100 scale) become custom numeric fields (org_checkup_score__c, team_health_score__c) with a measurement date field. Free-text commentary migrates as Epicor Document attachments linked to the Org Checkup date record. Org Checkup trend data spanning multiple quarters migrates as a time-series dataset to support longitudinal reporting in Epicor BI.

EOS One integrations with calendar, email, and Drive are connection-state records that cannot be exported via EOS One CSV. Epicor uses a different integration framework (Epicor Service Connect, REST API, IDO-based integrations) that has no structural overlap with EOS integration records. We deliver a written inventory of every EOS integration connection requiring manual re-establishment in Epicor, including calendar sync (Epicor ICE Workflow or third-party integration), email integration (Outlook add-in or Epicor REST API), and any Drive-based document sync. The customer reconciles integrations after Epicor cutover.

EOS Rock ownership spans quarterly cycles (Q1 2024, Q2 2024, Q3 2024, Q4 2024, Q1 2025) that create a temporal context EOS One tracks as a join relationship. In Epicor, quarterly cycle context is preserved by creating a parent Project record for each quarter (e.g., Project: EOS Rocks Q1 2025) and nesting all Rocks from that quarter as child Project Tasks. This preserves the quarter relationship without modifying Epicor's fiscal calendar. The Project naming convention uses the EOS quarter label so admins can cross-reference to the source EOS One data.

EOS Implementer relationships and consulting engagements are methodology artifacts with no Epicor equivalent. The Implementer's structured facilitation cadence (Level 10 facilitation, V/TO facilitation, quarterly check-ins) does not map to Epicor records. We document the Implementer engagement timeline as a CSV export during migration scoping and flag it for the customer to manage outside Epicor. If the customer continues using EOS Implementer services post-migration, the Implementer relationship continues independently of Epicor.

The V/TO core values, marketing positioning statements, and brand attributes stored in EOS One are migrated as Epicor Document records tagged as strategic_vision. These serve as reference documents in Epicor's Document Management system rather than operational data. The customer uses these documents during Epicor implementation workshops (particularly Epicor's Vision and Values alignment sessions in Epicor Activate) to carry forward the strategic context EOS provided into the new ERP implementation.