Migrate from Edison 365 to Trello

Edison 365 Ideas map directly to Trello cards. The Idea title becomes the card name, description migrates as the card description, Category maps to a Trello Label or List, Submitter maps to a Card Member, and status maps to card position within the appropriate List (e.g., Backlog, Screening, Approved). Archived Ideas require Trello Premium or Standard to export; we verify archived Ideas are accessible during discovery and flag any that require manual board re-activation before export.

Edison 365 Projects with sub-tasks and milestones map to a Trello board where the project header becomes the board name and Work Packages or milestones become Lists. Projects without sub-structures can map to a single card within an existing board. Edison 365 project fields (owner, start/end dates, budget, stage) migrate as custom fields on the card or as card metadata; budget fields require Trello Standard ($5/user/mo) or Premium because the free tier limits custom fields to one per card.

Edison 365 Business Cases contain costs, benefits, and approval status tracked via custom fields. Trello has no business case entity. We map each Business Case to a dedicated card with the key financial fields (estimated cost, expected benefit, NPV, ROI) as card custom fields or checklist items, and approval status as a label or list position. Benefit tracking is entity-specific in Edison 365 — if the same benefit metric appears across multiple Business Cases as duplicate instances, those instances all migrate as separate cards with no native rollup in Trello.

Edison 365 Resource records link people to Projects or Portfolios with allocation percentages and date ranges. Trello has no resource management object. We split resource records into Trello Card Members (the person assigned) and card-level custom fields for allocation percentage and date range where Trello custom field support allows. Trello's free tier limits cards to one custom field, so resource allocation metadata requires either Trello Standard or a documented manual lookup spreadsheet for free-tier migrations.

Edison 365 Portfolios aggregate multiple Projects and track portfolio-level KPIs and budget rollups. Trello has no portfolio object. We create a Trello Workspace-level structure with one board per Portfolio and child Project boards linked via card cross-references or Butler rules. Portfolio rollup calculations (total cost, total benefit, aggregate KPI scores) cannot be computed in Trello natively; we document the original Edison 365 rollup totals as a card in each Portfolio board so the customer's admin can reference them for manual or spreadsheet-based recalculation.

Edison 365 Pipelines have configurable stages per workflow (e.g., Idea > Screening > Business Case > Approval > Delivery). Stage names, order, and transition rules export from the workflow configuration. We map each Pipeline to a Trello board where stages become Lists in the configured order. Stage transition rules have no Butler equivalent — we document every transition condition in a written inventory so the customer's admin can implement manual gates or Butler trigger-action rules that approximate the original workflow logic.

Edison 365 stores custom field definitions separately per entity — Ideas have their own custom field set, Projects have another, Business Cases have a third. There is no consolidated schema export. We enumerate custom field definitions by querying each entity type separately during discovery, which adds a multi-pass enumeration step. We then attempt to create matching Trello custom fields on the destination cards, subject to Trello's custom field limits per card (free tier: 1 field, Standard and above: unlimited). Fields that cannot be represented in Trello (e.g., multi-select, formula, or date-range fields) are documented in a custom field gap analysis.

Edison 365 attaches documents by storing SharePoint URLs rather than file content. These links point to the source Microsoft 365 tenant's SharePoint and become orphaned after migration unless we perform a parallel file transfer. We export the full document inventory (URLs, file names, linked entity, linked record ID) and either upload files to Trello card attachments directly or to the destination SharePoint/OneDrive and re-link them. The customer must provide SharePoint access credentials for the parallel file migration track. This is a separate workstream from the record migration and is scoped and priced independently.

Edison 365 user records include display name, email, role, and department. We export the full user roster and map to Trello Workspace members by email match. Inactive Edison 365 users are included in the export but flagged for deactivation review in Trello. If the Trello Workspace is new (separate from an existing Atlassian organization), we provision Workspace members using the Edison 365 email list and assign them to relevant cards based on the assignee field in Edison 365.

Edison 365 Benefits are tracked against individual Business Cases or Projects as custom fields or separate benefit rows. Trello has no benefit tracking concept. We map benefit metrics to Trello custom fields on the Business Case or Project card, or to checklist items with monetary or KPI values in the checklist description. Benefit rollup across the portfolio requires a documented manual calculation because Trello has no aggregation capability. We preserve the original benefit target, current value, and benefit type from Edison 365 as separate fields for post-migration reference.

Edison 365 ships Power BI as its native reporting layer. Custom Power BI reports referencing Edison 365 data connections do not migrate. We export a list of all Power BI .pbix files and their report definitions, identify which Edison 365 entities each report references, and deliver a written inventory with the Trello board/card structure that the reports should be rebuilt against. The customer's admin or a Power BI partner rebuilds the reports post-migration against Trello data (accessed via Trello API or a third-party reporting Power-Up).

Edison 365 Pipeline stage-gate rules and transition logic are not automations in the Trello Butler sense. We extract every Edison 365 pipeline workflow definition — stages, transition conditions, approval gates, and assignment rules — and deliver them as a written workflow inventory. The customer's admin rebuilds these as Butler trigger-action rules or documents them as manual process steps. Butler does not support conditional stage-gate logic comparable to Edison 365's pipeline configuration; the rebuild scope is documented honestly so expectations are set.