Migrate from Exepron to monday Work Management

Exepron Projects map to monday.com Boards. We extract project metadata (name, status, start/finish dates, priority flags) and the Project Risk Quotient score as a custom number column. The Critical Chain metadata (buffer positions, drum assignments, PRQ confidence intervals) cannot map natively to monday.com; we document these as a structured handoff note for the customer's PMO so the administrator can add explanatory columns or notes to the destination Board.

Exepron Activities (tasks) map to monday.com Items. Task Name becomes Item name; Duration, Start, and Finish migrate to date and number columns. Fixed-Duration flags migrate as a checkbox column. Activity Kanban statuses and Custom Activity Statuses map to monday.com Status columns with equivalent label names. Predecessor chains migrate as monday.com dependency column entries where the destination Board supports them; we validate dependency column availability during scoping.

Exepron Work Packages map to monday.com Groups within a Board. Activity Bundles nested under Work Packages are resolved into a flat Group structure or a Board-Subitem hierarchy depending on the customer's preferred granularity. Some destinations treat bundles as folders; we resolve the structural mapping during scoping and apply it consistently across all migrating Work Packages.

Exepron Resources (people, equipment, facilities) map to monday.com People columns for human resources or custom text/email columns for equipment and facility resources. We export Resource Name, Type, and Consumption units. Resource assignment is resolved by matching the resource name or email to a monday.com workspace member; unmatched assignments go to a reconciliation queue. Consumption data is stored as a number column with unit label.

Exepron Resource Types (grouping entities like Engineers, Equipment, Contractors) map to monday.com custom fields or tag groups. We export the type hierarchy so the Dynamic Drum logic is preserved as a tagged classification system. Because monday.com does not have typed resource capacity planning, the type hierarchy becomes a filterable tag taxonomy on the relevant Board rather than an enforced scheduling constraint.

Exepron Custom Fields (per-account extension properties) map to monday.com custom columns of the closest native type: text properties become text columns, number properties become number columns, date properties become date columns. We export field definitions and values. Complex custom field structures (multi-select, dependent fields) are mapped to the most equivalent monday.com column type and documented in the mapping spreadsheet.

Exepron Project Templates (reusable task networks and resource assignments) map to monday.com Board Templates. We export template block structure and task sequences. Template blocks are supported but the destination must support template-to-board instantiation; monday.com Standard and above support Board Templates natively. The Critical Chain buffer positioning within a template cannot be reproduced automatically and is documented as a setup note for the customer's PMO.

Exepron Custom Roles govern permission scoping within the platform. We export role definitions and permission sets. Because monday.com uses its own RBAC model (Workspace Owners, Members, and Guests), we map roles to the nearest equivalent monday.com permission level and document the mapping. Role-based filter rules that Exepron uses for project visibility require manual configuration in monday.com Teams after migration.

Exepron Alerts are threshold-based notifications tied to task slippage and resource overloads. Reason Codes annotate why slips occurred. Both are exported as metadata. In monday.com, we map threshold alerts to Automation triggers (e.g., When status changes to At Risk, notify the assignee) and Reason Codes to a custom Status column value set or a text column for annotation. The customer configures automations post-migration using the delivered inventory.

Exepron's Earned Value Module tracks Planned Value, Earned Value, and Actual Cost per Activity. We export the EV metrics snapshot as number columns (Planned_Value__c, Earned_Value__c, Actual_Cost__c) and create a formula column for Cost Performance Index (CPI = Earned Value / Actual Cost) if monday.com Pro or above is licensed. EV is calculated at migration time, so this is flagged as a point-in-time snapshot rather than a live calculation.

Exepron What-If scenarios are separate project clones with modified durations, resource loads, or start dates. We export the base project plus the scenario delta. monday.com does not have a native What-If scenario engine. We clone the base Board and document the scenario deltas as a structured note in a Scenario_Delta__c column so the customer's PMO can manually reconstruct scenario comparisons.

BIDSS is Exepron's runtime Business Intelligence Decision Support System. Its dashboards, charts, and heatmaps are generated from live project data at query time. There is no persistent BIDSS configuration artefact to export. We explicitly exclude BIDSS from our migration scope. Customers who rely on BIDSS insights must rebuild those visualisations in monday.com's native dashboards (available from Standard) or in a separate BI tool from the migrated project data.

PALS (Project Advanced Learning System) generates learner progress data independently of live projects. It is not a persistent data object with an export schema; it is a simulation environment that produces runtime records. We do not migrate PALS records. If PALS certifications or completion records need to be preserved, the customer should export those separately from Exepron's PALS interface before the migration window and store them outside both platforms.