Migrate from OnePlan to Trello

OnePlan Plans map directly to Trello Boards. The Plan name becomes the Board name, and Plan type hierarchy (Program, Project, Sub-project) must be flattened: Programs become separate Boards, and Sub-projects become either separate Boards or Lists within the parent Board depending on the customer's structural preference. We define this flattening strategy during scoping. Board visibility defaults to Private unless the customer requires Workspace-level visibility.

OnePlan Work Plans map to Trello Lists within a Board. Each Work Plan's name becomes a List name, and the Work Plan's tasks populate that List as Cards. If the source Work Plan contains a schedule with start and end dates, those dates migrate to Card Due Dates or Custom Fields depending on the destination Custom Field configuration. We create Lists in the order defined by the Work Plan sequence if that ordering carries business meaning.

OnePlan Tasks map to Trello Cards. Task name becomes Card title; Task description migrates as Card description in markdown. Start date and due date from OnePlan map to Card Due Date fields or Date Custom Fields. Assigned resources from OnePlan map to Card members in Trello. Task dependencies from OnePlan cannot be represented as native Trello dependencies (Trello's dependency Power-Up is required for this) and are documented separately for post-migration rebuild.

OnePlan Risks have no native Trello equivalent. We map Risk records to Cards in a dedicated Risks List, set a Risk Label (e.g., red labeled) for visual identification, and migrate core fields (Risk name, description, likelihood, impact, status) as Card Custom Fields. The customer must enable the Custom Fields Power-Up on the destination Board before migration runs. Risks that require specialized tracking beyond what a Card provides should be migrated to a dedicated tool post-migration.

OnePlan Issues map similarly to Risks: Cards in a dedicated Issues List with an Issue Label for visual filtering. Core Issue fields (Issue name, description, priority, status, assigned owner) migrate as Card Custom Fields. Multi-select Choice fields from OnePlan Issues may not map directly if the destination Custom Field type is Dropdown (single-select) rather than Labels; we flag this during scoping and the customer chooses the resolution.

OnePlan Resources map to Trello Board members. We resolve Resources by email address and map them to Trello Members. If a Resource in OnePlan does not have a corresponding Trello user account, we hold them in a reconciliation queue for the customer's admin to provision before migration. Resource capacity and allocation data (percentage allocated per time period) has no native Trello representation and is documented in a separate capacity reference file for the customer's admin.

OnePlan Text custom fields map directly to Trello Custom Fields of type Text. We migrate the field name and all populated values per Card. Empty values are not copied. Text fields that use special characters or exceed Trello's display limits are truncated and flagged in the reconciliation report.

OnePlan Number and Currency custom fields map to Trello Custom Fields of type Number. Trello does not support a native Currency field type, so Currency values from OnePlan (e.g., $50,000) are stored as numeric values without currency symbol in Trello. We include the currency code (e.g., USD) as a prefix in the field name or as a separate Text Custom Field if the customer requires it.

OnePlan Date custom fields map to Trello Custom Fields of type Date. The date format from OnePlan is preserved as-is. Time component in OnePlan Date fields is stripped since Trello Date Custom Fields do not support time-of-day precision.

OnePlan Yes/No custom fields map to Trello Custom Fields of type Checkbox. A Yes value becomes a checked box; No becomes unchecked. We migrate the field name and preserve the boolean state per Card.

OnePlan Choice custom fields map to Trello Custom Fields of type Dropdown. The Choice options from OnePlan become Dropdown options in Trello. OnePlan multi-select Choice fields cannot map directly to Trello Dropdown (which is single-select); we handle this by either creating multiple single-select Dropdown fields (one per option) or by using Labels to represent multi-select values, and the customer chooses the strategy during scoping.

OnePlan User-type custom fields store a reference to a OnePlan resource. These map to Trello Card Members rather than a Custom Field. We resolve the user reference at migration time and add the member to the Card. If the User field allows multiple values, we add all resolved users as members. Fields that cannot be resolved are noted in the reconciliation report.

OnePlan Time-Phased Financial Plan data has no native Trello equivalent. Trello does not support financial planning, budget tracking, or time-phased financial allocation. We do not migrate this entity. We deliver a written inventory of all financial plan records as a CSV reference file so the customer's finance team can rebuild in a spreadsheet or a dedicated financial planning tool.

Resource allocation over time in OnePlan (percentage allocated per period) has no Trello equivalent. Trello shows team members as Card members but does not track capacity, allocation, or utilization. We do not migrate this entity. We deliver a resource capacity reference file for the customer's admin.

Stage Gate workflow configurations in OnePlan are system-level process settings that govern approval chains and stage transitions. These do not export from OnePlan's Migration Tool and have no equivalent in Trello's automation model. Butler Power-Up can handle basic card-triggered automations but cannot replicate the approval-gated workflow stages that OnePlan's Stage Gate model provides. We do not migrate workflows as code. We deliver a written inventory of every Stage Gate workflow with its stages, conditions, and actions so the customer's admin can evaluate Butler automation as a partial replacement.

The OnePlan Migration Tool does not handle file attachments, and the Trello import path for attachments requires Power-Up configuration and API access that is not part of standard CSV-based migration. We do not migrate attachments as part of the standard scope. We recommend a separate document migration using SharePoint or Trello's native attachment upload via Power-Up after the card migration completes. If the customer requires attachment migration, this is a separate scope item.