Migrate from zeno.pm to Trello

zeno.pm Portfolios aggregate Programs and Projects by investment, region, or business unit. Trello has no portfolio object. We map Portfolios to Trello Organizations as the top-level container, using the Organization description and a pinned Master Board to hold portfolio-level metadata. Financial roll-ups and KPI summaries from zeno.pm are preserved as Custom Fields on the Master Board and re-entered manually since Trello has no native financial model.

zeno.pm Programs group related Projects under a single program owner with program-level financials and status. We map each Program to a Trello Board, using the Board description to carry program-level metadata and Board Labels to indicate project status across the program. Program-level financial roll-ups require a Custom Field Power-Up on the Board or manual tracking in a linked spreadsheet.

zeno.pm Projects are the primary record containing tasks, milestones, financials, risks, and issues. We map each zeno.pm Project to a Trello Board, preserving project name, status, description, start date, end date, and owner. Trello Board start dates are stored in a Custom Field since the native Board object has no date fields. Project status (active, on hold, closed) maps to Board visibility settings and List naming conventions.

zeno.pm tasks and milestones are stored as project-level date properties rather than independent schedule objects. Milestone dates migrate as Card due dates with a milestone Label. Standard tasks migrate as Cards with descriptions, assignees (mapped to Trello Members), and checklists representing sub-tasks. zeno.pm task hierarchies are flattened to Cards and checklist items because Trello has no native sub-project or WBS structure.

zeno.pm Risks are structured records attached to a Project: title, likelihood, impact, status, owner, and mitigation notes. We map Risks to Trello Cards with a Risk Label, a risk-status Custom Field (Active, Mitigated, Closed), and likelihood and impact ratings as number Custom Fields. Mitigation notes become Card descriptions. The risk register as a whole is represented as a dedicated List on the Project Board or a separate Risks Board linked via a Board Connector Power-Up.

zeno.pm Issues follow a similar schema to Risks: title, priority, status, owner, and description. We map Issues to Trello Cards with an Issue Label, a priority Custom Field (Critical, High, Medium, Low), and status as a Card Label or List position. Issue ownership maps to Card assignees. The Issues and Risks can coexist on the same Board using Labels to distinguish them, which is the approach we recommend for small-to-medium project teams.

zeno.pm stores project budget, actuals, and forecast as project-level properties. Trello has no native financial model. We map budget and forecast as number Custom Fields on the Board, and actuals as a read-only number Custom Field updated post-migration. Currency is stored as a text Custom Field. If the customer requires formula-driven fields (variance, burn rate), we document the requirement for a Custom Fields Power-Up or a linked Google Sheets integration.

zeno.pm Resources track team member assignments to projects with allocation percentages and roles. We map resource names to Trello Members and allocation percentages to a number Custom Field on each Card. Role information (Project Manager, Developer, Designer) is stored as a text Custom Field. Trello has no native capacity planning or utilisation tracking; we document this gap and recommend a Power-Up or external resource management tool for teams requiring capacity visibility.

zeno.pm stores project schedules as date properties on the project record rather than as independent schedule objects. Milestone dates map to Card due dates. Project-level start and end dates map to Board Custom Fields. Trello does not support a native dependency graph; if zeno.pm has task dependencies, we represent these as checklist dependencies (card links) or as a written dependency map delivered to the customer for manual recreation using the Calendar Power-Up or a third-party dependency tool.

zeno.pm custom fields defined via its form builder require schema discovery before mapping. During discovery, we extract the full form schema from zeno.pm admin console or support and map each custom field to a Trello Custom Field by type: text to Trello text, picklist to dropdown, number to number, date to date. Trello Custom Fields are scoped to the Board level, not the Organization level; we flag any custom fields that should appear on multiple Boards for the customer to recreate per Board.

zeno.pm embeds AI features that generate project summaries and risk flags. We identify records with AI-generated content during profiling, preserve the output as Card description text, and flag these records with an AI-Generated Label. The customer should validate AI-generated content after migration since Trello does not have native AI enrichment features at the card level without a paid Power-Up.

zeno.pm does not expose a public REST API for attachment retrieval. We inventory all attachment references (file name, linked record, upload date) from the source export and deliver a structured re-upload checklist organised by Board and Card. We preserve the original file naming conventions and record associations so the customer can manually re-upload files to Trello Cards without losing context. This step adds time to the migration plan and must be accounted for in the project schedule.