Migrate your Exepron data

Projects are the top-level container in Exepron's hierarchy. We export project metadata, status, start/finish dates, priority flags, and the Project Risk Quotient score via GET /projects. The chain positioning is preserved as a computed field we capture at migration time.

Activities in Exepron correspond to Tasks. We map Task Name, Duration, Start, Finish, Predecessors, and Fixed-Duration flags. Activity Kanban statuses and Custom Activity Statuses are preserved as enumerated values; we translate them to the destination field equivalent during load.

Resources are typed entities (people, equipment, facilities). We export Resource Name, Type, Capacity, and Consumption units. Resource contention data is carried as a linked consumption table, not a standalone field.

Resource Types group Resources for drum scheduling. We export the type hierarchy so the Dynamic Drum logic can be reconstructed in the destination system. Types are required when migrating ATU (Automated Task Update Utility) configurations.

Custom Fields are per-account extension properties. We export field definitions and values but note that destination PM tools vary in their custom-field model; we map to the closest native or custom field in the target and flag any that cannot be represented.

Templates contain reusable task networks and resource assignments. We export the template block structure and task sequence. Template Blocks are supported but the destination must support template-to-project instantiation logic to use them meaningfully.

Custom Roles govern permission scoping within Exepron. We export role definitions and their permission sets. Because most destination PM tools have their own RBAC model, we map roles to the nearest equivalent or flag where custom roles cannot be represented.

Activity Bundles group related Activities under a parent Work Package. We export the bundle hierarchy. Some destination systems treat bundles as folders; we resolve the structural mapping during scoping.

Exepron alerts are threshold-based notifications tied to task slippage and resource overloads. Reason Codes annotate why slips occurred. Both are exported as metadata, but the destination must support a comparable alerting engine for them to remain actionable.

Earned Value Module tracks Planned Value, Earned Value, and Actual Cost per task. We export the EV metrics snapshot. Because EV is calculated at migration time, we flag this as a point-in-time export rather than a live-streaming figure.

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 do not migrate this object.

PALS (Project Advanced Learning System) is a simulation and knowledge-transfer environment. It generates learner progress data independently of live projects. We do not migrate PALS records as they are not project data.

What-If scenarios are separate project clones with modified constraints. We export the base project plus the scenario delta (changed durations, resource loads, or start dates). The destination must support scenario branching or we consolidate to the baseline.