Migrate from PlanZone to monday Work Management

PlanZone Projects map to monday.com Boards. Each project becomes a separate Board with the project name, description, dates, status, and owner preserved. We use monday's Board creation API to provision the structure, then populate Items during the task import phase. If the customer's PlanZone instance uses sub-projects or nested project hierarchies, we create a workspace-level Board structure and use Board Groups to represent the hierarchy. The Board owner is set from the PlanZone project owner email via monday's team member API.

PlanZone Tasks map to monday.com Items within a Board. The task name becomes the Item name, assignee maps to the monday assignee column, due date maps to the Date column, status maps to a Status column (we create the status options to match PlanZone's stage values), and priority maps to a Labels or Priority column. Parent-child nesting is preserved by setting the subitem relationship or Group membership based on PlanZone's task hierarchy depth.

PlanZone Milestones are flagged task types marking key delivery points. We export them with a milestone indicator and target date, then map to monday's Status column (creating a dedicated milestone status like 'Milestone Reached') or to a Date column with a milestone flag label. The customer chooses the preferred representation during scoping. Milestone name and target date are preserved as Item properties.

PlanZone stores task dependencies as a parent-reference field on the child task (flat linked field). monday.com uses a dedicated Dependency column that supports bi-directional links. We transform the flat PlanZone dependency links into monday Dependency column entries by querying the exported task ID set, resolving the parent reference, and inserting the dependency pair into monday's dependency_graph via the API. This mapping step must be validated against the destination's dependency model before the load phase begins.

PlanZone reusable project templates define a starting structure of tasks and milestones. The template link is not preserved in the CSV export — when a project is created from a template, the relationship is severed. We export the template as a Project skeleton, flag which tasks are template-generated, and note the template origin as a custom property on each Item. The customer uses this documentation to recreate the template in monday via Board Templates after migration.

PlanZone supports custom fields on Projects and Tasks. We discover these during the schema audit step and map each to a typed monday.com column (text, number, date, dropdown, checkbox, etc.). monday's column type must be chosen based on the field's data type in PlanZone. Some complex PlanZone field types may not have a direct monday equivalent and are flagged as Text with the original value preserved.

File attachments on PlanZone tasks are stored separately and referenced by URL. We export them as a file manifest (URL, filename, associated task) during the CSV pass, then re-upload each file to monday's file storage during the load phase using the monday.com Files API. File metadata (upload date, file size) is preserved in the monday Item's file card.

PlanZone task comments are threaded text entries with author and timestamp. We export them as a flat list attached to the task and recreate them in monday's Updates section on the Item. Updates preserve the original author email (mapped to a monday team member if found) and timestamp. Rich text formatting is simplified to plain text where PlanZone formatting does not map directly.

PlanZone assigns tasks to users by email reference. We extract all distinct user emails from the PlanZone export and map them to monday.com Team Members by email match. Users without a matching monday account are held in a reconciliation queue for the customer to provision before the Item import phase. monday's guest access model is used for any external collaborators that need view-only access.

PlanZone project-level start dates and target dates map to monday Board Date columns at the board level (using monday's board date properties) or as Item-level Date columns. We preserve both the planned start and the target end, and use these to configure the Board Gantt view after migration.

PlanZone project status values (active, on hold, completed, archived) map to monday Status column options. We define the mapping during scoping and create matching Status options in the destination Board. The mapping must account for any archived or legacy status values in PlanZone that may not apply to an active monday workspace.

PlanZone recurring task patterns are stored as recurrence metadata on the task record. monday.com does not support native recurrence rules on Items without third-party integrations. We flag recurring task instances as Items with a custom property noting the recurrence pattern, and the customer rebuilds recurrence logic using monday's automation triggers (when date arrives, create item) post-migration.