Migrate from Goplan to monday Work Management

Goplan project workspaces map to monday.com boards. Each project workspace's name, description, member access list, and date range migrate as the board name, board description, team members, and date column values. We create one board per project and map project-level member permissions to monday.com board member roles (board owner, editor, commenter, viewer). Archive state migrates as an archived status column if the board needs to remain visible but inactive.

Goplan tasks map to monday.com items within their corresponding board's groups. Task name becomes item name, task description becomes the item's text column or summary, and task status maps to a monday.com status column with color-coded labels. Assignments migrate as the person column; due dates migrate as the date column. If Goplan uses sub-tasks, these map to sub-items in monday.com.

Timesheet entries (hours logged per user, per task, per date range) map to monday.com's time tracking column values on the corresponding item. We extract the hours, date, user attribution, and task linkage from Goplan's timesheet export and create time entries against the migrated items. Note that monday.com time tracking requires Standard plan or above; if the destination is on Basic, we flag this during scoping and recommend a plan upgrade or alternative time-tracking integration.

Goplan custom field definitions and values migrate to monday.com columns using type matching: text fields map to text columns, number fields to numbers, dates to date columns, dropdowns to dropdown columns, and multi-select to tags or dropdown columns. We extract the full field schema during discovery and pre-create the corresponding columns on each board before item import to avoid post-import restructuring.

Goplan user accounts and collaborator roles extract with their project memberships and permission levels. We map these to monday.com users by email match. If a Goplan user has no matching monday.com account, we flag them in the reconciliation queue for the customer's admin to provision before item import (since item assignments require a valid monday.com user).

Goplan report definitions and their underlying data export as CSV. We preserve report definitions and data but do not migrate reports as live monday.com dashboards; monday.com dashboards are rebuilt from scratch using the migrated board data as source. We deliver a written report inventory listing each Goplan report's name, filters, and data sources with a recommended monday.com dashboard construction plan for the customer's admin.

Task-level comments and discussion threads are not confirmed as a separately exportable object in Goplan's available documentation. We verify comment availability during scoping. If comments exist as exportable text, we include them as an item description append or a linked document; if not, we flag this limitation in the migration scope and note that the customer should consider capturing comments manually before cutover if historical context is required.

File attachments on tasks or projects have not been confirmed in available Goplan data. We verify attachment availability during scoping and handle them as a separate media migration if present. monday.com stores files as file columns and Content Documents; if attachments exist, we migrate them as file columns within the relevant board items.

If Goplan uses nested projects or parent-child relationships, we map these to monday.com folder and sub-board hierarchy. We create a monday.com folder per top-level structure and nested boards within it, preserving the navigation relationship. Groups within a board handle task-level groupings rather than a separate hierarchy level.

Goplan automations (if any exist in the customer's account) are documented during discovery. monday.com's automation engine (available Standard+) uses trigger-action recipes that are architecturally different from Goplan's rule model. We do not migrate automations as code. We deliver a written automation inventory with each rule's trigger, condition, and action mapped to a recommended monday.com automation equivalent for the admin to rebuild post-migration.

Goplan task status values (e.g., To Do, In Progress, Done) map to monday.com status column labels with color coding. We preserve the status progression order so that board views filter and sort correctly. If Goplan uses custom workflow stages, we create custom status columns to match rather than forcing the default monday.com labels.

Goplan tags used to categorize tasks map to monday.com tags or dropdown columns depending on whether multi-select is required. We extract distinct tag values during discovery and configure the column with the relevant options pre-populated so that item import assigns tags without creating new values on the fly.