Migrate from Moovila to Microsoft Project

Moovila Projects map directly to Microsoft Project project files or Project for the web projects. We migrate project name, start date, finish date, schedule mode (from vs finish), calendar assignment, and project-level custom fields. Projects derived from Moovila base templates retain their task structure and milestone anchor points. Project-level properties like budget and cost data migrate if present in Moovila; Project Desktop stores these in custom fields or the Project Summary Task.

Moovila Tasks and subtasks migrate as Microsoft Project Tasks with WBS hierarchy preserved. We map task name, duration, start and finish dates, percent complete, priority, constraint type, and deadline to the corresponding Project fields. Moovila's task acceptance/rejection status migrates as a custom field since Project does not have a native acceptance state. Task notes migrate to the Project Task Notes field. Moovila's manual scheduling flag maps to Project's Task Mode field (Manual vs Auto Scheduled).

Moovila's predecessor-successor relationships (finish-to-start, start-to-start, finish-to-finish, start-to-finish) map directly to Microsoft Project's Predecessor and Successor fields. We preserve the dependency type, lag time, and cross-task references during migration. Cross-project dependencies from Moovila map to cross-project links in Project Desktop but are flagged as unsupported in Project for the web, where they require manual recreation.

Moovila Milestones migrate as Microsoft Project Milestone tasks (zero-duration tasks marked as milestones). We preserve milestone name, scheduled date, and linkage to dependent tasks. Moovila's milestone-to-task linkage that anchors critical path calculations is represented as the milestone's position in the predecessor chain within Project.

Moovila Resources (individuals, roles, and enterprises) map to Microsoft Project Resources. We migrate resource name, type (material vs work), max units, hourly rate (cost rate), calendar, and email if present. Moovila's role-level and enterprise-level cost rates migrate as cost rate tables in Project's Resource Sheet. Resource availability periods from Moovila's resource modeling map to the Resource Availability grid in Project Desktop.

Moovila resource-to-task assignments migrate as Project Assignments with Work (hours), Units (allocation percentage), and Assignment cost calculated from the resource rate and assignment duration. Moovila's Perfect Resource Management utilization targets migrate as Project Assignment Owner fields or custom fields for capacity analysis. If Moovila captures overallocation or utilization conflicts, these are flagged for resolution in Project's Resource Usage view.

Moovila base templates migrate as Microsoft Project template files (.mpt) or as reusable project templates in Project for the web. We preserve the task structure, milestone positions, default durations, and standard dependencies. Template analytics data (Business/Enterprise tier only) does not migrate as it is a reporting layer not a structural element; we document the template performance benchmarks separately for the customer to reference during post-migration template optimization.

Moovila execution-phase mini-templates stitch into base templates to form complete projects. We map each mini-template's task group to a Phase summary task within the destination project, preserving the phase-level grouping and its internal dependencies. Phase-level performance data from Moovila migrates as a custom field on the Phase summary task for post-migration analysis.

Moovila Risk Registers contain both manually entered risks and AI-generated risk predictions. Microsoft Project does not have a native risk register object. We migrate manual risk entries as rows in a risks-and-issues document delivered alongside the project data, with risk title, description, severity, status, and mitigation notes. AI-generated risk predictions from Moovila's RPAX engine are flagged as regenerated data and excluded from the import because they are computed outputs tied to Moovila's analysis model, not stored data.

Time submissions from Moovila Business and Enterprise tiers migrate as Assignment Actual Work on the corresponding Project task assignment. We map hours worked, dates, and billing codes where present. Pro-tier customers have no time tracking data to migrate. Approval workflows from Moovila are documented separately and not migrated as Project does not have a native approval workflow for time submissions; this requires a Power Automate flow or manual process post-migration.

Moovila custom fields on Projects and Tasks migrate to Microsoft Project custom fields of the closest matching type (text, number, date, flag, cost). Project Desktop supports custom fields at the project, task, and resource level via the Custom Fields dialog. Project for the web uses custom columns in the grid view. We map the Moovila field label to the Project field name and flag any type conversions required (e.g., multi-select picklist in Moovila becomes text in Project).