Migrate from Exepron to Trello

Each Exepron Project maps to a Trello Board. Project metadata (name, description, start date, target finish) migrates as board name and description. Trello Boards do not have native project-level budgets or Earned Value, so those metrics are noted as metadata on the board description for reference. Exepron's Project Risk Quotient (PRQ) score has no Trello equivalent and is recorded as a custom field on the board's first list card for audit purposes only.

Exepron Activities map to Trello Cards. Task Name becomes card title; Start and Finish dates migrate as card Start Date and Due Date if Trello Premium is in use, or as a custom date field on Standard. Predecessor chains from Exepron have no native Trello representation—predecessor data is exported as a custom field (predecessors__c) listing predecessor card names for admin reference. The card is placed in the Trello list that corresponds to the Exepron Activity Status value (e.g., Not Started, In Progress, Complete).

Exepron Activity Bundles group related Activities under a parent Work Package. We map each bundle to a Trello List, and the contained Activities within the bundle become Cards in that List. If the destination workspace uses Power-Up-enabled Card sections, bundles may instead map to sections within a single list. The customer selects the strategy during scoping based on their Trello plan and preferred board layout.

Exepron Resources (people, equipment, facilities) map to Trello Board Members. Resource Name becomes the member's display name; Resource Type (Person, Equipment, Facility) is preserved as a custom field on the member or on cards they are assigned to. Resource Capacity and Consumption data have no Trello equivalent and are exported as a separate CSV reference document for the customer's admin to use in capacity planning outside Trello.

Exepron Resource Types group Resources for drum scheduling logic. Trello has no drum or capacity scheduling model, so Resource Types are exported as a labelled reference set. Depending on customer preference, they map to Trello Labels (if the team uses labels for role-based grouping) or to a custom field on Cards for filtering. The Dynamic Drum schedule itself is not reproducible in Trello and is inventoried as a non-transferable artefact.

Exepron Custom Fields (available on Pro/Enterprise) migrate to Trello card-level Custom Fields if the workspace is on Standard or Premium. Text, number, date, and dropdown field types map directly. Multi-select or checkbox fields from Exepron map to Trello dropdown or checkbox custom fields. Note that Trello's native Custom Fields Power-Up supports a subset of field types; complex validation rules from Exepron (e.g., conditional requireds) cannot be reproduced and are documented as admin-rebuild items.

Exepron Custom Roles govern permission scoping within the platform. Trello uses Workspace-level Admin, Normal, andObserver roles plus Board-level permission settings. We export the role hierarchy and permission matrix as a reference document. The mapping is necessarily lossy because Trello's RBAC model is flatter than Exepron's custom permission sets; the customer's admin configures Trello workspace and board permissions post-migration based on the exported matrix.

Exepron Project Templates contain reusable task networks and resource assignments. We export the template structure as a reference document showing the task hierarchy and suggested assignments. Trello supports Board Templates on Premium plans. We provide a mapping from each Exepron template to a Trello board template structure that the customer's admin creates in Trello using the Duplicate Board feature.

Exepron Alerts are threshold-based notifications tied to task slippage and resource overloads; Reason Codes annotate why slips occurred. Both are exported as metadata on the relevant Activity record. We map open Alerts to Trello Card Labels (e.g., 'Overdue Alert', 'Resource Overload') and attach Reason Code text as a card comment for audit trail. Closed Alerts are noted in the migration audit report rather than created as active labels.

Exepron's Earned Value Module tracks Planned Value, Earned Value, and Actual Cost per Activity. Because EV is calculated at migration time, we export the current snapshot as a CSV with columns matching the EV data structure. In Trello, we create a custom number field (EV_Current__c) on cards and populate it from the snapshot. Trello has no native EV calculation engine; customers who need ongoing EV tracking rebuild this in an external BI tool or a reporting Power-Up.

Exepron What-If scenarios are cloned projects with modified constraints. We export each scenario as a separate board in Trello, named with the scenario name and tagged with a 'What-If' label. The base project delta (changed durations, resource loads, or start dates relative to the base project) is documented in a comparison table that the customer's admin uses to interpret the scenario board. Trello has no scenario comparison or simulation capability.

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 migration scope. Customers who rely on BIDSS insights receive an exported CSV of the underlying project metrics that powered the dashboards, which their admin can use to rebuild visualisations in a BI tool such as Power BI, Tableau, or a Trello reporting Power-Up.

PALS (Project Advanced Learning System) generates learner progress and simulation data independently of live projects. There is no persistent PALS artefact in the Exepron database—it is runtime-generated per user session. We do not migrate PALS records. Customers who need to preserve training history should export records from PALS directly before the migration window if that data has business value, as it cannot be reconstructed post-migration.