Migrate your Meegle data

Workflows are the top-level container in Meegle's data model. They define the visual map structure, including nodes, connections, and metadata. We export the full workflow definition as structured JSON and recreate it 1:1 in the target system.

Nodes are the building blocks within a Workflow. Each node type (task, milestone, group) has a defined schema. We preserve node type, position, and all standard properties during migration.

Tasks are a specific node type in Meegle. They include title, description, assignee, due date, status, and attachment references. Standard task fields migrate without transformation.

Subtasks exist as nested node relationships within a parent task node. The nesting structure requires flattening or preserving depending on the destination's data model. We flag the relationship explicitly in the migration manifest.

Meegle supports custom fields per workflow or across spaces. Field types include text, number, date, formula, and multi-select. Custom field schemas vary by workspace, so we map each field's type and options to the destination equivalent.

Views are display configurations tied to a workflow or space. They define which fields are shown, sort order, and grouping rules. We export view configurations as metadata and apply them to the corresponding workflow in the target system.

Meegle's advanced dependency feature links nodes with finish-to-start, start-to-start, and custom dependency types. These relationships require field-level mapping as dependency notation differs across platforms.

Roles govern cross-space authorization in Meegle. Role definitions include which users can access which nodes and fields. We map role assignments to the destination's permission model.

Attachments stored in Meegle's file system (up to 20T on Premium/Enterprise) are extracted by reference during export. We re-link them after importing tasks and nodes into the destination.

Meegle automations run on triggers such as task status changes or field updates. Automation logic is migrated as configuration, but execution may need validation in the target system due to environmental differences.

Member schedule tracks team member availability and allocation. This data maps to resource management objects in destination PM tools, though granularity varies by platform.

Change management is a first-class module in Meegle Standard and above. It tracks change requests, approvals, and implementation status. We preserve the change log entries and associate them with relevant tasks.