Migrate from Meegle to monday Work Management

Each Meegle Workflow maps to a monday.com Board. The Workflow name becomes the Board name, and the Workflow description migrates as the Board description. We create the Board under the appropriate monday.com Workspace before importing Nodes so that item creation targets a valid parent. Meegle Workflow templates do not auto-convert to live Boards; we create a Board instance and map the template's node structure as actual Items.

Meegle Nodes of type 'task' map to monday.com Items within the target Board. The node title becomes the Item name, node description becomes the Item description text, assignee maps to monday.com Person column, due date maps to Date column, and status maps to a Status column with values matched to the source node status labels. Each Item receives the Board as its parent context.

Meegle milestone nodes map to monday.com Items with the Status column set to a milestone label (e.g., 'Milestone'). Milestone Items retain their start and end dates in the Date column. The milestone name becomes the Item name. Milestone Items can have dependency relationships with other Items using monday.com's dependency column.

Meegle group nodes map to monday.com Groups within a Board. Group nodes that contain child nodes are converted to monday.com Groups with the group name preserved. Child task nodes land as Items within the corresponding Group. This preserves the Meegle hierarchical relationship while adapting to monday.com's flat Item-within-Group structure.

Meegle subtasks exist as nested Node relationships within a parent task node. We flatten this relationship by creating monday.com Subitems attached to the parent Item. Each Subitem inherits the parent's Board context and maps the subtask title, description, assignee, and status independently. Subitems are available from the Standard plan onward in monday.com.

Meegle custom fields per workflow map to monday.com Column types. Text fields map to Text Column, number fields map to Number Column, date fields map to Date Column, and formula fields map to Formula Column with the source expression translated to monday.com formula syntax. We pre-create all columns in the target Board before importing Items to avoid type mismatch errors.

Meegle multi-select fields map to monday.com Dropdown or Multi-Select Column depending on whether the field allows single or multiple selections. We extract the option labels from Meegle and populate the monday.com column options during column creation. Option values that do not exist in monday.com are added before Items are imported.

Meegle's advanced dependency feature with finish-to-start, start-to-start, and custom dependency types maps to monday.com's Dependency Column. We preserve the dependency direction and type as Item-level relationship metadata within the dependency column. Finish-to-start dependencies map directly; start-to-start dependencies are noted in a custom text field on the dependent Item for manual configuration if the destination workflow requires it.

Meegle's cross-space Roles governing node-level access map to monday.com Teams with Board-level and Item-level permission configurations. We extract the Role definitions, identify which Nodes each Role can access, and recreate those rules as monday.com Team membership plus Board access levels (full, limited, view-only). Meegle node-level permissions that do not have a direct monday.com equivalent are documented for admin review.

Meegle attachments stored in the platform's file system (up to 20T on Premium/Enterprise) are extracted by reference during export. We re-link attachments to the corresponding monday.com Item using the File Column type. If an attachment exceeds the target monday.com plan's storage (5G on Basic; unlimited on Standard+), we flag the attachment with a reference URL to the source file for manual retrieval.

Meegle's first-class Change Management module (available on Standard tier and above) tracks change requests, approvals, and implementation status. We map these to monday.com Items with a dedicated Status column for change state (Requested, In Review, Approved, Rejected, Implemented) and custom columns for approval date, requester, and change description. The change log entries migrate as Item updates or as a linked sub-board depending on complexity.

Meegle Member Schedule tracks team member availability and allocation. This maps to monday.com's Workload View for capacity planning and Time Tracking Column for actual hours logged. We preserve the allocation percentage and date range from Meegle as data in the Time Tracking Column and as a numeric custom field. Workload View configuration is created as a separate structural step post-migration.

Meegle's multi-view system (Table, Kanban, Gantt, Tree, Panorama) has no direct one-to-one equivalent in monday.com, which uses Board, Group, Timeline, Calendar, Map, Chart, and Doc views. We map the Table view to monday.com's main Board view, Kanban to Group view, and Gantt to Timeline view. Tree and Panorama views are documented as configuration notes for the admin to rebuild using monday.com's view options.

Meegle automations run on triggers such as task status changes or field updates. These are migrated as written configuration documentation, not as executable code. We document each Meegle automation with its trigger type, conditions, and resulting actions, and map it to a recommended monday.com Automation Recipe using monday's trigger-and-action framework. The admin rebuilds the automation in monday.com's Automation Center post-migration.