Migrate from Meegle to Microsoft Project

Meegle Workflows map to Microsoft Project as the top-level container. Each Workflow becomes a separate .mppx or Project for the Web project. The Workflow's name, description, and date range map to the Project's Name, Description, and Start Date fields. If the customer uses Meegle's cross-enterprise collaboration (Premium feature), we preserve the enterprise-level grouping as a Microsoft 365 Group-linked Project within Project for the Web.

Meegle Nodes of type Task map to Microsoft Project Tasks. Title, description, assignee, due date, start date, and status transfer directly. Duration in Meegle (if set manually) maps to Task Duration in Project; if Meegle nodes rely on dependencies for scheduling rather than explicit duration, we infer duration from the dependency chain length during transformation.

Meegle Milestone nodes map to Microsoft Project Milestone tasks with zero duration. The milestone name and date transfer directly. If the milestone has incoming dependencies, those become predecessor links on the milestone task in Project.

Meegle Group nodes (which aggregate related nodes visually) map to Microsoft Project Summary Tasks. The grouping hierarchy in Meegle determines the WBS outline level in Project. We preserve the parent-child relationship from Meegle's node nesting as the Task Hierarchy in Project.

Meegle's nested node structure maps to Project's outline hierarchy. The depth of nesting becomes WBS levels. We flatten the visual hierarchy during transformation and reconstruct it as indented task rows. If a subtask in Meegle has its own subtasks, the same recursion applies in Project.

Meegle's finish-to-start and start-to-start connections map to Microsoft Project FS and SS predecessor types. Meegle's finish-to-finish and start-to-finish types map to FF and SF predecessors. Lag time from Meegle's connection offset becomes the Lag field in Project. We infer the dependency type from the arrow direction in the visual node graph when no explicit type is stored.

Meegle custom fields per workflow map to Microsoft Project Enterprise Custom Fields (Text, Number, Date, Flag, or Lookup). We create the custom field definition in Project before migration and map values directly. Multi-select fields in Meegle become Text fields with semicolon-delimited values in Project unless a Lookup table is configured. Formula fields in Meegle Standard/Premium require manual rebuild as Project custom fields are formula-capable only at the Project level, not at the individual task level on Plan 3.

Meegle's Member Schedule (tracking team availability and allocation) maps to Microsoft Project Resources. We extract member email, name, and availability percentages from Meegle and create Resource records in Project. If a Meegle Member has no corresponding Microsoft 365 user license in the destination, we flag that resource as a Material Resource in Project rather than a Work Resource. Max Units from Meegle's allocation percentages transfer to the Resource's Max Units field.

Meegle Roles govern node-level access and define who can view or edit which nodes. Microsoft Project does not have a role-based permission model at the task level. We map Meegle Role names to a custom Text field on Tasks or to Resource Groups, and we deliver a written Role-to-Project Permission matrix for the customer's admin to implement via Microsoft 365 Groups and SharePoint site permissions post-migration.

Meegle file attachments stored in Meegle's 2T to 20T storage map to SharePoint document libraries linked from Project tasks via Hyperlink fields, or to OneDrive for Business if the organization uses Project for the Web with Microsoft 365. We extract the attachment URL from Meegle during export and insert it as a Hyperlink on the corresponding Project task. Files that cannot be accessed after export are flagged with a broken-link note.

Meegle's change management module (Standard tier and above) tracks change requests with approval status and implementation notes. We map change records to Project tasks with a custom change_request_status field (Open, Under Review, Approved, Implemented, Rejected) and preserve the change description and approver in custom text fields. We do not migrate the approval workflow itself as Meegle's change management approval logic does not have a Microsoft Project equivalent.