Migrate from Moovila to monday Work Management

Moovila Projects map directly to monday.com Boards. Project name, description, start and end dates, status, and owner assignment transfer to the Board name, description, and workspace members. Moovila's budget fields migrate as numeric custom columns on the board. We create boards via monday.com GraphQL API with the CreateBoard mutation using the workspace and board_kind arguments. Template-derived projects inherit the template's task structure and milestone placeholders as board structure.

Moovila Tasks and subtasks map to monday.com Items and Subitems. We preserve task hierarchy depth up to three levels of subitem nesting. Task status (Not Started, In Progress, Completed, On Hold, Cancelled) maps to a Status column with corresponding labels in monday.com. Assigned owners migrate as person column values by resolving email addresses against monday.com Workspace members. Due dates transfer to a Date column. Custom task fields map to monday.com custom columns by type: text fields to Text column, numeric to Numbers, dropdowns to Dropdown, and checkbox lists to Checkbox.

Moovila Milestones anchor critical path calculations and have associated dates and linked tasks. We represent milestones in monday.com as items with a milestone Status label (e.g., Milestone) and a Timeline or Date column. If the milestone has linked tasks, we add a dependency reference to the milestone item on those task items using monday.com's Dependencies column. The customer chooses between Timeline (start and end date) or single Date representation during scoping based on their reporting needs.

Moovila's task-to-task dependencies (finish-to-start, start-to-start, finish-to-finish, start-to-finish) map to monday.com's Dependencies column. We extract predecessor-successor relationships from Moovila's dependency model and create monday.com dependency entries using the connect_to_item or connect_dependencies mutations. Dependency type metadata beyond the monday.com binary 'blocked by'/'blocking' relationship is preserved in a text column on the item for reference. Critical path designation from Moovila's RPAX engine cannot be carried over as a calculated field.

Moovila resource assignments (individuals, roles, and enterprises) map to monday.com person column values. We resolve resources by email; any Moovila resource without a matching monday.com user account enters a reconciliation queue for the customer's admin to provision. Moovila's resource utilization targets and Dynachart assignments do not have a direct monday.com equivalent; we represent utilization as a numeric column on the board for manual population post-migration. Resource types (role labels) migrate as Dropdown column values on the resource item.

Moovila base templates and mini-templates map to monday.com Board Templates. We preserve the template's task structure, milestone anchors, resource placeholder assignments, and default durations. Template analytics (which Moovila generates on Business and Enterprise tiers showing which templates deliver margin and which do not) do not have a monday.com equivalent and cannot be migrated; we document the available analytics per template during scoping so the customer can reference it during monday.com reporting setup.

Moovila Risk Registers contain manually entered risks and RPAX-generated risk predictions. We migrate the manual risk records (title, description, severity, status, mitigation notes, assigned owner) as items in a dedicated risk board using Status, Severity (Dropdown), and text columns. RPAX-generated AI risk predictions and confidence scores are computed output and cannot be exported; we flag these during scoping and recommend regenerating risk analysis in monday.com's reporting layer or a connected BI tool post-migration.

Moovila time submissions, approval workflows, and billing codes (Business and Enterprise tiers only) map to monday.com's native Time Tracking column on items. Hours, dates, and the associated task item migrate as time entries linked to the item. Approval status is represented as a Status label on the time tracking entry. Billing codes and cost rates require a separate mapping table; we migrate them as Dropdown column values for assignment to time entries, but billing rate schedules require manual configuration in monday.com's integrations or a third-party billing tool.

Moovila user accounts, security roles, and team structures map to monday.com Workspace members. We match by email address. Security roles (Viewer, Editor, Admin) from Moovila map to monday.com permission levels within the workspace. SSO and domain management settings are documented as configuration notes for the customer's IT admin to reconfigure in monday.com's security settings post-migration.

Moovila attachments stored in Box, Dropbox, SharePoint, OneDrive, or Google Drive migrate as file references. monday.com's File column supports direct file attachments, and the platform has native integrations with all five cloud storage providers. We preserve the file URL and map it to the corresponding monday.com cloud integration or re-attach the file directly. File ownership and access permissions require reconfiguration in the destination cloud storage settings.

Moovila custom fields on projects and tasks map to monday.com custom columns. We handle type conversion: text fields to Text, numbers to Numbers, dates to Date, dropdowns to Dropdown, checkboxes to Checkbox, URLs to Link, and phone numbers to Phone. Multi-select fields map to Tags or Dropdown depending on the use case. Field-level validation rules in Moovila are documented for manual recreation in monday.com's column settings.

Moovila's bi-directional ConnectWise PSA sync creates linked records where project data lives in both systems. Migrating out of Moovila breaks the sync relationship. We treat ConnectWise records as external reference data and migrate the Moovila-native record as the primary object. The customer must re-establish PSA sync relationships manually after migration using monday.com's Integrations plan or a third-party connector. We deliver a written inventory of every active sync relationship during scoping so the customer's admin knows what to rebuild.