Migrate from PlanZone to Trello

PlanZone Projects map to Trello Boards as the top-level container. Each project name becomes the board name, and the project description migrates as the board description. We extract all projects from the CSV export and create one board per project during the load phase. If the customer uses PlanZone's template feature to spawn projects, we note the template origin on each board as a custom label so the admin can decide whether to use Trello's Board Templates feature for recurring setup.

PlanZone Tasks map to Trello Cards with the task name as card title, description as card body, assignee as card member, and due date migrated as card due date. We preserve the parent-child hierarchy by creating cards under the correct board and resolving the list assignment from the PlanZone stage (see Stage → List mapping). Task priority migrates as a Trello label with a priority color mapping so the admin can filter by priority across boards.

PlanZone task stages (e.g., Not Started, In Progress, Review, Done) map to Trello Lists within the destination Board. We extract all distinct stage values from the PlanZone CSV for each project and create corresponding lists. Stage ordering is preserved by creating lists in the order they appear in PlanZone. If PlanZone uses custom stage names, we carry them verbatim into Trello list names so the admin can rename them post-migration if desired.

PlanZone milestones are a flag on a task record with a target date and milestone name. We migrate milestone-flagged tasks as Trello Cards with the milestone name as card title, the milestone target date as card due date, and a Milestone label (we use a dedicated label color) to distinguish them from regular tasks. The admin can then use the Due Date power-up or Trello's calendar view to visualize milestone timing. There is no native milestone object in Trello, so this configuration is the standard workaround.

PlanZone stores task dependencies as a linked field on the child task pointing to the parent task ID. Trello has no native dependency object; dependencies are represented as card connections using the Card Links power-up or by adding the parent task name as a checklist item on the child card. We convert PlanZone's flat parent-reference format to one of these two strategies based on the customer's preference during scoping. The dependency resolution step must be validated before the load phase because it affects the checklist count and card structure.

PlanZone custom fields on Projects and Tasks are discovered during the schema audit step from the CSV column headers. We map each PlanZone custom field to a Trello Custom Fields Power-Up field of the matching type (text, number, date, dropdown). Trello Custom Fields is available from the Premium tier ($10/user); if the destination workspace is on the Free or Standard tier, we flag this as a tier upgrade requirement during scoping. The admin must enable the Custom Fields power-up on each destination board before migration.

PlanZone assigns tasks to users by email reference in the assignee field. We extract all distinct assignee emails from the CSV and match them against the Trello workspace member list. Members without a match in Trello are held in a reconciliation queue; the admin provisions new workspace members before the load phase runs. On Trello, a member added to a card is the equivalent of a PlanZone task assignment.

PlanZone task comments migrate as Trello card comments. We extract comment text, author email, and timestamp from the CSV. Comments are attached to the correct card by matching the parent task name. Trello comment ordering is chronological by timestamp. Large comment threads on individual cards may affect card rendering in Trello's UI, so we flag cards with more than 20 comments as a review item during the QA step.

PlanZone file attachments are referenced by URL in the CSV export. We re-upload each attachment as a Trello card attachment during the load phase, using the original filename. Attachments are tied to the correct card by matching the parent task. If an attachment URL is inaccessible (expired link, private storage), we flag it in the attachment manifest delivered with the scope agreement and note it as a manual-recreate item.

PlanZone reusable project templates define a starting structure of tasks and milestones. We export the template as a project skeleton and note which tasks are template-generated as a custom label (Template Origin) on each card. Trello has a Board Templates feature in the Premium tier for cloning a board structure. We do not create Trello Board Templates from PlanZone templates automatically; we deliver the template skeleton data and a written recommendation to use Trello's Board Templates feature to create the equivalent manually, which gives the admin control over which template becomes the canonical source.

PlanZone records the project owner as a user reference. We map the project owner to the corresponding Trello workspace member and add them as an Admin on the destination board during creation. This preserves the ownership hierarchy so the original PlanZone project owner has board administration rights in Trello from day one.

PlanZone stores project-level files and resources separately from task attachments. We export these as a file manifest listing each resource, its URL, and the project it belongs to. During the Trello load, we attach project-level files to the first card in the project's board (typically a board-intro or overview card) or add them as a pinned board resource if the destination uses a resource card pattern. The admin receives the file manifest as part of the scope agreement.