Migrate from Edison 365 to Asana

Edison 365 Ideas map to Asana Projects in a dedicated 'Idea Intake' Team. The Idea title becomes the Project name, description migrates as the Project description, category maps to a custom field (Idea Category), submitter maps to an Asana member, and Edison 365 Pipeline stage maps to an Asana custom field (Idea Stage). We preserve the original submission date as a custom date field. Edison 365's workflow-based Idea pipeline (e.g. Submission > Screening > Evaluation > Approval) does not migrate as a workflow; it is stored as the Idea Stage custom field for the admin to model in Asana as a dropdown.

Edison 365 Project records map directly to Asana Projects. Project name, description, owner, start date, end date, and budget migrate as standard and custom fields. Edison 365's stage value (e.g. Planning, In Progress, On Hold, Completed) maps to an Asana custom field (Project Stage). We resolve the Edison 365 owner by email match to an Asana member. Project-level custom fields migrate to Asana custom fields of matching type (text, number, date, dropdown).

Work breakdown items within Edison 365 Projects map to Asana Tasks. Task name, description, assignee, start date, due date, and status migrate directly. Edison 365 subtasks map to Asana subtasks. Task-level custom fields migrate to Asana task-level custom fields. We resolve assignees by email match and flag any Edison 365 task with multiple assignees (Edison 365 supports multi-assignee) for the customer to decide on Asana's single-assignee approach per task.

Edison 365 Business Case records merge into the Asana Project that represents the initiative they support. We create a Business Case section in the Asana Project's custom fields capturing cost estimates, benefit values, approval status, and financial notes as custom fields. Edison 365 custom financial fields on Business Cases map to Asana custom number fields. Approval history migrates as a custom text field. If a single Business Case supports multiple Edison 365 Projects, we create one Asana Project per source Business Case and note the cross-link in a custom text field.

Edison 365 Benefit records are entity-specific (attached to individual Business Cases or Projects) rather than globally reusable. We extract each Benefit record and create corresponding custom number or currency fields on the parent Asana Project (e.g. 'Benefit: Cost Savings', 'Benefit: Revenue Impact', 'Benefit: ROI %'). Benefit types stored as Edison 365 custom fields become Asana dropdown custom fields. Since Edison 365 stores duplicate benefit instances when the same metric is used across multiple Business Cases, we preserve each instance as a separate field on its respective Asana Project rather than attempting a global rollup that does not exist in the source.

Edison 365 Resource records represent people assigned to Projects or Portfolios with allocation percentages and date ranges. We map each Resource assignment to an Asana Task (or Project membership if the customer uses Asana Business with Portfolio assignments) with the assignee resolved by email match, start date and end date preserved as custom fields, and allocation percentage stored as a custom number field. Edison 365's portfolio-level resource allocations (allocations scoped to the Portfolio rather than a single Project) require the customer to designate a specific Asana Project or Portfolio for each resource rollup since Asana's workload feature does not support cross-project capacity aggregation.

Edison 365 Portfolios aggregate multiple Projects and display portfolio health, KPIs, and budget rollup. We migrate Portfolios as Asana Portfolios (Business tier required, $24.99/user/mo). Each Edison 365 Portfolio maps to an Asana Portfolio with the same name. The child Projects are added to the Portfolio membership. Edison 365 portfolio-level KPI values (total cost, total benefit, portfolio status) are stored as custom fields on a designated 'Portfolio Summary' Project within the Portfolio so that rollup calculations are visible. Live portfolio rollup calculations do not carry over because Asana calculates Portfolio health from the underlying Project data, not from pre-computed Edison 365 totals.

Edison 365 stores custom field definitions per entity type without a consolidated schema export. We enumerate custom fields for each entity type (Ideas, Projects, Business Cases) separately during discovery. The resulting schema is pre-built in Asana before migration using Asana's field library for global fields or project-local fields depending on the customer's reuse requirements. Dropdown options in Edison 365 custom fields become Asana dropdown option sets. Number and currency fields migrate with type preserved.

Edison 365 Pipelines have configurable stage names and transition rules per workflow. We extract the stage names and order from the Edison 365 workflow configuration and create corresponding Asana custom dropdown fields (one per Edison 365 Pipeline). The customer chooses whether to apply the stages as Project-level or Task-level custom fields. Stage transition rules do not migrate as workflow logic; we document them in the handoff inventory for the admin to model in Asana's task status options or a dedicated stage field.

Edison 365 User records (display name, email, role, department) map to Asana workspace members. We match by email. Any Edison 365 User referenced as a Project owner, Resource assignee, or Idea submitter who does not yet have an Asana account is placed in a reconciliation queue for the customer's admin to provision before that phase of migration begins. Inactive Edison 365 users are included as inactive Asana members and flagged for deactivation review.

Edison 365 stores documents as SharePoint URLs, not embedded files. We export the full document inventory (file name, URL, associated record) and perform a parallel file-level transfer to a destination store (Asana Direct Attachments, Google Drive, Dropbox, Box, or the customer's destination SharePoint). We recreate links in Asana as file attachments or as URL attachments pointing to the new file location. This is a separate migration track from the record migration and is scoped and priced independently. No Edison 365 SharePoint URL will remain valid after the source tenant is decommissioned.

Edison 365 tracks the timestamp and user who moved a Pipeline stage. We store this as a custom text field on the Asana Project (e.g. 'Stage History: Screening moved to Approved by J.Smith on 2025-09-14'). The full stage history is preserved for audit purposes even though Asana does not have a native stage history audit trail. We capture the most recent stage entry as the current status and document older entries in the handoff notes.