Migrate from Project.co to Microsoft Project

Project.co Projects map directly to Microsoft Project Online Project sites (PWA). Each Project.co project name, description, status, created date, and custom field values migrate to the corresponding Project Online project. Project.co's flat project list has no native hierarchy in Microsoft Project either, but Microsoft Project's project site structure provides SharePoint integration for associated content. We preserve the project created date as the project start date in Microsoft Project; due date from Project.co maps to a custom finish date field if the destination org uses custom fields.

Project.co Tasks migrate to Microsoft Project Tasks within each project. We map task title, description, assignee, due date, and status. Project.co's task status values (To Do, In Progress, Done) map to Microsoft Project's percent complete or state model. Project.co has no task dependencies or scheduling fields natively, so we reconstruct a basic schedule by ordering tasks chronologically by due date and creating Finish-to-Start dependencies between tasks in sequence order as a starting point; the customer refines dependencies post-migration in Microsoft Project's Gantt view. Custom field values on tasks migrate as Project Online custom fields.

Project.co Discussions are per-project threaded message feeds with author, timestamp, and body text. Microsoft Project Online has no native discussion object. We flatten each discussion thread as a chronological list of comments and create a SharePoint page within the associated project site that contains the full discussion history in reverse-chronological order, with author names and timestamps preserved. Alternatively, if the customer uses Microsoft Teams, we can create a Teams channel post per project with the same content. The customer chooses the target during scoping.

Project.co files stored in project-level folders migrate to SharePoint document libraries attached to the Microsoft Project Online site. We download each file binary from Project.co, preserve the folder path as a SharePoint library folder structure, and re-upload using the SharePoint REST API. File metadata (uploader name, upload date) migrates as SharePoint column values. Large file counts extend the migration timeline proportionally because each file requires an individual download-reupload cycle; we surface total file volume during scoping so the customer can plan the export window accordingly.

Project.co Notes are standalone rich-text documents attached to projects. We create SharePoint pages within the project site with the same title and rich-text body. Formatting is preserved where the destination supports basic HTML; complex formatting may require minor manual cleanup post-migration. We note the total count of Notes during scoping because each is a separate content migration item.

Project.co time entries (task association, duration, billable flag, date) migrate to Microsoft Project as hours logged against the corresponding task. We convert the duration to hours and create a task assignment with hours in the resource plan. The billable flag from Project.co migrates as a custom field on the task or as a column in the associated SharePoint list; Microsoft Project Online does not have a native billable flag at the task level. Hourly rates are not present in Project.co and must be configured manually per user in Microsoft Project Online or in an associated timesheet system.

Project.co recurring tasks store a recurrence rule and next-run date. We create the recurring task as a standard Microsoft Project Task and flag it as recurring in the notes field with the original recurrence rule text. Microsoft Project Online does not have a native recurring task scheduler equivalent to Project.co's recurrence model; the recurrence pattern must be manually re-established post-migration using Microsoft Project's recurring task feature or Power Automate.

Project.co custom field definitions (name, type, options) and their values per record migrate to Microsoft Project Online custom fields. Project.co field types (text, number, date, dropdown) map to equivalent Project Online field types. Custom fields are scoped to the PWA site in Project Online; we configure them before record import so that values load during the main migration phase.

Project.co's per-user roles scoped to individual projects (team member, client, freelancer, project-specific admin) map to SharePoint group membership on the project site. We extract every role assignment from Project.co and create corresponding SharePoint groups in the destination Microsoft Project Online site. Client portal access (Project.co's no-paid-seat client access) maps to an Entra ID guest account or an external SharePoint group, depending on the customer's tenant settings. Role mapping requires coordination with the customer's M365 admin during scoping.

Project.co clients access projects via client portal links without consuming a paid seat. We extract client email addresses and names and create Entra ID guest accounts or configure SharePoint external access links on the project site, depending on the customer's security policy. Client viewing permissions are mapped to SharePoint read-level access on the associated project site's document library and project details page.