Migrate from zeno.pm to Asana

zeno.pm Portfolios map to Asana either as a top-level Workspace (if the organisation uses one Workspace for all work) or as an Asana Portfolio with cross-team visibility. We assess the customer's Asana structure during scoping: single-Workspace is simpler and suits organisations with fewer than 50 projects; Portfolio-of-Projects suits multi-region or multi-business-unit organisations that need executive roll-up without merging teams. Portfolio KPIs and summary financials from zeno migrate to custom fields on a designated reporting Project.

zeno.pm Programs aggregate multiple Projects and carry program-level status and financial roll-ups. We map Programs to Asana Teams (the team-level container for projects, members, and permissions) or to a top-level Project with Sections for each child project, depending on whether the program has its own team membership distinct from the project teams. Program-level financial roll-up values migrate as custom fields on the Team or parent Project.

zeno.pm Projects map directly to Asana Projects. We map project name, description, status, start date, target end date, and owner. zeno's project-level financial properties (budget, actuals, forecast) migrate as numeric custom fields on the Asana Project. If zeno uses a template-based project structure with custom form fields, we extract the full form schema during discovery, create matching custom fields in Asana via the API, and map each field individually before project import.

zeno.pm custom fields are defined per-project via its form-builder and are not visible in any public API documentation. During discovery, we request the complete form schema from zeno support or extract it from the admin console. We then create equivalent Asana custom fields by type: zeno picklist fields map to Asana enum (single-select or multi-select), numeric fields to numeric, date fields to date. Conditional visibility rules and required-field constraints from zeno are documented in the mapping notes for the customer's admin to re-implement in Asana where applicable.

zeno.pm Risks are structured records attached to a Project: title, likelihood, impact, status, owner, mitigation notes, and creation date. We map each Risk to an Asana Task within the corresponding Project, using custom fields for Likelihood (enum: Low/Medium/High), Impact (enum: Low/Medium/High/Critical), Risk Status (enum: Open/In Progress/Mitigated/Closed), and Mitigating Action (text). The Task assignee maps from the zeno Risk owner. Risk creation date migrates as the Task created_at timestamp.

zeno.pm Issues share a similar schema to Risks: title, priority, status, owner, description, and creation date. We map each Issue to an Asana Task with custom fields for Issue Priority (enum: Low/Medium/High/Urgent), Issue Status (enum: Open/In Progress/Resolved/Closed), and Issue Description (rich text). Issues and Risks are kept in separate sections or labelled distinctly within each Project so that the customer's team can filter the project view to show only open issues or only open risks.

zeno.pm resource assignments associate a team member with a project or program at a percentage of availability. We map these to Asana Project members and Task assignees. For project-level assignments, the zeno resource becomes a member of the Asana Project. For task-level assignments, the resource becomes the Task assignee. Allocation percentage is stored in a custom numeric field on the Task if the customer requires it; otherwise it is preserved in the resource mapping documentation for the customer's admin to manage in Asana's workload view post-migration.

zeno.pm milestone dates are stored as project-level date properties rather than as independent schedule objects. We extract all milestone names and dates from the project record, create Asana Milestone tasks within each relevant Project, and set the milestone due date to match. Dependencies between milestones (if tracked in zeno as project metadata) are documented as a dependency map and the customer's admin recreates them in Asana Timeline view.

zeno.pm stores project-level budget, actual spend, and forecast as structured financial properties. We map these as numeric custom fields on the Asana Project: Budget (currency), Actual Cost (currency), Forecast (currency), and Variance (formula: Budget minus Actual). If zeno stores line-item financials, those migrate as subtasks or checklist items within a designated financial tracking task. Currency values migrate as plain numbers; any currency metadata is preserved in a text field.

zeno.pm embeds AI features that generate project summaries, risk summaries, or enriched text. We identify records with AI-generated content during profiling, preserve the full output text in the Task description or a dedicated custom field (AI_Summary__c), and flag it in the migration report so the customer knows which content was AI-generated and may require human review in Asana.

zeno.pm does not expose a public API for attachment retrieval. Documents, images, and files attached to Projects, Programs, or Risks cannot be retrieved programmatically. We inventory all attachment references during discovery (file name, linked record, approximate upload date) and produce a manual re-upload checklist organised by project. The customer re-uploads files post-migration using the checklist. We preserve file names and associations in the checklist so context is not lost even if the upload is manual.

zeno.pm's reporting suite consists of pre-configured server-rendered templates that are not accessible via any export mechanism. We migrate all underlying data — financials, risks, issues, milestones, timelines — so that equivalent reports can be rebuilt in Asana. We document the complete list of active zeno reports, their data sources, and their layout during discovery to guide the rebuild effort. This is a manual step performed by the customer or a consultant post-migration.