Migrate from Edison 365 to Microsoft Project

Edison 365 Projects map to Microsoft Project project files. Project name, description, owner, start date, finish date, and budget migrate as standard project fields. Milestones defined in Edison 365 become summary tasks or milestone tasks in Microsoft Project. Edison 365 custom fields on Projects map to Microsoft Project enterprise custom fields (Project-level custom fields require Project Online or a Project Web App connection; standalone MPP files use local custom fields). We preserve the Edison 365 project stage as a custom text field on the imported project for PMO reference.

Edison 365 Ideas have no direct Microsoft Project equivalent. Microsoft Project is a scheduling tool, not an idea-intake platform. We extract all Ideas with title, description, category, submitter, status, and submission date. These are delivered as a structured CSV inventory alongside the migrated project files. The customer's PMO manually creates tasks from Ideas or uses a separate Idea tracking system (Planner, a SharePoint list, or a Power App). We flag Ideas with active status or unresolved approvals that may require follow-up before being converted to project tasks.

Edison 365 Business Case records contain costs, benefits, and approval status. The cost and budget values migrate as custom cost fields on the linked Microsoft Project file. The approval status and approver fields migrate as custom text fields. However, the Business Case object itself does not exist in Microsoft Project, so the full record structure (including benefit metrics, NPV calculations, and custom financial rows) cannot migrate as a first-class object. We extract all Business Case fields into a CSV deliverable for the customer's financial team to reference or manually re-enter.

Edison 365 Benefits are entity-specific records (attached to individual Business Cases or Projects) with KPI targets and actual values. Microsoft Project has no benefits or KPI tracking object. Benefit values can be migrated as custom number or currency fields on the Project file, but the benefit rollup calculations that Edison 365 performs across the portfolio do not transfer. We extract all Benefits records by Project and Business Case and deliver them as a structured CSV so that the customer's admin can recreate benefit tracking in a separate spreadsheet, Power BI report, or Finance system.

Edison 365 Resources map to Microsoft Project Resources. We extract resource name, email, department, role, and cost rates. Edison 365 supports Azure AD-linked resources, named resources, and generic resources; these map to the equivalent Microsoft Project resource type. Allocation percentages and date ranges from Edison 365 assignments migrate as assignment data in Microsoft Project, but the allocation percentage model in Edison 365 differs from Microsoft Project's work-units model; we convert allocation percentages to hours or work values based on the project calendar and resource capacity if the customer requests a direct assignment migration.

Edison 365 Portfolio records aggregate KPIs, budgets, and resource utilization across multiple Projects. Microsoft Project (standalone) has no cross-project portfolio rollup. We extract all Portfolio metadata and project membership, then deliver it as a structured CSV inventory. If the customer uses Project for the Web (part of Microsoft Project Plan 3 or Project Plan 5), we can map the Portfolio data to the Power Apps / Dataverse portfolio tables as a separate engagement. The customer should decide during scoping whether Portfolio records are migrated as reference data or archived as historical documents.

Edison 365 Pipelines have configurable stage names, ordering, and transition rules per workflow (e.g. Idea > Screening > Business Case > Approval > Delivery). Microsoft Project has no pipeline or workflow object. Stage names and current stage assignments for Projects migrate as a custom text field (e.g. ProjectStage) on each imported project. Stage transition rules, automated notifications, and approval gates do not migrate and require manual reconstruction in Microsoft Project or a Power Automate workflow built by the customer's admin.

Edison 365 stores documents in SharePoint document libraries and references them by URL. These URLs point to the source Microsoft 365 tenant and become orphaned after migration. We export the full document inventory (file name, URL, associated Edison 365 entity, upload date, and uploader) and offer a parallel SharePoint-to-SharePoint or SharePoint-to-OneDrive file transfer to relink documents to the destination tenant. Without this parallel track, document-linked records in the migrated project files will have broken attachment references.

Edison 365 stores custom fields per entity without a unified schema export; we enumerate custom fields by querying each entity type separately. Microsoft Project supports custom fields at the Project level (for Project Online / Project Web App) or at the Task and Resource levels. We map Edison 365 custom fields to the equivalent Microsoft Project custom field type (text, number, date, cost, flag) and flag any that cannot be represented in Microsoft Project's custom field schema. Custom fields requiring lookup tables or multi-select options may need manual configuration in the destination before data load.

Edison 365 user records include display name, email, role, and department. We extract the full user roster and map to Microsoft Project Resources by email. Inactive Edison 365 users are included but flagged for the customer's admin to deactivate or reassign in Microsoft Project. Resources assigned to projects without a matching user in the destination Microsoft 365 tenant are held in a reconciliation queue until the admin provisions the missing resource.