Migrate from web2Project to Microsoft Project

web2Project Projects map directly to Microsoft Project Project files (MPP) or Project Online workspaces. The project name, description, color coding, start and finish dates, priority, and status transfer as-is. Project-level custom fields map to Microsoft Project custom fields via the Field Picker. We detect project count during discovery to determine whether the destination is a single MPP deliverable or a SharePoint-connected Project Online workspace with multiple projects.

web2Project Tasks map to Microsoft Project Tasks with task name, start and finish dates, duration, priority, percent complete, and task notes preserved. Subtask hierarchy (parent-child relationships) transfers as Outline Level and Summary Task structure in Microsoft Project. Milestones in web2Project (tasks with zero duration) become Microsoft Project milestone tasks. Task-level custom fields map to corresponding Microsoft Project custom fields.

web2Project inter-task dependencies map to Microsoft Project predecessor-successor links. We translate Finish-to-Start (the standard web2Project dependency type) to Microsoft Project FS predecessor links. Start-to-Start and Finish-to-Finish dependencies map to SS and FF predecessor types respectively. Lead and Lag time values transfer as the Lag field in Microsoft Project. Circular dependency detection in web2Project is flagged and escalated during discovery so it does not block import.

web2Project Users map to Microsoft Project Resources. We extract the user display name, email address, and role assignment. Resource type is set to Material or Work depending on whether the user represents a person or a consumable resource. Active/inactive status maps to Resource's active flag. Role names from web2Project transfer as Resource Notes for capacity planning reference. Capacity, calendar, and cost rate fields require manual configuration in Microsoft Project and are flagged in the handoff document.

web2Project Companies are organizational entities with projects assigned to them. Microsoft Project does not have a native Company or Account object. We map Companies as Project-level custom text fields (e.g., Client) on each project, or as a Summary Task named after the company at the top of the project outline. The customer chooses the preferred representation during scoping. If multiple projects map to the same company, the organization may prefer a SharePoint list or Project Online Enterprise Resource Pool entry for cross-project reference.

web2Project Departments are sub-organizational units within Companies. Microsoft Project Resources support a Group field that maps to organizational groupings. We map Departments to the Resource Group field on the corresponding resources, which enables filtering and grouping in Microsoft Project resource views. The alternative is a Project-level custom field if the organization prefers department-level reporting at the project rather than resource level.

web2Project v2.4 custom fields (text, number, date, dropdown, checkbox) map to Microsoft Project custom fields using the Field Picker. Note that Microsoft Project Plan 3 and Project Desktop support up to 10 custom fields per project; Project Plan 1 does not support custom fields at all. We confirm the destination license tier during scoping. If the source has more custom fields than the destination supports, we migrate the highest-priority fields and document the remainder for manual entry. Custom field schema differs between pre-v2.4 and post-v2.4 web2Project instances; we detect the source version during database inspection and adjust extraction logic accordingly.

web2Project budget fields are explicitly documented as documentation-only with no financial calculation, tracking, or reporting logic. We migrate these values as read-only text custom fields in Microsoft Project. No budget-versus-actual reporting, no cost rollup, and no resource rate integration is implemented because the source values carry no financial calculation context. Any actual budget tracking must be re-implemented in Microsoft Project using cost resources, fixed costs, or a Project Online financial integration.

web2Project project-specific forum threads (categories and post content) map to Microsoft Project Task Notes. Each forum post becomes a separate line within the task note, preserving the post author, timestamp, and body text. Forum thread ordering is preserved by sequential numbering within the note. This is an informational mapping only; Microsoft Project does not have a native discussion or collaboration object. The customer should evaluate whether SharePoint task collaboration, Teams channel posts, or Planner comments are more appropriate for ongoing team communication post-migration.

web2Project file attachments at the project and task level store file metadata (filename, upload date, uploader) and a reference to the file location. We migrate file metadata as a Microsoft Project Hyperlink on the relevant task, pointing to the original file path or a SharePoint document library URL. Actual file content transfer (moving binary files from web2Project's upload directory to the destination SharePoint site or file server) is a separate file transfer step coordinated alongside the database migration. We flag this step explicitly in the handoff document because it is not covered by database-to-API migration logic.

web2Project calendar events with iCalendar export support map to Microsoft Project Tasks with Start and Finish dates. The event title becomes the task name and the event description becomes the task note. Recurrence patterns in web2Project calendar events do not transfer; recurring events are migrated as individual tasks and flagged for manual recurrence setup in Microsoft Project. Microsoft Project's base calendar (Standard, Night Shift, or custom) can be configured to reflect the organization's working days if the web2Project calendar had non-standard working hours.