Migrate from zeno.pm to Microsoft Project

zeno.pm Projects map to Microsoft Project files or Project for the web Project records. We extract project name, status, description, start date, end date, owner, and any project-level custom fields via the vendor-coordinated export. zeno.pm stores scheduling data as project-level properties rather than independent task objects, so we transform those date properties into a flat project-level milestone record in Microsoft Project. Dependencies between projects in zeno.pm become cross-project dependencies or are documented as predecessor relationships to recreate in the destination.

zeno.pm Programs aggregate multiple projects with their own status, financials, and reporting roll-up. In Microsoft Project Plan 3 and Plan 5, programs map to Enterprise Projects that contain sub-projects, or to Roadmap rows that aggregate status across multiple independent project plans. We preserve the program-to-project parent-child relationship as an Enterprise Project hierarchy or as a Roadmap association depending on the destination Plan tier. Program-level financials roll up to the parent Program record and map to summary cost fields in the destination.

zeno.pm Portfolios are top-level containers aligned to business units, regions, or investment themes. Microsoft Project does not have a native Portfolio object; portfolio-level roll-up requires either Project Online with its Portfolio Views or a Project Plan 3/5 Roadmap. We map the portfolio hierarchy as a structured document delivered alongside the migration so the customer's admin can recreate the portfolio groupings in the appropriate Microsoft tool. Portfolio-level KPIs and financial summaries migrate as structured data to be surfaced in Power BI if the customer has that license.

zeno.pm Risks are structured records attached to Projects with title, likelihood, impact, status, owner, and mitigation notes. We map these to Microsoft Project tasks with custom fields capturing likelihood, impact, and risk status. For organisations using Project Online with SharePoint, risks can be stored in a linked SharePoint Issues List. The risk register is treated as a child collection of the parent Project record, and we preserve the ordering and grouping from zeno.pm during migration. Risks without an owner in zeno.pm are flagged for manual assignment in Microsoft Project.

zeno.pm Issues follow a similar schema to Risks and are stored as a separate log within each Project. We map issue title, priority, status, owner, and description to Microsoft Project tasks with custom priority and status fields, or to a SharePoint Issues List linked from Project Online. Issues and Risks from zeno.pm are migrated in the same pass because their schema structures are similar. Any linked attachments on issues are inventoried for manual re-upload.

zeno.pm stores project financials including budget, actuals, and forecasts as project-level properties. We map these as structured financial line items, preserving values and currency. Microsoft Project natively supports Fixed Cost, Fixed Cost Accrual, and Cost fields on tasks. For complex financial roll-ups, we deliver a structured CSV mapping that the customer imports separately or connects to a Power BI financial reporting model. zeno.pm financial summaries that reference external accounting system integrations do not migrate as live connections; they require reconfiguration in the destination.

zeno.pm tracks team member assignments to projects and programs with resource names, roles, allocation percentages, and availability. We map these to the Microsoft Project Resource Sheet with Max Units carrying the allocation percentage. For Project Online, resources migrate to the Enterprise Resource Pool and project assignments are linked. Resource capacity and utilisation data in zeno.pm is preserved as structured availability records in the destination. Any generic (non-user) resources in zeno.pm map to Material Resources or generic resources in Microsoft Project.

zeno.pm stores milestone dates and dependencies as project-level metadata rather than as independent schedule objects. We extract every milestone date from the project record and create discrete Milestone tasks in Microsoft Project with the correct Finish Date and zero duration. Dependencies between milestones in zeno.pm map to predecessor-successor relationships (FS, SS, FF, SF) in Microsoft Project. This transformation is the most structurally significant step in the migration because zeno.pm does not expose these as independent objects.

zeno.pm custom fields are defined via its form-builder and are not visible in any public API documentation. During discovery, we request the full form schema from zeno.pm support or extract it from the admin console. We map each custom field individually to Microsoft Project's Project Summary Tasks custom fields, flagging any picklist dependencies, conditional visibility rules, or required-field constraints. Note: Microsoft Project .mpp import does not carry project-level custom fields (a documented Microsoft limitation), so these require manual field creation and value mapping post-import if the customer is using Project Desktop.

zeno.pm embeds AI features that generate or enrich project data such as summaries and risk flags. We identify records with AI-generated content during profiling, preserve the output as text in a custom field (e.g., AI_Summary__c) on the destination Project or Task record, and flag the record for review by the project manager to validate the AI-generated content in its new context. AI risk flags migrate as risk entries with a note indicating the AI origin for transparency.