Migrate from Genius Project to Microsoft Project

Genius Project Projects map to Microsoft Project Project (PWA Project or Project for the Web project). The Project Name, Start Date, Finish Date, and Description transfer directly. We map the Project Status and Priority custom fields to Enterprise Custom Fields in Project Online. The Stage-Gate stage assignment maps to an Enterprise Custom Field picklist; governance workflow logic does not migrate. Project-level Cost Plan summaries map to custom cost fields on the Project Summary task.

Genius Project Tasks map to Microsoft Project Tasks with hierarchical parent-child relationships preserved through the Outline Number and WBS fields. Task Name, Start, Finish, Duration, % Complete, Priority, and Constraint Type transfer directly. Task-level resource assignments map to Assignment records in Microsoft Project. Summary tasks in Microsoft Project correspond to parent tasks in Genius Project; we preserve the grouping by setting IsSummary=True on the parent task record.

Genius Project Subtasks flatten into Microsoft Project Tasks with the same parent assignment. We preserve the Subtask Name, dates, duration, and assignment. Microsoft Project supports unlimited nesting depth through outline levels; we map all subtask hierarchy to the equivalent outline level. Notes and custom fields on subtasks migrate to Task Notes and Enterprise Custom Fields on the corresponding Microsoft Project Task.

Genius Project Resources map to Microsoft Project Resources in the Enterprise Resource Pool (PWA) or local Resource Sheet (Project for the Web). Resource Name, Email, Type (User, Equipment, Material), Max Units, and Cost Rate transfer. The capacity utilization percentage from Genius Project maps to Max Units; for example, a 80% allocation in Genius Project becomes Max Units = 0.8 in Microsoft Project. Generic Resources and Role Resources require customer guidance on whether to map to named resources or role-level resources.

Genius Project task-resource assignments map to Microsoft Project Assignment records linking Task to Resource. Assignment Start, Finish, Units, and Work (hours) transfer. Microsoft Project calculates assignment cost from the Resource Cost Rate multiplied by Work; we validate that cost rate values from Genius Project map correctly to the Rate fields in the destination Resource sheet. Overtime rate assignments do not have a direct equivalent and are noted in the migration inventory.

Stage-Gate stage names and order from Genius Project map to a Microsoft Project Online Enterprise Custom Field defined as a Lookup Table with the stage labels in sequence. We set the stage value on each Project record. The approval workflow logic attached to each gate in Genius Project does not migrate; we deliver a written Stage-Gate Workflow Inventory with each stage name, gate condition, approver role, and a note that the governance workflow requires rebuild in Power Automate or a PWA workflow. Stage order is preserved via the Lookup Table index.

Genius Project Portfolios have no direct Microsoft Project object. We export the portfolio membership (which Projects belong to which Portfolio) and reconstruct it in the destination as a SharePoint Online site with a Project List linking to each migrated Project via URL. Alternatively, for customers on Microsoft 365, we map Portfolio membership to Microsoft 365 Group membership with Planner as the project grouping surface. The migration inventory documents the full portfolio hierarchy so that the customer's PMO can rebuild dashboards in Power BI.

Genius Project Cost Plans store line items with categories (Labor, Material, Expense, etc.), Planned Cost, Actual Cost, and Variance per project. Microsoft Project does not have a Cost Plan object; instead it supports cost fields on individual Tasks (Cost) and a Project Summary Cost field. We aggregate the Genius Project Cost Plan totals by category and map them to custom cost fields on the Project Summary task in Microsoft Project. The detailed line-item breakdown is exported as a structured CSV and provided as a reference document; customers who need the detailed cost breakdown post-migration use the CSV with Power BI or a linked Excel workbook.

Genius Project CapEx investment records track capital expenditure approvals, amounts, and tracking at the portfolio or project level. Microsoft Project has no CapEx object or equivalent financial investment tracking. We export CapEx records as structured data and deliver them in a CSV alongside the migration. Customers who require CapEx tracking post-migration must configure it in a linked financial system such as Dynamics 365 Finance, SAP, or a custom Power Apps solution; we document the CapEx field schema and recommended data model in the migration handoff.

Genius Project Resource Capacity Plans store available hours, utilization percentage, and allocation by time period per Resource as time-series records. In Project Online PWA, we map these to Resource Plans with the time-phased availability data entered per Resource. In Project for the Web, capacity data is managed through the resource management add-in; we document the capacity values and provide a time-phased capacity CSV for manual entry or Power Automate-based import. Utilization percentages from Genius Project do not calculate automatically in Microsoft Project and require a separate utilization report to be rebuilt in Power BI.

Genius Project custom fields on Projects, Tasks, and Resources map to Microsoft Project Enterprise Custom Fields. Project Online enforces a 10-custom-field limit per entity type (Project, Task, Resource). At discovery, we audit the customer's full custom field inventory and assign a priority rank to each field. Fields that exceed the 10-field limit are noted as deferred; we provide a custom field priority matrix so the customer's admin can select which fields to migrate and which to retire or store in a linked SharePoint list. Project for the Web has the same 10-field limit with a different configuration interface.

Genius Project document attachments (files linked to Projects or Tasks) are exported with metadata (filename, file type, linked entity, upload date). Microsoft Project does not store documents natively; we redirect document links to a SharePoint Document Library provisioned by the customer's IT team. We provide a document mapping table with the original Genius Project URL, the new SharePoint URL, and the linked Project or Task name. Customers must provision the SharePoint library and grant appropriate permissions before migration.