Migrate your zeno.pm data
SaaS-based Project Portfolio Management platform with pre-configured reporting and program aggregation. Designed for organisations that need to consolidate project data across multiple initiatives without a heavyweight ERP.
In its favor
Why people choose zeno.pm
The signal that keeps zeno.pm on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Pre-configured best-practice reports mean organisations do not build dashboards from scratch — teams get executive KPIs, project-level drill-downs, and aggregated portfolio views immediately after setup.
The platform supports both agile and waterfall delivery models simultaneously, allowing a single portfolio to contain projects using different methodologies without a tier upgrade.
Pay-as-you-go pricing with a free tier lowers the commitment threshold for small teams or government departments evaluating portfolio management for the first time.
Configurable forms and workflows allow organisations to align the tool to their existing project governance framework rather than rewriting their process to fit the software.
Out-of-the-box configuration requires minimal professional services engagement, making it accessible for teams without a dedicated implementation budget.
The platform lacks an automated migration path from existing tools — one reviewer explicitly noted that moving from .mpp files into zeno.pm has no built-in automated process and requires manual re-entry.
The dashboard and user interface feel dated compared to modern SaaS alternatives, with reviewers citing the look and feel as a reason they considered switching platforms.
Organisations with complex custom reporting requirements find the built-in report suite insufficient and the export options limited for feeding data into external BI tools.
Reasons to switch
Why people leave zeno.pm
The recurring reasons buyers give for replacing zeno.pm. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where zeno.pm fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
zeno.pm pricing overview
Zeno.PM uses a pay-as-you-go model with a free tier and a per-user-per-day pricing structure for the Starter plan. Professional and Enterprise tiers require direct sales engagement for custom pricing, and the platform supports data sovereignty hosting for regulated industries.
Free
Tier 1 of 4
Free
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on zeno.pm's schedule — see our quote-based pricing →
What gets migrated
zeno.pm object support
Object-by-object support for zeno.pm migrations. Per-pair details surface during scoping.
Projects
Mapping requiredProjects are the primary record in zeno.pm. We map project name, status, dates, owner, and description fields directly. Custom project fields and form-derived properties require mapping to destination equivalents because zeno.pm uses a configurable form-builder for project metadata.
Programs
Mapping requiredPrograms aggregate multiple projects in zeno.pm. We preserve the program-to-project parent-child relationship and map program-level financials and status by rolling up child project data. The program object has fewer standard fields than Projects, so we handle it as a secondary mapping pass.
Portfolios
Mapping requiredPortfolios are the top-level container in zeno.pm, aligned to investments, regions, business units, or product lines. We map portfolio hierarchies and aggregate any portfolio-level KPIs from child Programs and Projects.
Custom Fields
Mapping requiredZeno.PM allows organisations to define custom fields on Projects, Programs, and Portfolios via its form-builder. We extract the full custom field schema during discovery and map each field to the destination system's equivalent, flagging any fields with picklist or conditional logic dependencies.
Risks
Mapping requiredRisks are stored as structured records attached to a Project. We map risk title, likelihood, impact, status, owner, and mitigation notes. The risk register is treated as a child collection of the parent project during migration.
Issues
Mapping requiredIssues are stored alongside Risks as a separate log within each Project. We map issue title, priority, status, owner, and description. Issues and Risks share a similar schema structure in zeno.pm, so we handle them in a shared transformation pass.
Financials
Mapping requiredZeno.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 where present. Financials are tied to the project record, not stored independently.
Resources
Mapping requiredResource management in zeno.pm tracks team member assignments to projects and programs. We map resource names, roles, allocation percentages, and availability. Resource capacity and utilisation data is derived from assignment records rather than a separate capacity object.
Schedules and Milestones
Mapping requiredZeno.PM stores project schedules as date properties on the project record. Milestone dates and dependencies are handled as project-level metadata rather than independent schedule objects. We map milestone name, due date, and status, and flag any inter-project dependencies for manual review.
Attachments
Not in this platformZeno.PM does not expose a public REST API for attachment export or import. We cannot automatically migrate binary attachments (documents, images, linked files) and instead document the full attachment list as a reference inventory for manual re-upload after migration.
Reports
Not in this platformZeno.PM's reporting suite consists of pre-configured report definitions and dashboards rendered server-side. Report configurations are not exposed via a documented API. We migrate the underlying data that feeds reports (Projects, Programs, financials, risks, issues) so that equivalent reports can be rebuilt in the destination system.
AI-Generated Data
Mapping requiredZeno.PM embeds AI features that generate or enrich project data such as summaries or risk flags. We identify records with AI-generated content during profiling, preserve the output as-is, and flag it for customer review so they can validate or regenerate it in the destination system.
| Object | Support | Notes |
|---|---|---|
| Projects | Mapping required | Projects are the primary record in zeno.pm. We map project name, status, dates, owner, and description fields directly. Custom project fields and form-derived properties require mapping to destination equivalents because zeno.pm uses a configurable form-builder for project metadata. |
| Programs | Mapping required | Programs aggregate multiple projects in zeno.pm. We preserve the program-to-project parent-child relationship and map program-level financials and status by rolling up child project data. The program object has fewer standard fields than Projects, so we handle it as a secondary mapping pass. |
| Portfolios | Mapping required | Portfolios are the top-level container in zeno.pm, aligned to investments, regions, business units, or product lines. We map portfolio hierarchies and aggregate any portfolio-level KPIs from child Programs and Projects. |
| Custom Fields | Mapping required | Zeno.PM allows organisations to define custom fields on Projects, Programs, and Portfolios via its form-builder. We extract the full custom field schema during discovery and map each field to the destination system's equivalent, flagging any fields with picklist or conditional logic dependencies. |
| Risks | Mapping required | Risks are stored as structured records attached to a Project. We map risk title, likelihood, impact, status, owner, and mitigation notes. The risk register is treated as a child collection of the parent project during migration. |
| Issues | Mapping required | Issues are stored alongside Risks as a separate log within each Project. We map issue title, priority, status, owner, and description. Issues and Risks share a similar schema structure in zeno.pm, so we handle them in a shared transformation pass. |
| Financials | Mapping required | 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 where present. Financials are tied to the project record, not stored independently. |
| Resources | Mapping required | Resource management in zeno.pm tracks team member assignments to projects and programs. We map resource names, roles, allocation percentages, and availability. Resource capacity and utilisation data is derived from assignment records rather than a separate capacity object. |
| Schedules and Milestones | Mapping required | Zeno.PM stores project schedules as date properties on the project record. Milestone dates and dependencies are handled as project-level metadata rather than independent schedule objects. We map milestone name, due date, and status, and flag any inter-project dependencies for manual review. |
| Attachments | Not in this platform | Zeno.PM does not expose a public REST API for attachment export or import. We cannot automatically migrate binary attachments (documents, images, linked files) and instead document the full attachment list as a reference inventory for manual re-upload after migration. |
| Reports | Not in this platform | Zeno.PM's reporting suite consists of pre-configured report definitions and dashboards rendered server-side. Report configurations are not exposed via a documented API. We migrate the underlying data that feeds reports (Projects, Programs, financials, risks, issues) so that equivalent reports can be rebuilt in the destination system. |
| AI-Generated Data | Mapping required | Zeno.PM embeds AI features that generate or enrich project data such as summaries or risk flags. We identify records with AI-generated content during profiling, preserve the output as-is, and flag it for customer review so they can validate or regenerate it in the destination system. |
Gotchas
What to watch for in zeno.pm migrations
Issues we've hit on past zeno.pm migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No documented public API for data export
Attachments are not accessible via API
Report definitions are not portable
No automated .mpp or legacy tool migration
Custom form fields require schema discovery before mapping
| Severity | Issue |
|---|---|
| High | No documented public API for data export |
| High | Attachments are not accessible via API |
| Medium | Report definitions are not portable |
| Medium | No automated .mpp or legacy tool migration |
| Low | Custom form fields require schema discovery before mapping |
Leaving zeno.pm?
Where zeno.pm customers move next
5 destinations zeno.pm can migrate to.
How a zeno.pm migration works
Four steps, zeno.pm-specific
Connect
Not publicly documented into zeno.pm. Scopes limited to read-only on the data we move.
Map
We translate zeno.pm-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate zeno.pm quirks before production.
Migrate
Full migration with zeno.pm rate-limit handling. Rollback available throughout.
FAQ
zeno.pm migration FAQ
Answers to the questions buyers ask most during zeno.pm migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your zeno.pm migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate zeno.pm.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your zeno.pm setup and destination — written quote back within a business day.