Migrate from iPlan to Trello

iPlan Projects map to Trello Boards. Each project becomes a standalone board with the project name as the board title, project description as the board description, and project dates preserved in a custom date field on the board card. For organizations using Workspace-level organization for multiple related projects, we create a Trello Workspace per portfolio and map each iPlan project to a board within it. We flag any iPlan projects with over 50 linked tasks and recommend board-splitting before migration to avoid Trello's performance degradation on very large boards.

iPlan Tasks map directly to Trello Cards. Task name becomes card title, task description migrates to card description (with rich text preserved as markdown), start and due dates migrate to the card date fields, and task priority maps to Trello labels using a configurable color-coded label scheme defined during scoping. Assigned resources in iPlan map to Trello card members. Task status (Not Started, In Progress, Completed) maps to card position within Trello lists (Backlog, In Progress, Done) configured to match the team's workflow.

iPlan Milestones map to Trello Cards with the milestone name as card title and the target date as the card due date. We create a Milestone label in Trello (distinct color from priority and status labels) so teams can filter all milestone cards across boards. Milestones with no linked tasks are created as standalone milestone cards and noted as requiring manual task linkage post-migration. Milestone interdependencies are captured in a dependency map delivered as a CSV alongside the migration for the admin to implement using a Power-Up like Card Dependencies.

iPlan Subtasks flatten into Trello Card checklists. Each parent task card receives a checklist named after the parent task or a project-defined grouping, with each subtask becoming a checklist item. Checklist item completion status migrates as checked or unchecked. We flag subtasks that exceed 50 items per card because Trello's checklist UX degrades at that volume. Teams needing true nested sub-cards (parent-child task hierarchy) are directed to the Card Repeater or similar Power-Up for post-migration configuration.

iPlan Resources (employee database records) map to Trello Workspace members. We extract resource name and email and invite each person as a Workspace member during migration. Resource roles and department metadata are preserved in a custom text field on each member's profile or as a board-level label for role-based filtering. iPlan's availability schedule and capacity calendar do not have a Trello equivalent; we note this gap in the migration handoff so the customer's admin can decide whether to use a capacity-planning Power-Up or external resource management tool.

iPlan custom fields on Tasks and Projects map to Trello Custom Fields. We map text, number, and dropdown custom fields to their Trello equivalents (text, number, dropdown). Checkbox fields map to Trello checkbox custom fields. Date fields map to Trello date custom fields. Formula and rollup fields from iPlan cannot migrate as computed fields because Trello does not support calculated custom field types; we migrate the last computed value as a static number or text field and document the formula for manual re-entry in Trello Power-Ups or external tools. Trello's 25-character custom field name limit requires truncation; we confirm abbreviation rules with the customer during scoping.

iPlan Timesheet records (hours logged, date, project, task) migrate as structured text appended to the relevant Trello Card description with a formatted log entry (date, hours, notes). Trello does not have a native timesheet object; the activity log in the card description preserves the data for reference but does not provide billing or capacity reporting. We flag timesheet data for any tasks with incomplete or inconsistently dated entries during validation. Organizations needing time tracking in Trello should consider a Power-Up like Tempo or a native time-tracking integration post-migration.

iPlan billing and financial tracking records migrate as structured financial summary text appended to the relevant Card description. Trello has no native billing or invoice object. We preserve budget amounts, cost variance, and billing status as text fields within the card for historical reference, but recommend that organizations requiring financial tracking in Trello use an external accounting integration or a financial Power-Up. We do not migrate billing data into Trello if the source records reference orphaned projects or incomplete timesheet data; these are flagged and listed in the reconciliation report.

iPlan knowledge-base articles export with article text, categories, and linked files. We map articles to Trello Card descriptions (for short, task-related articles) or recommend linking to an external knowledge tool (Confluence, Notion, Google Drive) with the link stored in the card description. Article categories map to Trello labels or board-level tags. We flag any knowledge-base articles exceeding 5,000 characters because Trello card descriptions have practical rendering limits at that length. File attachments from knowledge articles migrate separately as card attachments or are linked to the external document store if the customer elects an external knowledge management tool.

File attachments associated with iPlan Projects, Tasks, or Knowledge articles are extracted and uploaded as Trello Card attachments, preserving file names and upload timestamps. We map each attachment to the card representing its parent task or project. Large files (over 10 MB) are flagged and uploaded to a linked Google Drive or SharePoint folder with the URL stored in the card description. Trello's attachment restrictions in Enterprise environments are respected during migration; we coordinate with the customer's admin on any domain-level attachment policy.

iPlan workflow automation rules are captured as human-readable specifications during scoping. Each rule is documented with its trigger condition, criteria, and resulting actions in a structured format that maps to Trello Butler commands or Power-Up automation constructs. We deliver the workflow specification as a written document for the customer's admin to implement in Trello; we do not build the automations as part of the standard migration scope. Rule ordering and execution priority are documented for manual sequencing in Trello.

iPlan report configurations and dashboard layouts use a proprietary visualization schema that cannot be directly transferred to Trello. We export the underlying data (project metrics, task completion rates, earned-value figures) as CSV files alongside migration, and we deliver a written specification document describing each original report's metrics, filters, and recommended visualization so the customer can rebuild in Trello's dashboard Power-Up, Google Data Studio, or another BI tool. We do not rebuild reports in the destination platform as part of standard scope.