Migrate from Project Insight to Microsoft Project

Project Insight projects map directly to Microsoft Project files (MPP) or Project Online projects. We extract the project record including name, description, start date, finish date, status, and priority from the project-level report. In Project Online, this creates a project site with the schedule visible in the web interface and the Project Desktop client. Project Insight's project-level custom fields export in the same row and map to custom fields in the destination.

Tasks export via the task-level report with the parent-child hierarchy preserved through a flattened WBS path or indent structure. We reconstruct the WBS tree in Microsoft Project using the outline number and indent level, then restore predecessor-successor links using the dependency report. Duration, start date, finish date, percent complete, and task type migrate directly. Summary tasks map as Summary rows in Microsoft Project.

Resource records from Project Insight's resource management report map to Microsoft Project resources. We import resource name, type (material or work), max units, cost rate table entries, and calendar assignments. Project Insight's allocation percentage translates to assignment units in Microsoft Project. If Project Insight uses a resource pool shared across projects, we note this for the customer's administrator to configure the shared pool in Microsoft Project.

Project Insight custom fields are available on the Pro tier and above. Their values export within the same row as the parent object. We map each named custom field to an equivalent Microsoft Project custom field using the closest type match (text, number, date, flag, or outline code). Custom fields with dropdown options map to outline codes or lookup tables in Microsoft Project. If the source account is on the Free tier, no custom fields exist to export and this mapping step is skipped.

Project Insight time entries linked to tasks export as work values on task assignments in Microsoft Project. We aggregate time entries by task and resource, then set the assignment work field to the sum of hours. If the destination is Project Online, hours can also be tracked via the timesheet module. We flag any time entries that do not map to a task in the migration scope so the customer can handle them manually or via the timesheet system post-migration.

Project Insight constraint types (ASAP, Finish No Earlier Than, Finish No Later Than, Start No Earlier Than, Start No Later Than) export as a text field. Microsoft Project uses constraint dates combined with task type and deadline fields to control scheduling. We carry the original constraint type as a text custom field on the task and set the corresponding constraint date if one exists. Tasks with ASAP constraint become scheduling-driven tasks; tasks with hard constraints get explicit constraint dates. A scheduler must review all constraint-carrying tasks post-import because the two systems model scheduling priority differently.

Task-to-task predecessor relationships export via the dependency report. We translate finish-to-start, start-to-start, finish-to-finish, and start-to-finish relationship types into Microsoft Project predecessor fields using the FS, SS, FF, and SF codes. Lead and lag time values migrate as positive or negative day offsets on the predecessor entry. We validate that predecessor IDs resolve to tasks within the same project after the task sequence is established.

Project Insight portfolios and programs group multiple projects under a parent structure. Microsoft Project does not have a native portfolio object equivalent in Project Online or Project Desktop. We map portfolio-to-project associations to a cross-project grouping table or a Project Roadmap view, and the customer's administrator decides whether to use Project Online's Roadmap feature or a separate portfolio tracking method. We document the original portfolio structure for reference during rebuild.

Project Insight project status values (Active, On Hold, Complete, Archived) map to the status field or percent complete on the project summary task in Microsoft Project. We preserve the original status text in a custom field so the customer can sort or filter by the historical status after migration.

Project Insight users assigned as task owners or project managers map to Microsoft Project resources. We resolve users by email match to resources created from the resource report. Any user referenced in assignments but not found in the resource list goes to a reconciliation queue for the customer's administrator to provision. Resources without a corresponding Project license are created as material resources or informational entries as the customer prefers.