Migrate from Edison 365 to monday Work Management

Edison 365 Project records map to monday.com Boards. Project name becomes the Board name, owner maps to the monday.com member who receives the Board, start and end dates map to Date columns, budget maps to a Numbers column with currency formatting, and stage maps to a Status column with stage names matched from the Edison 365 Pipeline configuration. We configure Board type (Main or Shareable) and set the default group structure during schema design.

Edison 365 Ideas map to monday.com Items on an Ideas Board. The Idea title becomes the Item name, description becomes a Text column, category becomes a Dropdown or Tags column, submitter maps to a People column, and status maps to a Status column with stage names preserved from the Edison 365 workflow configuration. If the customer uses Edison 365's idea-to-project linking, we add a Link to Item column referencing the corresponding Project Board.

Edison 365 Business Case records become monday.com Items on a dedicated Business Cases Board. Financial rows (cost estimates, benefit projections, ROI metrics) export from Edison 365 custom fields and map to monday.com Numbers or Formula columns. Approval status becomes a Status column. Because Edison 365 stores Business Cases as distinct entities while monday.com has no native business-case object, we create a separate Board for Business Cases linked to the parent Project Board via a Link to Item column. The Edison 365 Business Case-to-Project association is preserved as a parent-child link in monday.com.

Edison 365 Resource allocations (person, project, percentage, date range) split across two monday.com structures. The resource roster (person name, role, department, email) migrates to a Resources Board as Items, with role and department as Dropdown columns. Active allocations appear as People column entries on the relevant Project Board Items, with allocation percentage and dates mapped to Numbers and Date columns. Portfolio-level allocation rollups are not available in monday.com natively and require a manual recalculation post-import or a third-party resource-management integration.

Edison 365 Portfolios aggregate Projects and track KPIs, budget rollup, and health indicators across the project portfolio. monday.com does not have a native Portfolio object. We map each Edison 365 Portfolio to a monday.com Workspace, create a portfolio dashboard Board using monday.com widgets (status chart, workload view, timeline), and link child Project Boards via a Link to Item column or integration automation that we document for the customer's admin to configure post-migration. Portfolio-level rollup totals (total cost, total benefit) are recalculated from the imported Project Board data and entered as static or formula values on the portfolio dashboard.

Edison 365 Pipeline stages (configurable per workflow) export from the workflow configuration with stage names, order, and probability percentages. We map each stage to a monday.com Status column option on the target Board in the same sequence. Probability percentages migrate to a separate Numbers column or are embedded in the Status column configuration if the customer uses a probability-display integration. Stage transition rules are not preserved as automation rules in monday.com because Edison 365's workflow gates have no direct equivalent.

Edison 365 Benefits are entity-specific (attached to Projects or Business Cases) and store benefit type, target value, current value, and unit. Since monday.com has no native benefit-tracking object, we extract benefit rows from Edison 365 Business Cases and Projects and map them to monday.com Numbers columns on the corresponding Project Board. Benefit type names become column labels, and values transfer as numeric entries. Any benefit rollup across the portfolio requires manual recalculation or a monday.com formula-column configuration that we document in the handoff.

Edison 365 stores custom field definitions per entity type without a consolidated schema export, so we enumerate custom fields by querying each entity separately during discovery. Text, number, date, and dropdown custom fields map to monday.com column types (Text, Numbers, Date, Dropdown). Multi-select fields map to Tags columns. The mapping is recorded in the approved field map before import begins, and any custom fields without a direct monday.com column equivalent are flagged for manual recreation or approximation.

Edison 365 documents are stored in SharePoint and referenced by URL rather than embedded content. We export the full document inventory (file name, SharePoint URL, parent record reference, created date) and run a parallel SharePoint-to-monday.com file migration so that file attachments land on the correct Items after cutover. Edison 365 SharePoint URLs pointing to the source Microsoft 365 tenant become orphaned after migration and are flagged and replaced with monday.com file attachments or monday.com Workdocs links.

Edison 365 user records (display name, email, role, department) map to monday.com member accounts by email match. We export the full user roster, provision matching monday.com accounts (active or inactive based on the original Edison 365 user status), and map owner references on Projects and Ideas to monday.com People column values on the relevant Items. Any Edison 365 user without a matching monday.com account is held in a reconciliation queue for the customer's admin to provision before the production migration begins.

Edison 365 Company records (used in Portfolio and Business Case contexts for stakeholder tracking) map to Items on a Contacts or Stakeholders Board in monday.com. Company name becomes the Item name, website becomes a Text column, and industry maps to a Dropdown column. If the customer has a significant stakeholder list, we recommend a separate Contacts Board rather than adding them to the Project Board.

Edison 365 Pipelines and workflow configurations (stage names, order, transition rules) export from the workflow settings and are used to configure monday.com Status columns and board structure. Transition rules, approval gates, and stage-gate automation logic have no direct equivalent in monday.com and are documented in the handoff as recommended automation rebuilds. The Edison 365 workflow configuration JSON is included in the written inventory delivered to the customer.