Migrate from Exepron to Microsoft Project

Exepron Projects map to Microsoft Project plans (MPP files) or Project Online Projects. Project metadata (name, start date, finish date, priority, status) migrates directly. The Project Risk Quotient (PRQ) score migrates as a custom numeric field. We use the Exepron GET /projects endpoint and reconstruct the project in the destination by creating a new MPP or Project Online project entry before any Task or Resource data is imported.

Exepron Activities map to Microsoft Project Tasks. Activity Bundles map to Summary Tasks with their child Activities as subordinate tasks at the correct WBS depth. Fixed-duration flags map to Task.Type = Fixed Duration. Kanban statuses and Custom Activity Statuses are preserved as a custom Text field (ActivityStatus__c in Project Online) since Microsoft Project has no native status enumeration equivalent to Exepron's Activity states. Predecessor chains in Exepron (Critical Chain buffer insertion points) are reconstructed as standard finish-to-start predecessors in Microsoft Project.

Exepron Work Packages are the unit of scheduling in the Critical Chain. We map them to Microsoft Project Tasks. The compiled Work Package state (the most recent Exepron-generated schedule) is captured as the migration snapshot. Work Package versions are not individually migrated; only the latest compiled state moves. If a Work Package has multiple chain assignments, we create a single task entry and note the chain assignment in a custom field.

Exepron Resources (people, equipment, facilities) map to Microsoft Project Resources. Resource Name, Type (Material, Work), Max Units, and Cost per Use migrate directly. Resource consumption data from the linked consumption table migrates as Assignment (Task Assignment with Units and Work values). We resolve the Resource Type hierarchy from Exepron to ensure named resources are correctly typed in the Microsoft Project resource pool.

Exepron Resource Types group Resources for Dynamic Drum scheduling. We map the type hierarchy to Microsoft Project Resource Groups (Type field) so that resource assignments are grouped by role. ATU (Automated Timetable Update) Resource Types that drive Exepron's constraint logic are flagged as a custom field (ATU_Flag__c) for the project manager to evaluate for manual scheduling decisions in Microsoft Project.

Exepron Custom Fields (per-account extension properties) map to Microsoft Project Enterprise Custom Fields in Project Online PWA, or local custom fields in Project Desktop. We export field definitions and values and map to the closest typed Microsoft Project field (Text, Number, Flag, Date, Cost). Some Exepron custom fields may not have a natural Microsoft Project equivalent; those are flagged for the customer's PMO admin to configure post-migration.

Exepron Project Templates (reusable task networks and resource assignments) are exported as task and resource block structures. Template-to-project instantiation does not occur automatically in Microsoft Project; we deliver a structural export of the template hierarchy so the customer's PMO can create a corresponding template in Microsoft Project or use the exported block structure as a reference for manual template creation.

Exepron Earned Value records (Planned Value, Earned Value, Actual Cost) are exported as point-in-time snapshots and mapped to custom numeric fields in Microsoft Project (EV_PV__c, EV_EV__c, EV_AC__c). Microsoft Project calculates EV metrics automatically from baseline and actual data; the Exepron snapshot serves as a baseline reference rather than live EV tracking going forward.

Exepron Alerts (threshold-based task slippage and resource overload notifications) and Reason Codes (slip annotations) migrate as metadata. In Project Online these become custom Flag or Text fields on tasks; in Project Desktop they are preserved as Notes attached to the relevant task. The destination system has no native alert engine equivalent to Exepron's PRQ-driven alerting, so the customer should plan to use Power Automate or manual review for ongoing threshold monitoring.

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 (changed values). In Microsoft Project, we create a separate Summary Task group for each scenario so the PMO can manually compare baseline versus scenario outcomes. The destination does not natively support What-If branching; this is a manual reconstruction for planning purposes.

BIDSS is Exepron's runtime Business Intelligence Decision Support System. Dashboards, heatmaps, and PRQ trend charts are generated from live project data at query time and are not stored as discrete persistent objects. We do not migrate BIDSS configurations. Customers who rely on BIDSS insights must rebuild those visualisations in a BI tool (Microsoft Power BI is the natural destination given the Microsoft ecosystem) using the migrated project and resource data as source tables.

PALS (Project Advanced Learning System) generates learner progress data independently of live projects. There are no persistent PALS export artefacts. We explicitly exclude PALS from our migration scope. Customers using PALS for team onboarding and skills tracking should evaluate Microsoft Teams, SharePoint, or a dedicated LMS as the replacement learning management layer.